Prototyping

What is Prototyping?

Prototyping is a development method rapidly creating simplified product versions (prototypes) to obtain user and stakeholder feedback. Ranging from hand-drawn sketches to digital interactive mockups, fidelity levels vary. Showing prototypes to actual users reveals design problems before full development, enabling improvement.

In a nutshell: Creating a working model before the real product, testing with users, finding improvement areas before full development.

Key points:

• What it does: Create simplified product versions for validation
• Why it matters: Find problems before full development, reducing rework and development costs
• Who uses it: Designers, developers, product managers, startup founders

Why it matters

New product concepts rarely reach 100% correctness initially. Actual user testing reveals “this feature isn’t needed” or “this feature is missing” discoveries. Running feedback loops before full development creates market-needed products.

Skipping prototyping for direct full development causes major issues late, generating enormous rework costs. Most startups repeat prototyping and user testing, achieving maximum learning with limited budgets. This represents “experiencing failures cheaply before full development”—low-cost validation.

How it works

Prototyping progresses through three fidelity levels: low, medium, and high.

Low-fidelity prototypes are hand-drawn sketches or whiteboard diagrams. Early-stage concepts answer basic questions: “Is this idea feasible?” “Do users accept this workflow?” Minimal information created quickly in hours to days.

Medium-fidelity prototypes are digital tool-created static images or interactive digital mockups. Including color, layout, text close to final products but without detailed animation or complete functionality. Creation takes days to weeks. This prototype level suits user testing and stakeholder sharing.

High-fidelity prototypes are partially developed implementations in programming languages. Including actual interactions, animations, backend connection. Extreme similarity to final products. “Pilot versions” implementing specific features rather than complete development. Takes 1-4 weeks.

Real-world use cases

New smartphone app validation A fintech company developing a new money transfer app created medium-fidelity prototypes (Figma screen transitions) for 20 user tests. Feedback: “confirmation screen too complex,” “notification settings unclear.” Before full development, they modified structure.

Major website redesign pre-validation Publishers proposing new website designs created high-fidelity prototypes, testing with existing users. Through prototyping, “article search function placement” and “navigation menu structure” improvements emerged before full development.

Startup new business validation New ventures needing investment judgments created low-to-medium fidelity prototypes, testing with 100-200 target users before full development. This validates market needs, helping investors judge business viability accurately. Many startups repeat this validation loop before major investment.

Benefits and considerations

Prototyping’s greatest advantage is discovering problems cheaply and quickly, enabling improvement. Even wrong assumptions involve small rework costs at prototype level. Teams/stakeholders specifically imagine “how finished products work,” reducing misunderstandings.

However, overly-perfect prototypes create double work with full development, wasting time/budget. Determining “which fidelity level suffices” is crucial. Selecting test participants carefully matters. Non-target user testing produces unreliable feedback requiring careful sampling.

Related terms

• Wireframing — Pre-prototyping layout determination
• UI Design — Determining prototype visual elements
• Usability Testing — User testing prototypes for feedback
• UX Design — Prototyping’s overall user experience design purpose
• A/B Testing — Multiple prototype comparison validation

Frequently asked questions

Q: Can I reuse prototype code in full development? A: Low-to-medium prototype code typically discards. Prototype goals differ—testing, not full development quality (testing, optimization). However, design knowledge sometimes carries over.

Q: When should I end prototyping and start full development? A: When “user testing achieved satisfaction level” and “major problems resolved.” Avoid perfection; assume “next stages improve” exiting prototyping importantly.

Q: Recommended prototype creation tools? A: Low-fidelity: paper. Medium: Figma/Adobe XD. High: development languages. Tool selection matters less than “creating quickly appropriately-fidelity prototypes.”