Rapid Prototyping

Purpose

Rapid Prototyping turns abstract ideas into tangible artefacts as quickly as possible. The goal is not to build something polished, but to create something testable — a physical or visual representation that lets you learn by making and get feedback before investing significant time or money.

At a glance

• Group size: 2–8
• Duration: 30 minutes
• Difficulty: Low
• Facilitation style: Hands-on making, lightly facilitated
• Setting: Workshop table with craft supplies; can be adapted for digital tools

How to run

1. Frame the question (5 min): What do you want to learn from this prototype? Write a specific hypothesis or question on the wall.
2. Choose the medium (2 min): Paper, cardboard, clay, construction bricks, digital wireframes — pick the fastest option that can answer your question.
3. Build (15 min): Work individually or in pairs. Speed over polish. If it takes more than 15 minutes, you are over-engineering.
4. Share and critique (8 min): Each person/pair presents their prototype in 1–2 minutes. Others provide feedback focused on the hypothesis: "Does this answer the question?"

Materials needed

• Paper, cardboard, scissors, tape, markers
• Optional: construction bricks, modelling clay, pipe cleaners
• Optional: digital wireframing tools (Balsamiq, Figma)
• Timer

Pitfalls & common mistakes

• Perfectionism: Spending too long making it look good defeats the purpose.
• Prototype without a question: If you don’t know what you’re testing, you can’t learn from the result.
• Falling in love with your prototype: It’s disposable by design. Be ready to throw it away.
• Skipping feedback: A prototype nobody tests is just arts and crafts.

Inclusion & accessibility

• Provide multiple media options so participants with different motor abilities can contribute.
• Pair participants who may struggle with physical construction with a building partner.
• Accept verbal or sketch-only prototypes as valid contributions.

Variations

• Storyboard prototype: Draw a 6-panel comic strip instead of building a physical object.
• Role-play prototype: Act out the service or product experience instead of constructing it.
• Digital sprint: Use Figma or Keynote to build a clickable mockup in the same time box.

When NOT to use this

• When the concept is already well-defined and needs engineering, not exploration.
• When stakeholders expect a high-fidelity demo — manage expectations first.
• When the team has no access to any making materials (though even pen and paper suffice).

Source & further reading

• d.school, Stanford University — "Prototype to Test" method card
• Knapp, Jake — *Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days* (2016)
• Brown, Tim — *Change by Design* (HarperCollins, 2009)