Write your idea statement, crisply.
Also called: Idea brief · Concept statement · Product hypothesis · One-line pitch
A short, testable articulation of what the product is, who it is for, the problem it solves, and the rough shape of the solution.
One tight paragraph, or five filled boxes: problem, who, solution shape, why now, what success looks like. It turns a spotted opportunity into something the next stages can test. Write it vague and every later stage inherits the fog. There is a worked canvas below.
What an idea statement is
An idea statement is the moment you commit a spotted opportunity to words. It names four things in plain English: the problem you are solving, who has it, the rough shape of the solution, and what makes the moment right. Done well, it fits in one short paragraph and can be read aloud to a stranger who then repeats it back accurately.
The point is not polish. It is to make the idea testable. A vague statement (“a smart device for bakers”) cannot be argued with, researched, or designed against, so it survives every review unchanged and quietly wastes the next three stages. A tight statement makes specific claims that Stage 02 Discover can go and check. If a claim is wrong, you want to find out in week one, not week twenty.
Why vagueness costs you later
- It hides disagreement. Two founders can both nod at “a better proofing solution” while privately picturing completely different products. The fog only clears when someone tries to design it, by which point the disagreement is expensive.
- It can’t be falsified. If the statement makes no specific claim about who, what, or why now, then no research result can ever contradict it. An idea that cannot be wrong cannot be validated either.
- It smuggles the solution in early. A statement that leads with features (“an app-connected box”) freezes a design decision before Discover has earned it. Name the problem first; let the solution shape stay rough on purpose.
A worked idea statement
The cleanest way to write one is to fill five boxes honestly, then read them back as a single paragraph. Here is the proofing box’s, written early, before any validation, so you can see the shape of a good answer rather than a generic template.
Read those five boxes back as one paragraph and you have the statement. Notice the solution shape stays rough on purpose: it names ceramic, heat and a knob, but not the heater wattage, the bill of materials, or the certification. Those are later-stage answers. The statement’s job is to be specific about the problem and honest about how little of the solution is yet decided.
Weak statement vs strong statement
The same idea, written two ways. The weak version feels safe because it commits to nothing. The strong version makes claims you can go and test, which is exactly what makes it useful.
“A smart, premium device that helps home bakers get better results in the kitchen, using the latest technology to make baking easier and more reliable for everyone.”
- No named problem, no named person.
- “Everyone” is nobody specific.
- Leads with the solution, and a vague one.
- Nothing here research could ever disprove.
“Serious home bakers lose overnight proves in cold UK kitchens that drift between 14°C and 19°C. A heated ceramic box that holds 26°C overnight, no app, around £149, would let them stop binning loaves.”
- Specific problem with a number on it.
- A person you could go and find.
- Solution shape rough but committed.
- Every claim is checkable in Discover.
The weak statement cannot be wrong, which is precisely the trouble: it gives the next stage nothing to push against. The strong one makes four falsifiable claims, and any of them being wrong is cheap to learn now and ruinous to learn after tooling.
How it fits the bigger picture
Write Idea Statement is activity 01.02, the second activity of Stage 01 Idea. It builds on the opportunity you spotted in 01.01 and feeds straight into set expectations (01.03), where you agree what this idea is allowed to cost in time and money before it earns more. The statement is the thing every later stage measures itself against.
What it can do
It turns a loose hunch into a single testable paragraph the whole team can hold a decision against. When someone proposes a feature in Stage 06 Design, you can ask whether it serves the problem the statement named, and the statement answers. It also makes disagreement visible early, while it is still free to resolve.
What it can’t do
It can’t tell you whether the idea is any good. That is the job of Stage 02 Discover and Stage 04 Evaluate, which go and test the claims the statement makes. The statement is a clear hypothesis, not a verdict. Write it to be proved wrong cheaply, not to be defended.
See the full 10-stage process →
Try it yourself
Fill the five boxes in fifteen minutes: problem, who, solution shape, why now, what success looks like. One sentence each, plain English, no buzzwords. Then read them back as a single paragraph and ask: “could a stranger repeat this and could research prove any of it wrong?” If either answer is no, it is still too vague. Rewrite the box that failed.
Or run the guided version. The Free Sprint walks you through the same four questions and hands back a tightened statement. Start the Free Sprint →
Your idea-statement checklist
Project notes: the first paragraph
▸ From the notebook · optional reading
Sitting with Dan and Anna Hartley in Stockport to write the proofing box down for the first time, before a single number was validated.
3 min read · click to open
Dan opened with the sentence most ideas open with: “A smart proofing gadget for keen home bakers.” It sounded fine and meant almost nothing. I asked them to fill five boxes instead, out loud, and I wrote them on the whiteboard in their Stockport kitchen.
Where it got specific
The problem box was the one that earned its keep. Anna said it plainly: her own kitchen sits at 15°C overnight in winter, and a prove that should hold near 26°C just stalls. We pushed on the cost of a failed prove and landed on roughly twelve hours and a few pounds of flour, binned, every time it went wrong. That number made the problem real in a way “better results” never had.
The who box mattered next. “Home bakers” was too broad, so we narrowed it to the serious overnight prover who already follows the Sourdough School, not the once-a-month dabbler. Different person, different willingness to pay.
The argument worth having early
The solution-shape box is where Dan and I disagreed, which was the useful bit. He wanted to write “app-connected, temperature graph on your phone” into the statement. I pushed back: “That is a design decision, and we have not earned it. Keep the shape rough. No app, around £149, a knob and a small display, and let Discover tell us if that is wrong.” He humoured me. Six months later the same no-app line held all the way to launch.
We ended with one paragraph that a stranger could repeat back. It cost us forty minutes. Every later stage, all the way to UKCA work and BS EN 61010, checked itself against that paragraph. Forty minutes for a compass that lasted the whole project is not a close call.
— Idea stage, project notes, 2026
— Next in Idea → Set expectations