ISLE88 / DESIGN / 3 MIN
Define the finish before the first screen.
A short acceptance check makes a vague feature much easier to design and build.
Start with a decision.
“Improve the dashboard” is difficult to finish. “Help a kitchen owner spot dishes with missing costs before setting a price” gives the work an audience, a task, and a consequence. A useful brief names all three.
Describe the last useful state.
Write what a person should be able to see or do at the end. For example: the owner can distinguish a complete cost from an estimate, open the ingredient that needs attention, and return to the dish without losing changes. This sentence becomes the first acceptance check.
Include the awkward cases.
Now ask what happens with no ingredients, a failed save, a missing price, and a slow connection. These states often decide whether the main path can be trusted. Agree which ones belong in this piece of work before adding more screens.
Try this with your next brief.
Complete this sentence: “When [person] needs to [task], they can [observable result]. We will check it by [specific action].” If the last part is hard to write, the scope probably needs another conversation.
MORE FROM THE STUDIO
Choose your subjects.
Occasional notes on design, development, AI, and learning. Confirm your email to subscribe.
Get Field Notes