INNOVATIONDays to result

Rapid Prototyping

Build to think, fail fast, and iterate quickly -- a rough prototype is worth a thousand words

Problem it solves

test ideas quickly

Best for

Teams and individuals who need to test ideas quickly, communicate concepts persuasively, or break through analysis paralysis by making abstract ideas concrete

Not ideal for

Situations requiring regulatory compliance or safety-critical validation where rough prototypes could be misleading or dangerous

Overview

Why this framework exists

Rapid prototyping is the practice of building quick, rough, tangible representations of ideas to learn, communicate, and iterate. The Kelleys position it as the antidote to analysis paralysis and the knowing-doing gap. Rather than debating ideas in the abstract, you build something concrete enough for people to react to -- even if it is made of paper, foam core, and tape. The approach embodies the principle that an experiment ending in failure is not a failed experiment, as long as constructive learning is gained. Thomas Edison maintained that the real measure of success is the number of experiments that can be crowded into twenty-four hours. Rapid prototyping treats every iteration as a learning opportunity: the faster you find weaknesses, the faster you can improve. The key rule is Boyle's Law: never go to a meeting without a prototype.

Core principles

7 total
  1. Build to think -- making ideas tangible reveals insights that analysis alone cannot
  2. Be quick and dirty -- explore a range of ideas without becoming too invested in only one
  3. An experiment ending in failure is not a failed experiment as long as constructive learning is gained
  4. The faster you find weaknesses during an innovation cycle, the faster you can improve what needs fixing
  5. Early failure is crucial to success in innovation
  6. Boyle's Law: never go to a meeting without a prototype
  7. A compelling prototype doesn't need high production value -- it can make up in authenticity what it lacks in polish

Steps

4 steps
  1. Choose your prototype format based on what you need to learn
    Match your prototype to your question. Paper models test form and layout. Role-play tests service interactions. Video prototypes communicate experience and emotion. Foam and cardboard test ergonomics and size. The medium should be whatever helps you learn fastest, not whatever looks most polished.
    Pro tipWhen testing a new app feature, print an oversized phone screen on paper, cut out a window, and have someone act out the interaction behind it -- this was literally how the Elmo's Monster Maker dance feature was prototyped and approved in under an hour.
  2. Build the roughest version that communicates your idea
    Use whatever materials you have on hand: paper, tape, foam core, existing products you can modify, digital mockups, or even acted-out scenarios. The goal is to make the idea concrete enough that people can react to it, not to create a finished product.
    Pro tipTime-box your first prototype to one hour or less. Constraints force creativity and prevent over-investment in a single direction.
    WarningResist the perfectionist urge to polish before testing. A rough prototype tested with real users is infinitely more valuable than a beautiful prototype that sits on your desk.
  3. Test with real users and gather feedback
    Put your prototype in front of the people who would actually use the final product or service. Watch how they interact with it. Note where they get confused, what excites them, and what they ignore. Ask open-ended questions rather than leading ones.
    Pro tipPay more attention to what people do with your prototype than what they say about it. Behavior reveals truth that words often obscure.
  4. Iterate based on learning, not opinion
    Use the feedback and observations from testing to inform your next iteration. Adapt, pivot, or double down based on evidence. Then build the next prototype and test again. Each cycle should take days, not months.
    Pro tipEdison's approach: crowd as many experiments as possible into the available time. The more cycles you complete, the better your final solution will be.
    WarningDon't iterate endlessly on the same concept. If multiple rounds of testing show fundamental flaws, be willing to pivot to an entirely different approach rather than polishing a broken idea.

Checklist

Saved in your browser

Examples

2 cases
Elmo's Monster Maker dance feature

With an hour before a conference call, Adam Skaates printed an oversized iPhone image on a plotter, mounted it on foam core, cut out the screen area, and stood behind it to act as Elmo while a colleague simulated touch interactions via webcam. The crude one-take video was sent to Sesame Workshop minutes before the meeting.

OutcomeThe quick prototype was fun and persuasive. The feature -- which had been in danger of being cut -- was approved. Today it is a key feature in the shipped Elmo's Monster Maker app.
Steelcase Node chair -- 200+ prototypes

To reinvent the classroom chair, the team progressed through paper-and-tape models, plywood attached to existing chairs, foam shapes, 3D-printed parts, steel mechanisms, and full-size production models. They brought prototypes to colleges for student and professor feedback at every stage.

OutcomeThe Node chair -- with swivel seat, adjustable surface, casters, and tripod base -- launched in 2010 and is now used in eight hundred schools and universities worldwide. The relentless prototyping process ensured every detail was validated through real use.

Common mistakes

3 traps
Over-investing in the first prototype
Spending too much time and resources on a single prototype makes you emotionally and financially invested in that direction, even when feedback suggests you should pivot. Quick and dirty prototypes make it easy to throw away ideas that don't work.
Using words when you should be building
Talking about ideas in meetings is far less persuasive and informative than showing a prototype. The Elmo's Monster Maker team's crude video prototype was more convincing in minutes than any verbal pitch could have been.
Treating failure as the end rather than a lesson
Edison's thousand unsuccessful lightbulb attempts were not failures -- they were experiments that eliminated possibilities and provided learning. The Wright brothers chose remote Kitty Hawk partly to experiment without media scrutiny. Both understood that early failure is crucial to eventual success.

Origin story

How this framework came to be

The practice emerged from decades of IDEO product development work, where teams routinely build hundreds of prototypes per project. Dennis Boyle, one of IDEO's master prototypers, crystallized the philosophy into Boyle's Law: never go to a meeting without a prototype. The approach was validated across countless projects -- from designing the first Apple mouse to reimagining classroom furniture. The Steelcase Node chair project alone involved over two hundred prototypes, progressing from paper-and-tape models to plywood components to foam carvings to 3D-printed parts to full-size production models.

Source

Traced to primary
Source · BOOK
Creative Confidence
Tom Kelley & David Kelley · 2013
Open source →

Related frameworks

Browse all Innovation →