Start your first help article with one task a user is trying to finish. State the requirements, give the steps in order, and show how to tell whether the task worked. Test the article against the product before publishing it. A short guide that completes one job is a useful starting point; you do not need to document every screen at once.
Getting ready to share your product? Launch your startup on Maidensail when the core experience is ready for new users.
Pick a task from evidence
Look for a question in support conversations, a repeated point of confusion during testing, or a step you have watched someone struggle with. Do not invent a problem simply because a help centre feels incomplete.
The Office for National Statistics guidance on user needs starts with who the user is, what they need to do, and why. It also asks writers to define conditions that show the content has met that need. The context is public statistics, but the planning exercise can be adapted to a product guide.
For a hypothetical invoicing app, that could be:
As an account owner, I need to download last month's invoices so I can send them to my accountant.
The article is finished when the reader can find the export, choose the right period, and recognise the downloaded file. "Explain the reporting screen" is a much less bounded assignment.
Use a title that names the action
Try "Download invoices for a date range" rather than "Reports overview" if the article serves the export task. Use terms that match both the user's question and the interface. If those terms differ, explain the connection early instead of making the reader guess.
Open with a sentence saying what the guide covers. Then put any requirements before the steps: the necessary account role, supported plan, device, or setup. Verify each requirement against the current product. Do not copy an old limitation into a new guide without checking it.
Write the steps while doing the task
Use a test account and non-sensitive sample data. Follow the workflow yourself and record the actual labels in order.
- Give each step one clear action where possible.
- Say where the action happens, especially when a new page opens.
- Describe the expected result at the end.
- Add a screenshot only when it helps someone find or understand something.
- Remove personal data, secrets, and unrelated customer information from any image.
For the invoicing example, the final line might explain where the CSV downloads and which date field the filter uses. Those details need checking in the actual app; they are not universal rules for invoice software.
Do not tell readers to disable protections or share credentials to get around a problem. If a step depends on permissions, explain how to contact the appropriate account owner instead.
Give the reader a route when it does not work
Include a small troubleshooting section for problems you have verified. For example, an empty export might reflect a date filter with no matching records, but do not present that as the only possible cause unless you know it is.
Say what the reader can check safely, then provide the real support route. Ask only for details needed to investigate. A screenshot of an error can be useful; a password, payment card number, or full customer database is not a sensible default support request.
Test the guide with someone new to the task
Give a reader the article and ask them to try the workflow without coaching. Watch where they hesitate or take a different route. Compare the outcome with the completion conditions you wrote at the start.
Fix missing steps and unclear labels before polishing the wording. The ONS guidance also recommends plain language, descriptive headings, and checking for duplicated content. Link an existing explanation when it already answers the question instead of creating a second version to keep current.
When the workflow changes, review the guide alongside the product. The guide to writing release notes users can act on covers how to explain that change publicly.
The takeaway
Choose one evidenced question, write toward a visible result, and check every step in the product. Expand the help centre as you learn what users need, rather than treating its size as a measure of quality.
Ready for people to try what you have built? Launch your startup on Maidensail.
Source note: the user-need and completion-criteria approach is adapted from the ONS content guidance. The invoicing example and product-help checklist are suggested exercises, not measured results or descriptions of Maidensail users.

