Prototyping & Pretotyping

Table of Contents

1. Purpose
2. When to Use
3. What Is It?
4. Workflow
5. Common Patterns
6. Fidelity Ladder
7. Guardrails
8. Quick Reference

Purpose

Test assumptions and validate ideas before investing in full development. Use cheapest/fastest method to answer key questions: Do people want this? Will they pay? Can we build it? Does it solve the problem? Pretotype (test idea with minimal implementation) before prototype (build partial version) before product (build full version).

When to Use

Use this skill when:

• High uncertainty: Unvalidated assumptions about customer demand, willingness to pay, or technical feasibility
• Before building: Need evidence before committing resources to full development
• Feature prioritization: Multiple ideas, limited resources, want data to decide
• Pivot evaluation: Considering major direction change, need quick validation
• Stakeholder buy-in: Need evidence to convince execs/investors idea is worth pursuing
• Pricing uncertainty: Don't know what customers will pay
• Workflow validation: Unsure if proposed solution fits user mental model
• Technical unknowns: New technology, integration, or architecture approach needs validation

Common triggers:

• "Should we build this feature?"
• "Will customers pay for this?"
• "Can we validate demand before building?"
• "What's the cheapest way to test this idea?"
• "How do we know if users want this?"

What Is It?

Pretotyping (Alberto Savoia): Test if people want it BEFORE building it

• Fake it: Landing page, "Buy Now" button that shows "Coming Soon", mockup videos
• Concierge: Manually deliver service before automating (e.g., manually curate results before building algorithm)
• Wizard of Oz: Appear automated but human-powered behind scenes

Prototyping: Build partial/simplified version to test assumptions

• Paper prototype: Sketches, wireframes (test workflow/structure)
• Clickable prototype: Figma/InVision (test interactions/flow)
• Coded prototype: Working software with limited features (test feasibility/performance)

Example - Testing meal kit delivery service:

• Pretotype (Week 1): Landing page "Sign up for farm-to-table meal kits, launching soon" → Measure sign-ups
• Concierge MVP (Week 2-4): Manually source ingredients, pack boxes, deliver to 10 sign-ups → Validate willingness to pay, learn workflow
• Prototype (Month 2-3): Build supplier database, basic logistics system for 50 customers → Test scalability
• Product (Month 4+): Full platform with automated sourcing, routing, subscription management

Workflow

Copy this checklist and track your progress:

Prototyping Progress:
- [ ] Step 1: Identify riskiest assumption to test
- [ ] Step 2: Choose pretotype/prototype approach
- [ ] Step 3: Design and build minimum test
- [ ] Step 4: Run experiment and collect data
- [ ] Step 5: Analyze results and decide (pivot/persevere/iterate)

Step 1: Identify riskiest assumption

List all assumptions (demand, pricing, feasibility, workflow), rank by risk (probability of being wrong × impact if wrong). Test highest-risk assumption first. See Common Patterns for typical assumptions by domain.

Step 2: Choose approach

Match test method to assumption and available time/budget. See Fidelity Ladder for choosing appropriate fidelity. Use resources/template.md for experiment design.

Step 3: Design and build minimum test

Create simplest artifact that tests assumption (landing page, paper prototype, manual service delivery). See resources/methodology.md for specific techniques (fake door, concierge, Wizard of Oz, paper prototyping).

Step 4: Run experiment

Deploy test, recruit participants, collect quantitative data (sign-ups, clicks, payments) and qualitative feedback (interviews, observations). Aim for minimum viable data (n=5-10 for qualitative, n=100+ for quantitative confidence).

Step 5: Analyze and decide

Compare results to success criteria (e.g., "10% conversion validates demand"). Decide: Pivot (assumption wrong, change direction), Persevere (assumption validated, build it), or Iterate (mixed results, refine and re-test).

Common Patterns

By assumption type:

Demand Assumption ("People want this"):

• Test: Fake door (landing page with "Buy Now" → "Coming Soon"), pre-orders, waitlist sign-ups
• Success criteria: X% conversion, Y sign-ups in Z days
• Example: "10% of visitors sign up for waitlist in 2 weeks" → validates demand

Pricing Assumption ("People will pay $X"):

• Test: Price on landing page, offer with multiple price tiers, A/B test prices
• Success criteria: Z% conversion at target price
• Example: "5% convert at $49/mo" → validates prici

...