INNOVATIONDays to result

Rapid Prototyping Philosophy

Build to think, don't think to build

Problem it solves

stagnant innovation

Best for

Any team or individual developing new products, services, or experiences where the solution cannot be fully specified in advance

Not ideal for

Regulatory environments where prototypes might be mistaken for finished products, or contexts where even rough experiments carry significant safety risks

Overview

Why this framework exists

Rapid Prototyping is the practice of making ideas tangible as quickly and cheaply as possible in order to learn, evaluate, and improve. David Kelley calls it 'thinking with your hands,' contrasting it with specification-led, planning-driven abstract thinking. The philosophy holds that prototyping generates results faster than abstract deliberation because most problems are too complex to think through correctly the first time.

The key insight is that prototypes should command only as much time, effort, and investment as is necessary to generate useful feedback and drive an idea forward. Early prototypes should be fast, rough, and cheap. The greater the investment in a prototype, the more committed its creators become and the less likely they are to profit from constructive feedback. A whiteboard marker taped to a film canister and clipped to a clothespin can catapult a discussion forward as effectively as a precision-engineered model.

Critically, prototyping extends far beyond physical products. Services can be prototyped through role-playing and skits. Software can be mocked up with Post-it notes. Experiences can be prototyped through scenarios, storyboards, and video narratives. The principle remains the same: anything tangible that lets you explore, evaluate, and push an idea forward is a prototype.

Core principles

5 total
  1. The faster you make ideas tangible, the sooner you can evaluate, refine, and zero in on the best solution
  2. Prototypes should be just good enough to generate useful feedback, never more refined than necessary
  3. The greater the investment in a prototype, the less likely its creators will listen to constructive criticism
  4. Prototyping is not about creating working models; it is about giving form to ideas so you can learn from them
  5. Anything tangible that lets you explore an idea is a prototype, including skits, storyboards, and Post-it note mockups

Steps

5 steps
  1. Start with the Cheapest Possible Expression
    Use whatever materials are at hand to make the idea physical. Cardboard, foam, tape, markers, Legos, household objects. The Gyrus surgical instrument prototype was made from a whiteboard marker, film canister, and clothespin. IDEO's first Apple mouse was a deodorant ball in a butter dish.
    Pro tipSet a time limit of minutes or hours, not days. Speed prevents overthinking and encourages multiple attempts.
    WarningDon't start with digital tools or precision manufacturing. High-fidelity materials create the illusion of a finished product and shut down creative exploration.
  2. Define What You Want to Learn
    Each prototype should have a specific learning objective. Pick what aspect of the idea you want to test and achieve just enough resolution to make that the focus. You don't need to prototype everything at once.
    Pro tipUse the phrase 'This prototype is designed to test whether...' to keep each iteration focused on a single question.
  3. Explore Multiple Ideas in Parallel
    Because early prototypes are cheap, build several versions simultaneously rather than refining a single concept. This prevents premature commitment and creates opportunities to discover better ideas at minimal cost.
    Pro tipWhen prototypes are cheap enough, failure becomes learning rather than loss. Encourage the team to build the ideas they are least sure about.
  4. Get Feedback from Real Users
    Eventually take prototypes out into the world to get feedback from intended users. At this stage, surface quality may need slightly more attention so users are not distracted by rough edges, but resist the urge to over-polish.
    Pro tipWatch how people interact with the prototype rather than asking them what they think of it. Behavior reveals more than opinion.
    WarningA Steelcase executive once destroyed a $40,000 foam prototype by sitting on it because it looked too real. Don't make prototypes so polished that people mistake them for the final product.
  5. Iterate Toward Resolution
    Use feedback to generate the next generation of more detailed, more refined prototypes. Each cycle should increase fidelity in the dimensions that matter most while maintaining the learning posture that makes prototyping powerful.
    Pro tipKnow when to say 'enough is enough.' An experienced prototyper recognizes the point of diminishing returns for each iteration.

Checklist

Saved in your browser

Examples

2 cases
Gyrus Surgical Instrument

While developing a nasal surgery instrument, a surgeon used imprecise words and awkward hand gestures to describe wanting a pistol-grip device. After the meeting, a designer grabbed a whiteboard marker, taped it to a 35mm film canister, and attached it to a plastic clothespin that could be squeezed like a trigger. This zero-cost prototype catapulted the discussion forward and put everyone on the same page.

OutcomeThe rudimentary prototype saved countless meetings, videoconferences, shop time, and airplane tickets. It moved the project from vague verbal description to shared physical understanding in minutes.
Mayo Clinic SPARC Innovation Program

IDEO helped Mayo Clinic create a prototyping laboratory embedded in the hospital itself. SPARC operates as part experimental clinic, part design consultancy, where designers, strategists, medical professionals, and patients work together to prototype everything from examination room layouts to electronic check-in kiosks using the See-Plan-Act-Refine-Communicate methodology.

OutcomeSPARC became an ongoing innovation engine within Mayo Clinic, generating continuous improvements to patient experience. It demonstrated that prototyping can be applied not just to products but to the process of innovation itself.

Common mistakes

4 traps
Over-investing in early prototypes
When a prototype is too polished, two things go wrong: mediocre ideas go too far toward realization, and the team becomes psychologically committed to defending their investment rather than learning from feedback.
Prototyping only physical products
Services, experiences, and organizational systems all benefit from prototyping. Use scenarios, storyboards, role-playing, and video narratives. Software interfaces can be mocked up with Post-it notes long before a line of code is written.
Waiting until the idea is fully formed to build
Prototyping is not the step after ideation; it IS a form of ideation. Building a rough model forces decisions that abstract discussion avoids and surfaces problems invisible in the conceptual stage.
Using prototypes to confirm rather than explore
The purpose of prototyping is to learn something new, not to validate what you already believe. If a prototype only confirms existing assumptions, it was probably too polished and too narrow.

Origin story

How this framework came to be

Brown traces the prototyping philosophy back to his childhood Lego experiments and forward through IDEO's founding story. The firm's very first prototype was created when Douglas Dayton and Jim Yurchenco affixed a roller ball from a tube of Ban Roll-on deodorant to the base of a plastic butter dish, creating Apple Computer's first mouse. That spirit of scrappy, improvisational making has remained central to IDEO's identity. The philosophy was further reinforced by Charles Eames's famous response when asked if his iconic lounge chair came to him in a flash: 'Yes, sort of a thirty-year flash.'

Source

Traced to primary
Source · BOOK
Change by Design
Tim Brown · 2019
Open source →

Related frameworks

Browse all Innovation →