Validation
Find the fastest honest way to learn whether the idea deserves to be built.
Validation is not asking people whether they like an idea. We identify the assumptions most likely to break the product, then design focused tests around behaviour, demand and willingness to change. The goal is confidence to proceed, change direction or stop before the expensive work begins.
Discuss your idea
- 15 years
- Founding, operating and shipping products
- One team
- Strategy, design and engineering together
- One outcome
- A product decision you can act on
Our process
Rigorous enough to reduce risk. Lean enough to keep momentum.
- 01
Map the risks
Separate customer, value, usability, commercial and delivery assumptions, then rank them by uncertainty and impact.
- 02
Choose the evidence
Decide what observable behaviour would strengthen or weaken each assumption before running a test.
- 03
Run the smallest useful test
Use interviews, prototypes, concierge trials or demand experiments sized to the decision—not a theatrical mini-launch.
- 04
Make the call
Turn results into a clear recommendation: continue, revise the thesis, test again or stop.
What you leave with
Useful work, made for the next decision.
- Assumption and risk map
- Research or experiment design
- Prototype or demand test
- Evidence-led recommendation
What excellence means here
Tests are designed to disprove comfortable assumptions, not confirm them.
Interest is separated from behaviour and willingness to commit.
Learning is documented in language the whole team can act on.
Relevant work
See the capability inside real products.
Different products need different combinations of strategy, design and engineering. These cases show how the work connects.
Have a question worth testing?