Carolyn Stransky

Humanizing Your Documentation

Your documentation isn't for an ideal user; it's for a frustrated human. Here's how to write for them.

Humanizing Your Documentation
#1about 4 minutes

Understanding use case-driven documentation for users

Focus documentation on user goals and what they can accomplish, not just on describing interface elements.

#2about 4 minutes

Shifting documentation earlier in the development lifecycle

Integrate documentation writing from the use case phase of development instead of treating it as an afterthought.

#3about 2 minutes

Choosing inclusive and neutral language in docs

Use precise, neutral, and inclusive language to create a welcoming environment and avoid problematic terms like master/slave or gendered pronouns.

#4about 3 minutes

Removing words like 'simply' and 'easy'

Replace patronizing words like 'simply' or 'easy' with specific, comparative, or absolute descriptions to avoid frustrating users.

#5about 2 minutes

Writing with plain language and avoiding humor

Avoid using humor which is hard to localize, and instead use plain language to make documentation more accessible and easier to read.

#6about 1 minute

How to document common errors effectively

Address common user errors by explaining what happened, why it happened, and what the user should do next to resolve it.

#7about 2 minutes

Overcoming the curse of knowledge in writing

Combat the curse of knowledge by explaining core concepts, avoiding assumptions, and providing a glossary for product-specific terms.

#8about 3 minutes

Writing clear and accessible code snippets

Improve code snippets by avoiding screenshots, using semantic HTML, enabling syntax highlighting, and replacing abstract placeholders with meaningful variable names.

#9about 2 minutes

Structuring docs and setting clear expectations

Maintain clear documentation by adopting a consistent structure and being transparent about your product's limitations and ideal use cases.

#10about 1 minute

Adopting honest, helpful, and human principles

Build trust and improve user experience by grounding your documentation in the core principles of being honest, helpful, and human.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

Related Articles

View all articles
BB
Benedikt Bischof
Humanizing Your Documentation
About the speaker:Carolyn Stransky is a journalist, software engineer, conference speaker and technical writer based in Berlin. This is how she describes herself on her website:Majority of the week, I'm a frontend engineer focused on accessibility, d...
Humanizing Your Documentation
SM
Stephen McKenna
Technical Documentation For Developers
Technical documentation is an old strategy but essential in web development. However, it’s often a neglected part of the software development process. When done well, it can make a huge difference in the usability and quality of a product. But unfort...
Technical Documentation For Developers
DC
Daniel Cranney
The real reason we document our code
The world of software development moves fast. Technology is constantly changing, as are the tools we use with it, and even the role of a programmer is itself constantly in flux. However, some aspects of software engineering are so foundational that w...
The real reason we document our code
BR
Benjamin Ruschin
What Developers Really Need to Create Great Code Demos
Every developer on earth has, at some point, had another developer to thank for a breakthrough, a success, an aha moment they wouldn’t have had without coming across that blog post, that open-source contribution, that reply on socials or that humble ...
What Developers Really Need to Create Great Code Demos

From learning to earning

Jobs that call for the skills explored in this talk.