02 · Product Management
From Vision to Prototype
Turn an approved vision into something real customers can react to, and find out what they actually want before engineering spends the budget.
The most expensive way to test an idea is to build it. Too many teams jump straight to engineering and learn what customers actually wanted only after the money is spent.
Signs your team needs this
- A big build is about to be greenlit on conviction rather than evidence.
- The team believes in a concept but hasn't put it in front of a customer yet.
- A past launch missed because customers wanted something different from what was built.
- Research happens, but the results arrive after the decisions are made.
- Leaders want proof before committing the budget.
How it works
This is a working engagement, not a deliverable handed over from the outside. We guide your team as they do the work, so what gets built is something they understand, own, and can keep running after we leave.
Surface the riskiest assumptions
The team lists everything that has to be true for the vision to work, then ranks those assumptions by how much is riding on them and how little they actually know. The top of that list is where testing starts.
Choose the lightest test
A concept, a flow, or a clickable mockup: we help the team pick the cheapest artifact that can answer the riskiest question. Often that's far less than people expect.
Build it themselves
We don't build the prototype for you. We coach your team as they do it, including how to use AI-assisted tools that now turn a written idea into something clickable in days rather than quarters.
Plan the validation
Before anyone talks to a customer, the team decides who to talk to, how to ask without leading, and what result would change their mind. Success criteria are written down first, so the evidence can't be explained away later.
What your team walks away with
A prototype they built
Something customers can see and react to, made by your team so they can keep iterating on it after we leave.
A prioritized assumption list
The beliefs your plan depends on, ranked by risk, so the team tests what matters most first.
A lightweight validation plan
Who to test with, what to ask, and clear success criteria agreed before the first conversation.
Why we work this way
Nobody confides in a clipboard. People react honestly to something they can touch.
Ask customers about an idea and you'll hear what they think you want to hear. Put a prototype in their hands and you'll see what they actually do. That's the central idea of Jason's book, and it's why this engagement is built around making the idea real enough to react to, as early and as cheaply as possible.
See it in practice
Our First Paycheck case study follows this process end to end: hypotheses written before any screens, a clickable prototype built with AI assistance, metrics defined from the first release, and two rounds of revision driven by what reviewers and testers told us.
Teams with a vision or concept they believe in but haven't yet put in front of customers, or leaders who want evidence before greenlighting a big build.
The vision itself isn't settled yet (start with a Product Vision Sprint), or you're looking for an agency to build production software.
Common questions
How polished does the prototype need to be?
Only as polished as the question requires. A rough concept can test whether a problem matters; a clickable flow can test whether people understand the solution. Over-polishing early is one of the most common ways teams waste time.
Do we need designers and engineers on the team?
They help, but they aren't required. With today's AI-assisted tools, a product manager can build a credible clickable prototype. We'll shape the team around the question you're trying to answer.
How many customers do we need to talk to?
Fewer than most teams think to spot the biggest problems, and enough to see a pattern rather than a single opinion. The validation plan sets this up front so the number isn't decided after the fact.
Is it remote or in person?
Either. Prototype testing in particular works very well remotely.
Working on a hard product problem?
Every engagement starts with a conversation about your customers, your team, and what you're trying to achieve. If From Vision to Prototype isn't the right shape, we'll say so and help you find what is.
Start a conversationThe thinking behind this work is in Jason's book, Nobody Confides in a Clipboard.
Other ways to work together
- Product Vision SprintProduct Management
- Backlog to RoadmapProduct Management
- Leading with AuthenticityLeadership Coaching