Evaluating the user experience of documentation -- Podcast with Bob Watson
You can listen to the podcast here:
Here are a few questions we cover during the podcast:
- Should tech writers do user testing and research, or is this product team’s job in designing the product?
- Can’t we just leverage marketing personas for the user research we need?
- How can looking at the market and product angles help clarify user needs and behaviors?
- What kind of knowledge can we leverage from universal design patterns about how users consume docs?
- How do we avoid hasty generalizations from a user sample that’s too small?
- Is it feasible for tech writers to actually do user testing on top of all of their other duties?
- How can you make feedback forms on docs more likely to get responses from users?
- If you collect feedback at major milestones that users complete, how do you avoid just collecting responses from successful users?
- How does Twilio successfully collect info from their users?
- How can you successfully gather metrics that show user success or failure on tasks?
- How can you make your feedback surveys specific to the data so that you get better responses?
For more information about Bob Watson, see his site, Docs by Design.
About 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.