A few weeks ago I gave a presentation to the STC Berkeley chapter on findability of help content. The recording is available here:
Download MP3 (right-click, then Save Link As)
For the slides, see Recording and slides for why users can't find answers in help. The link refers to the Silicon Valley chapter presentation of the same material -- the slides are the same, but the presentation to the Berkeley chapter (this recording) differed quite a bit given the audience feedback. (My presentation format involves presenting various problems to the audience and inviting them to provide solutions -- hence the difference in the presentations.)
I wrote a post reflecting on some of the discussion here: A few things tech writers frequently say: Videos tedious, topics best when short, people just use Google, and more.
Note that there may be gaps of periodic silence during the presentation where someone is making a comment. In general I try to rephrase the comment, but I don't think I did a great job at it here. At any rate, the discussion here was quite a bit more interesting than the one at the Silicon Valley chapter, especially concerning topic length.
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include the following technical communication topics: Swagger, agile, trends, learning, plain language, quick reference guides, tech comm careers, and certificate programs. I'm interested in information design, API documentation, visual communication, information architecture and findability, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.