01 · ISOLATE
Name the risky assumption
Choose the product, workflow, model, or feasibility question that matters most to the investment.
Prove · working prototypes and evidence
Show what it takes to make the idea work.
Build a small, working version of the idea and put it in front of the people it affects. Learn whether it helps, whether people will use it, what the technology needs, and how the cost changes as the work grows.
The problem
The idea is promising. The important assumptions are still guesses.
The model may not be reliable enough. The workflow may not fit how people actually work. Users may not trust the answer or change what they do. Those questions get more expensive once the team has committed to a full program.
I define the question with the team, build the smallest useful version that can answer it, and put the workflow in front of real users. The work ends with evidence, tradeoffs, and a clear call on what to do next.
How the engagement works
Build for the decision, not for the demo.
02 · BUILD
Make the smallest useful version
Implement only what the team needs to test the question with enough realism to learn.
03 · TEST
Put evidence in the room
Observe users, document the findings, and decide whether to proceed, change direction, or stop.
Other ways to work
A prototype may follow a strategy decision or expose an engineering capability gap.
A useful first conversation
Which assumption is too important to leave on paper?
Bring the idea, the open question, and what the team would need to believe before making a larger investment.
Find your starting point