Real concept, no proof
There is a genuine idea and no artefact. Every conversation restarts from explanation, and feedback stays abstract because there is nothing specific to disagree with.
Pattern 03 · Founder product
When the concept is real but there is nothing to touch.
The direction is clear in your head, but stakeholders cannot engage with a description. The decision keeps getting deferred because there is nothing concrete to react to.
Prototype first, on real data
Build the smallest working thing that produces a real result from real inputs. Not a mockup - something that runs, so the discussion moves from whether it makes sense to whether the output is right.
The conversation gets specific
Stakeholders react to output instead of description, and the next iteration is driven by observed use rather than speculation about it.
Principles
How I keep it honest.
Ship enough to learn
The goal is the fastest honest signal, not a finished product. Enough to be judged, not enough to be precious about.
Real inputs only
A prototype fed on tidy sample data proves nothing. It runs against the actual messy documents or it does not count.
Leave an iteration path
Built so the next layer can be added without a rewrite, and so throwing it away is cheap if the signal says to.
Next step
Get in touch