Rapid Prototyping¶

Why It Matters¶

Abstract reasoning about ideas keeps you trapped in your own mental model. Prototyping forces contact with reality, which is the only reliable source of surprising information. The faster you can make ideas tangible and testable, the faster you discover which assumptions are wrong. This transforms "being right" from a prerequisite to an outcome of iteration.

The Key Move¶

For any idea, ask: "What's the cheapest, fastest way to make this tangible enough to learn from?" Create that artifact (sketch, mockup, script, physical model, role-play) and expose it to the relevant reality (users, materials, constraints) within hours or days, not weeks. Treat prototypes as disposable learning tools, not precious creations. When feedback reveals flaws, discard and rebuild rather than defending and refining.

Classic Application¶

IDEO's early work used foam core, cardboard, and hot glue to prototype physical products in a single day. For a medical device, they might build a non-functional physical mockup to test whether doctors could hold it properly, separate from whether the electronics worked. This reveals ergonomic failures immediately rather than after expensive tooling.

Surprising Application¶

Testing career transitions. Instead of deliberating endlessly about whether to switch fields, rapid prototyping suggests: find the fastest way to do the actual work. Want to try consulting? Offer to do a small project for free. Considering teaching? Run a single workshop. The prototype is a concrete experience of the work itself, not research about the work. You learn whether you like the reality, not whether you like the idea.

Failure Modes¶

Prototyping the wrong fidelity - building too high-fidelity when you need to test basic concepts (wasteful), or too low-fidelity when you need to test real performance (uninformative). Confusing prototypes with pilots - prototypes are meant to be discarded, pilots are meant to become products. Testing with the wrong reality - showing users polished mockups invites aesthetic feedback, not functional feedback. Over-iterating on a prototype instead of rebuilding from scratch with new insights.

Go Deeper¶

Schrage, Serious Play: How the World's Best Companies Simulate to Innovate; Kelley & Kelley, Creative Confidence, Chapter 5