Low-fidelity prototyping in the develop phase - what a low-fidelity prototype is, the materials and techniques used (paper, card, mock-ups, role-play, storyboards), why fast and rough is the point, how user testing of low-fidelity prototypes produces evidence, and how that evidence drives iteration

What this dot point is asking

QCAA names low-fidelity prototyping as a core skill of the develop phase. This dot point asks you to know what a low-fidelity prototype is, how to make one quickly and cheaply, and how testing it with the user produces evidence that drives the next iteration. The point is not to build something polished - it is to learn fast and cheap before committing. Marks come from showing that you prototyped, tested with the user, and let the results change your design.

The answer

What low-fidelity means

Fidelity is how closely a prototype resembles the finished design. A low-fidelity prototype is deliberately rough - it represents enough of an idea to test one question, and no more. It might be a paper mock-up of a layout, a cardboard model of a handheld object, a storyboard of how an interaction unfolds, or a role-play of a service. The roughness is the feature, not a shortcut: a crude prototype invites honest feedback, because the user can see it is not precious and feels free to criticise it.

Materials and techniques

Low-fidelity prototyping uses whatever is fast and cheap:

• Paper and card - sketched screens, folded forms, cut-out parts to test layout and arrangement.
• Foam, clay or found objects - quick three-dimensional mock-ups to test size, grip and ergonomics.
• Storyboards - a sequence of frames showing how a person uses the design over time.
• Role-play and bodystorming - acting out an interaction or service to feel how it flows.
• Wireframes - rough block layouts for screen-based or spatial designs.

The technique fits the question. To test whether a handle fits the hand, mock it in foam. To test whether a sequence makes sense, storyboard it.

Why fast and rough is the point

Low-fidelity prototyping is about learning per dollar and per hour. Because each prototype is cheap, you can build several, test them in parallel, and discard the losers without regret. The cost of being wrong is tiny, so you can take risks and test bold ideas early, when changing direction is still easy. Investing in a polished prototype too soon is the expensive mistake - you become attached to it and reluctant to change it even when testing says you should.

Testing with the user

In human-centred design the test that matters is with the identified user. You put the rough prototype in front of them, give them a realistic task, and observe:

• What they do (not just what they say).
• Where they hesitate, struggle or succeed.
• What surprises you - the use you did not anticipate.

You watch and listen rather than explaining or defending. The aim is to surface problems while they are still cheap to fix.

How evidence drives iteration

The output of a test is evidence, and evidence drives the next move. A prototype that fails a user test is a success of the process - it told you something before it was expensive to learn. Depending on what the test reveals, you might refine the prototype, switch to a different concept, or loop back to explore because the test exposed a misread need. This is the iterative, non-linear heart of the design process made concrete. Documenting the test result and the decision it drove is exactly what markers look for.

Low-fidelity versus high-fidelity

Low-fidelity prototypes dominate the develop phase, where breadth and fast learning matter. As the design converges, fidelity rises - the resolve phase uses high-fidelity prototypes and visualisations to refine and communicate the chosen response. The skill is to stay low-fidelity as long as the questions are still open, and only invest in fidelity once the concept is settled.

Worked example