Search results

Podcast: How to Create User-Centered Documentation, Interview with Joe Sokohl

Series: User-centered documentation

by Tom Johnson on May 30, 2008
categories: podcasts

Listen here:

In this podcast, Joe Sokohl explains how to create user-centered documentation by contacting, observing, and interviewing users to gather information about what types of information they use and the help deliverables they actually want.

In his experience, Joe found that almost no one used the user manual, but instead wanted quick information for specific tasks. The users hated stand-up training with PowerPoint slides (what the execs thought users needed), and instead wanted hands-on experience with the real system.

Creating user-centered documention requires technical writers to break the standard (and ridiculous) rule of not contacting the user, to get out of their shells and interact and interview others, and to often challenge standards and assumptions from executives. It may be hard, but doing so is essential, because if you end up creating the wrong deliverables, all your efforts to create help may be irrelevant and useless.

In the podcast, Joe recommends a number of books:

For more information on Joe Sokohl, see his blog here. Also, I blogged about this presentation earlier here.

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.

If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.