Build for the moment of need
- State the prerequisite and outcome. For example: “You need access to a workspace; by the end you will have invited a teammate.” Use a task and prerequisites that match your product.
- Capture the shortest real path with safe sample data. Include the confirmation or resulting state, not just the last click.
- Write one action per step and explain the consequence when it is not obvious. Use the product’s actual labels.
- End by telling the reader how to return to their own account and repeat the task. If permissions or settings can change the path, explain the relevant difference in the surrounding article.
Example: invite a teammate
In a fictional product, the reader’s goal is to invite a colleague to a workspace. Start on the workspace settings screen, show where to open the team area, enter a fictional address, choose a role, and show the invitation’s pending state. The result is “an invitation was sent,” not “the colleague has joined”: those are different states and can require different follow-up. The article around the demo should answer the questions a recording cannot settle for every reader:- Before starting: What access or information does the reader need? Where do they start?
- At the decision: How should they choose a role in their own workspace? Link to your product’s actual permissions reference.
- After the last step: Where can they check a pending invitation, and what should they do if the recipient cannot join?