1. Choose a distinct buyer problem
Collect recurring questions from sales, support and product teams. Choose a problem that differs from the general value proposition, then state the decision the page should help a reader make.
Do not create a URL for every small interface control. A separate page is justified when the use case, decision questions and supporting evidence are meaningfully distinct.
2. Trace inputs through to an outcome
Document the starting state, required inputs, main steps, expected result and what the user does afterwards. Note dependencies such as permissions, imports, integrations or administrator choices.
Have the product owner verify every step. If outcomes vary, explain the conditions instead of presenting an ideal case as the normal result.
3. Use evidence without changing what it means
Capture the real interface in a safe test environment with fictional data. Remove personal or customer information, but do not alter labels or controls in a way that suggests a different product.
Use a clearly labelled illustration to explain a relationship or data flow. Keep conceptual art distinct from evidence of the interface.
4. Match the call to action to the next step
Link to a demonstration when the buyer needs to see the workflow, documentation for a technical review, or a conversation when scope needs discussion.
Check that the button promise matches its destination. Do not describe an enquiry form as account activation or promise an unverified response time.
| Page element | Check |
|---|---|
| Audience | Who performs the task and who decides? |
| Workflow | Which inputs and roles are required? |
| Evidence | Does the image show a real product version? |
| Next step | Does the CTA match its destination? |