The Fidelity Spectrum: Lo-Fi vs Hi-Fi Prototyping | Interaction Design

What Is a Prototype?

A prototype is a preliminary representation of a design used to explore ideas and test them with users before committing to full implementation. Two defining characteristics:

They exist on a fidelity spectrum, from rough paper sketches to fully interactive digital mockups.
They are disposable — they exist to learn from, not to become the shipped product. The cost of throwing away a prototype is the cost of the learning it enabled, not the cost of rework.

Low-Fidelity (Lo-Fi) Prototypes

Lo-Fi prototypes use inexpensive, non-technical materials: paper, card, sticky notes, whiteboard sketches. They are rough, clearly incomplete, and obviously not the final product.

Key characteristics:

Quick and cheap to create, modify, and discard — you can iterate several designs in a single afternoon.
Test overall structure, navigation, and concept — not visual detail, colour, or precise layout.
Encourage open, unintimidated feedback: users criticise a rough sketch far more freely than a polished screen because they do not feel they are criticising “finished” work that someone spent weeks building.
Can be created and changed within a single design session, enabling rapid co-design with users present.

When to use Lo-Fi:

Early in the UCD cycle, when the design direction is still unsettled.
When exploring multiple alternative concepts and you need quick comparative feedback.
When you want users to focus on structure and flow, not visual polish.

High-Fidelity (Hi-Fi) Prototypes

Hi-Fi prototypes are interactive digital mockups that closely resemble the final product in look-and-feel. They may use real UI components, actual colour schemes, and realistic data.

Key characteristics:

Close to the final look-and-feel — suitable for detailed usability testing and stakeholder sign-off.
Needed to test things that only work at high fidelity: precise timing effects (Fitts’ / Hick’s Law effects); aesthetic judgement; realistic Cognitive Walkthroughs where visual hierarchy and salience matter.
More expensive and slower to change — so they are used later in the UCD cycle, once the structural design has been validated through Lo-Fi testing.

When to use Hi-Fi:

Late in the UCD cycle, when the structure is settled and you are refining details.
For summative evaluation — measuring whether the final design meets predefined usability targets.
When presenting to stakeholders who need a realistic preview before signing off on development.

Why Lo-Fi Encourages Better Feedback

This is a specific examinable point. Users are more honest with Lo-Fi prototypes because:

The roughness signals “this is a draft — your criticism is wanted and expected.” A polished Hi-Fi prototype signals “this is nearly finished — criticism would be rude or pointless.”
Users focus on structure and flow rather than fixating on surface details. With a Hi-Fi prototype, a user might say “I don’t like the blue — could you make it green?” — a cosmetic opinion that wastes evaluation time. With a Lo-Fi sketch, such comments do not arise because there is no colour to critique.
Lo-Fi’s disposability lowers the designer’s own emotional investment — they are more willing to throw away a sketch that took 10 minutes than an interactive mockup that took two days.

Expected Learning

Distinguish Lo-Fi from Hi-Fi prototypes in terms of cost, speed, appropriate UCD stage, and the type of feedback each elicits.
Explain why Lo-Fi prototypes encourage more honest and structural feedback, with reference to user psychology.
For a given design scenario, recommend Lo-Fi or Hi-Fi and justify the choice.
Understand that prototyping is iterative — Lo-Fi validates structure; Hi-Fi validates detail; both feed back into the UCD cycle.

Past Paper Questions

Prototyping appears in: 2025 Q5 (sketch app screens — Lo-Fi), 2023 Q6 (mindfulness app — prototyping methods), 2021 Q5 (Lo-Fi prototype alternatives), 2018 Q6 (CUSTOM stakeholders; Lo-Fi/Wizard of Oz prototyping). The exam frequently asks you to justify why Lo-Fi is appropriate for a specific scenario.