The honest prototype
A prototype's job is not to impress. It is to answer the most dangerous open question as cheaply as possible, and sometimes to tell you not to build the thing at all.
Prototypes get a bad reputation from the ones built to sell rather than to learn. A demo engineered to dazzle a stakeholder is a different artifact from a prototype built to find out whether an idea survives contact with reality. We are interested in the second kind.
Find the riskiest question first
Every new product has one question that matters more than the rest — the one that, if answered badly, makes everything else moot. Sometimes it is technical: can this run fast enough? Sometimes it is human: will anyone actually change their behavior to use it? An honest prototype aims the cheapest possible experiment directly at that question.
The best possible outcome of a prototype is sometimes a confident decision not to build.
Cheap to build, cheap to throw away
Honesty here means being willing to discard the code. A prototype that you are too attached to delete has stopped being a prototype and become a foundation you did not choose deliberately. We keep the learning and, often, rebuild the thing properly once we know it is worth building.
Fast, focused, and disposable is not a lack of rigor. It is rigor applied to the one thing that matters: learning the truth before spending real money to find it.
Keep reading
Like how we think about building software?
Get in touch