User Avatar

Alden DeSoto

2y ago

Product teams: Want great user documentation for your product? Here's the single most important step that most people miss. (Yes, even many tech writers miss this.) 1/9

1/9

User Avatar

Alden DeSoto

2y ago

Here's the missing step: Decide what "good" looks like. What's your objective for publishing this article / help center / explainer video / developer documentation / etc ? What results would you ideally like to see? 2/9

2/9

User Avatar

Alden DeSoto

2y ago

Once you're clear on your desired outcome, you'll have a good idea of exactly what needs to be in the article. And once you know that, your article might practically write itself. (More on this in a minute...) 3/9

3/9

User Avatar

Alden DeSoto

2y ago

For a new product, "good" usually = adoption. The user documentation must answer the questions new users will have. It must remove, or significantly reduce the friction to adoption. 4/9

4/9

User Avatar

Alden DeSoto

2y ago

For a mature product with strong adoption, "good" = serviceability. The user documentation must reduce the number of support requests. 5/9

5/9

User Avatar

Alden DeSoto

2y ago

Now that you're clear on what your article needs to accomplish, how might it "practically write itself"? 6/9

6/9

User Avatar

Alden DeSoto

2y ago

Your PRD already has most of the information/use cases/examples/etc that users need to successfully adopt your product. It just needs to be presented in a user friendly format that includes only the information relevant to users. 7/9

7/9

User Avatar

Alden DeSoto

2y ago

Paste your PRD into ChatGPT and ask it to draft your article. Even better, paste it into Docs-writer.ai, which I created for this purpose. Docs-writer.ai is free, you'll get better results, and you won't spend time refining prompts to get what you want. 8/9

8/9

User Avatar

Alden DeSoto

2y ago

To wrap up: Get clear on your objective. Don't skip this step. Your users will thank you and you'll improve product outcomes. 9/9

9/9