Neural Sync Active
Learning Objectives
Registry Synced
Learning Objectives
420 words
2 min read
Reading compass
Now · 1. The Prototype Phase
Learning Objectives
- Understand rapid prototyping principles
- Create low-fidelity and high-fidelity prototypes
- Plan prototyping for learning
- Week 4: Selected ideas to prototype
- Willingness to build imperfectly
1. The Prototype Phase
Purpose: Make ideas tangible to learn, test, and improve. Prototypes answer specific questions, not demonstrate finished solutions.
Mindset: Build to think. A prototype is worth a thousand meetings. Fail early to succeed sooner.
2. Fidelity Spectrum
| Fidelity | Example | Purpose | Cost | Time |
|---|---|---|---|---|
| Low | Paper sketch, storyboard | Test concept, flow | Very low | Minutes |
| Medium | Wireframe, cardboard model | Test layout, interaction | Low | Hours |
| High | Clickable prototype, 3D print | Test usability, feel | High | Days |
Rule: Start with LOWEST fidelity that answers your question. Iterate quickly.
3. Prototyping Methods
Paper Prototyping: Sketch screens/interfaces on paper. Test by having user "tap" paper while designer switches sheets.
Role Playing: Act out a service experience. Helps identify pain points in service design.
Storyboard: Visual sequence showing how user experiences solution over time.
Wizard of Oz: Prototype appears functional but is actually operated by a human behind the scenes. Tests user response before building real system.
Physical Prototypes: Cardboard, foam, clay, Lego for physical products. 3D printing for more refined versions.
4. Prototyping for Learning
Before prototyping, ask: What do we want to learn? What question are we answering? What's the riskiest assumption we need to test? Prototype the RISKIEST assumptions first.
Q1: What is the purpose of prototyping in design thinking?Not to build a finished solution, but to learn. Prototypes make ideas tangible, test assumptions, get user feedback early, and improve iteratively. Q2: Why start with low-fidelity prototypes?Low cost and fast to create (minutes vs days). Encourages iteration (easy to throw away). Users give more honest feedback on rough prototypes (they see them as changeable). Q3: What is the Wizard of Oz prototyping method?A human operates the prototype behind the scenes to simulate functionality. Tests user response and validates demand before building the actual system. Q4: What is a storyboard prototype?Visual sequence of how a user experiences the solution over time. Shows context, actions, and emotions. Tests the narrative flow and identifies missing steps. Q5: What is "prototyping the riskiest assumption"?Identify the assumption that, if wrong, would kill the project. Build a prototype specifically to test that assumption first. Example: assuming people want a service - test with a landing page before building. Join Discord PreviousIdeate PhaseNextTest Phase