Free tool · no data sent
From a vague need to a scoping note.
Six steps, the questions I ask in client workshops. At the end, a clear, shared note: what we build, for whom, why — and what we leave out.
The six steps
Each step comes with a tip: why the question matters, and the usual trap.
- 1
The problem
Describe the current situation and what it costs. No solution yet: that comes later.
- 2
The users
Two or three profiles are enough: who they are, what they want, what holds them back.
- 3
The goals
One goal, one indicator, one target. If it cannot be measured, we will not know whether the project worked.
- 4
The scope
Scope protects the project: what is left out matters as much as what is in.
- 5
The features
Describe each need from a user’s point of view, then rank it. A successful first version often fits in four or five must-haves.
- 6
Risks and questions
Write down the assumptions to check and the decisions to make with the client before development starts.
An analyst’s eye, built in
The tool reviews your scoping and flags inconsistencies, the way I would when reviewing a requirements document.
- A goal without a measurable indicator.
- More than half of the user stories marked as must-haves.
- A user profile that appears in no user story.
Your answers stay in your browser. Nothing is sent to or stored on the server.