Skip to content
NewTemplates & toolkits are on the way — join the waitlist
Hecham Gazhi

UX Design · Lesson 09 / 13

Prototyping

What prototypes are for, how to choose the right fidelity, the main prototyping methods and tools, how to build a prototype for testing, and the mistakes that waste time.

5 min read · 5 quiz questions

What is a prototype?

A prototype is a simulation of a product or feature that people can interact with before it's built. It might be a stack of paper screens, a clickable set of wireframes in Figma, or a coded experiment.

The purpose of a prototype is learning. It answers a question — Do people understand this flow? Which of two concepts works better? Is this animation clear? — at a fraction of the cost of building the real thing.

A useful mindset: "If a picture is worth a thousand words, a prototype is worth a thousand meetings." Showing something people can click ends debates that discussion alone can't.

Why prototype?

  • Test with users before investing in development.
  • Communicate ideas to stakeholders and developers more clearly than static screens.
  • Explore interactions — transitions, gestures, micro-interactions — that are hard to describe.
  • Compare alternatives side by side.
  • Find technical questions early — developers can see what's being asked.

Fidelity: match it to your question

Fidelity describes how close a prototype is to the final product. It has several dimensions — visual detail, content realism, interactivity, and data — and they don't all have to be high at the same time.

Question you're askingSuitable prototype
Does this concept make sense at all?Paper prototype or storyboard
Can people navigate this flow?Clickable mid-fidelity wireframes
Do people understand the content and labels?Mid-fidelity with real copy
Does the visual design communicate trust and hierarchy?High-fidelity static or clickable screens
Does this complex interaction feel right?High-fidelity with animations, or coded prototype
Does it work with real data or at real speed?Coded prototype

Common mistake: Building high fidelity too early. A polished prototype takes longer to make, makes the team reluctant to throw it away, and makes test participants hesitant to criticise something that looks finished.

Prototyping methods

Paper prototyping

Screens are sketched on paper or cards. During a test, a team member plays "the computer" and swaps papers as the participant "taps". It's very fast, needs no tools, and makes everyone comfortable suggesting changes.

Clickable prototypes

Screens in a design tool (Figma, Sketch, Adobe XD, Framer) are linked with hotspots so people can tap through a flow. This is the most common type for usability testing.

Wizard of Oz

The user interacts with what looks like a working system, but a human is secretly doing the work behind the scenes — for example, typing chatbot replies. Great for testing AI or automation ideas before building them.

Coded prototypes

Built with real code, often quick and disposable. Useful when you need real data, complex logic, performance, or device features like the camera.

Video and storyboard prototypes

A short video or comic strip showing how a product would fit into someone's life. Useful for testing value propositions before designing screens at all.

Prototyping in Figma

Figma is the most widely used tool for interactive prototypes. Key concepts:

  • Flows and starting points — define where a prototype begins; one file can contain several flows.
  • Connections (hotspots) — link an element to another frame with a trigger (on click, on drag, while hovering, after delay).
  • Smart animate — animates layers with matching names between two frames, for smooth transitions.
  • Overlays — show modals, dropdowns and toasts on top of the current screen.
  • Scroll behaviour — fixed headers, horizontal carousels, sticky elements.
  • Interactive components — variants that change state (a toggle, a checkbox) wherever the component is used.
  • Variables and conditionals — store values (like items in a cart) to build more realistic logic.

Building a prototype for a usability test

  1. 1Start from the test tasks. Prototype only the paths those tasks need — not the whole product.
  2. 2Use realistic content: real product names, prices, dates and the participant's likely data.
  3. 3Make the expected path work, and decide what happens when people click elsewhere (a gentle "not available in this prototype" or nothing).
  4. 4Add key feedback: loading states, success messages, errors you want to test.
  5. 5Test the prototype yourself on the real device size (phone prototypes on a phone).
  6. 6Run a pilot session with a colleague and fix anything broken before real participants arrive.

Example · A focused prototype

A team testing a new money transfer flow prototyped only five screens: choose recipient, enter amount, review, confirm with PIN, success. The home screen was a static image with one working button.

It took a day to build, and five test sessions revealed that people didn't notice the transfer fee on the review screen — a problem fixed in an hour, long before development started.

Good prototyping habits

Do

  • Define the question before you build.
  • Build the minimum needed to answer it.
  • Prototype on the real device size.
  • Keep prototypes organised and clearly labelled as prototypes.

Don't

  • Polish everything before testing anything.
  • Fall in love with a prototype — it's meant to be thrown away.
  • Let stakeholders think a prototype means the feature is nearly built.
  • Leave broken links in the paths you'll test.

Key takeaways

  • Prototypes exist to learn — each one should answer a specific question.
  • Match fidelity to the question; low fidelity is often enough and gets more honest feedback.
  • Methods range from paper and Wizard of Oz to clickable designs and coded prototypes.
  • For testing, prototype only the paths your tasks need, with realistic content.
  • Prototypes are disposable — don't fall in love with them.

Exercise

Paper prototype a mobile feature

  1. Choose a feature, e.g. "split a restaurant bill with friends".
  2. Sketch 5–7 screens on index cards.
  3. Ask a friend to complete the task while you swap cards as they "tap".
  4. Note every moment they hesitate or tap the wrong place.
  5. Redraw the problem screens and test again with someone else.

Test yourself

Prototyping quiz

5 questions. Score 70% or more to complete the lesson.

  1. 1.What's the main purpose of a prototype?
  2. 2.You want to test whether a navigation flow makes sense. What's usually enough?
  3. 3.In a Wizard of Oz prototype…
  4. 4.Which Figma feature animates matching layers between two frames?
  5. 5.When preparing a prototype for a usability test, you should…