Put the right things into words.

01 / Write a brief that can guide decisions.

Use this structure: “For [audience], create [experience] so they can [outcome]. The first version includes [three essentials]. It does not include [out of scope].” Add an example of a real task.

• Name a specific audience, not “everyone”.
• Describe the task rather than a list of technologies.
• Use original sample content without private information.

02 / Choose the smallest useful version.

List the user’s steps from arrival to success. Keep only the steps necessary for the first result. Mark everything else as later.

• Write one primary workflow.
• Define success in observable terms.
• Specify empty, loading, validation and failure states.

03 / Write acceptance criteria.

For a booking idea: “A visitor can select an available date. Unavailable dates cannot be selected. A failed request shows an actionable message.” These are requirements for a future app, not claims about current functionality.

• State who performs each action.
• Include access and privacy restrictions.
• Check mobile and keyboard interaction, not just appearance.