About
Acceptance is clearer when a person can connect a request to a result they can actually see.
Start with the task
Name the user task, the condition that matters and the result that would make the task complete.
Follow more than one path
A normal journey may work while a boundary or interruption does not. Keep each expected outcome visible.
Leave a reviewable record
A decision belongs to people who can inspect the criterion, observed result and unresolved work.
Story
A tidy scenario can still miss the real decision. The useful question is what the user should be able to observe.
Contributors
Clear credit belongs to the people who wrote, checked and challenged a guide.
Roadmap
Keep the next useful question in view as testing moves from a brief to a release conversation.
Timeline
Move from the first acceptance question to a reviewable decision without losing the path between them.
Contact
For a difficult page, use the topic feedback control. Do not include confidential product material.