What it is
Clickable prototypes (in tools like Figma) that simulate real interactions and navigation, letting stakeholders and users experience a flow without engineering it.
When to use it
During Prototype, when you need to test or communicate a flow with realistic interaction.
Why (value)
Communicates intent far better than static screens, enables realistic usability testing, and de-risks decisions before build.
How to run it
- Design the key screens and states.
- Link them to simulate the flow and interactions.
- Add realistic content where it matters.
- Test with users or demo to stakeholders.
- Iterate on findings.
Inputs and outputs
- Inputs: Screen designs and a prototyping tool.
- Outputs: A clickable prototype for testing and communication.
Time and effort
Medium. Depends on fidelity and scope.
Evidence and limitations
Testing on a prototype yields behavioral signal but is still a proxy for the real product, edge cases, data, and performance differ. Validate critical assumptions on the real build. See Evidence and limitations.
Tips and pitfalls
- Prototype only the flow you need to test.
- Use realistic content for realistic feedback.
- Do not over-polish before validating the concept.
Variations
Low-fi clickable, high-fi interactive, motion prototypes.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Explore related methods
- Wireframing — Lay out structure and content priority without visual design to focus on function.
- High-fidelity mockups — Produce pixel-accurate visual designs that show the real look and feel.
- Usability testing — Watch representative users attempt real tasks to find where the design helps or gets in their way.
