Deciding what to build first
Before anything gets built, we check whether it should be, then cut the idea to a first release your team can learn from.
“Every stakeholder has a different version of the MVP.”
We pin down who it’s for, what job it does, and which assumption would sink it if wrong. The first release tests that assumption. We prototype where it settles an argument faster than a meeting would, then help build what survives.
Platen: our own prototype, paused once it had answered the question
What we do
- The problem, agreed — The user, the job, and the evidence that matters.
- Scope with the cuts written down — What’s in, what’s out, and why.
- Prototype, then build — Prototypes where they end debates; real builds for what survives.
- Launch and learning plan — Owners, sequence, and the next decisions.
What usually goes wrong
- An MVP that’s really version two with the polish removed.
- Scope that reopens every week because nobody wrote down what was cut.
- A launch that produces no evidence about the question it was meant to answer.
Which MVP decision keeps reopening?
Bring the argument. We’ll help you settle it with evidence instead of another meeting.