Prototype to think, not to finish

Build or sketch something rough specifically to learn what you actually want.

Why it works

Abstract plans feel complete because the gaps are invisible — you can’t see what you don’t know yet. A rough prototype makes the assumptions concrete and the gaps visible. It turns a thinking problem into a seeing problem, where the feedback loop between intention and output runs in minutes rather than weeks.

How to do it

1. Build the ugliest version that could still test the core assumption — skip everything else.
2. Show it (to yourself or others) and note the first three things that feel wrong.
3. Treat each "wrong" as a better question, not a failure, then iterate.

Evidence

Rapid prototyping is foundational to design thinking methodology; qualitative studies and practitioner accounts consistently find earlier, rougher prototypes accelerate learning. Controlled comparisons to non-prototyping approaches are sparse. Dow et al. (2010) supply the controlled evidence: creating several prototypes in parallel produced better-rated design outcomes, more divergent exploration, and higher self-efficacy than refining a single one. (clinical)

Strong in design/engineering contexts; evidence in knowledge-work and writing tasks is more anecdotal.

Sources

• Dow, S. P., Glassco, A., Kass, J., Schwarz, M., Schwartz, D. L., & Klemmer, S. R. (2010). Parallel prototyping leads to better design results, more divergence, and increased self-efficacy. ACM Transactions on Computer-Human Interaction, 17(4), Article 18.

Common mistake

Polishing the prototype before others see it — which reintroduces the perfectionism that prototyping is meant to bypass, and signals that feedback is optional.