How does building a prototype turn an idea into something customers can react to?
Create and iterate prototypes of a product or service to test, demonstrate and refine the value proposition.
How to build low and high fidelity prototypes of a product or service, use them to gather customer feedback, and iterate towards a refined offer that demonstrates the value proposition.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
Jump to a section
What this dot point is asking
You need to show you built one or more prototypes, used them to get genuine customer feedback, and changed your idea in response. Iteration is the evidence markers reward.
What a prototype is and why it matters
A prototype is a representation of your solution that you can put in front of people to learn from. It is not the finished product; its job is to make ideas tangible, surface problems early, and let customers respond to something concrete rather than a description. A rough prototype in week one is worth more than a perfect product launched too late.
Low fidelity versus high fidelity
- Low fidelity prototypes are quick and cheap: paper sketches, cardboard models, storyboards, wireframes or a role-played service. They test core concepts fast and are easy to throw away.
- High fidelity prototypes look and behave closer to the real thing: a working sample, a clickable app mock-up, a 3D-printed part. They test detail and usability but cost more time.
Start low, then raise fidelity only as the concept earns it. Spending too long polishing a prototype before testing is wasted effort if the core idea is wrong.
Prototyping a service
Products are not the only thing you prototype. For a service, you can prototype the customer experience: a storyboard of the steps a customer goes through, a role-play of the interaction, or a manual "concierge" trial where you deliver the service by hand. This reveals friction points before you build any systems.
The MVP and the prototype-to-product path
A prototype and a minimum viable product (MVP) overlap but are not identical. A prototype is built mainly to demonstrate and refine a concept, often shown to a few users in a controlled way. An MVP is the simplest version released to real customers in the real market to generate validated learning about whether they will adopt and pay. A venture often moves along a path: rough low-fidelity prototypes to shape the concept, higher-fidelity prototypes to refine usability, then an MVP to test genuine demand. Recognising where a given artefact sits on this path, and being explicit about what each version is meant to learn, shows the assessor a deliberate development process rather than aimless tinkering. The throughline is that every build, from a cardboard mock-up to an MVP, exists to answer a question and reduce a risk, not simply to produce something that looks finished.
Iterating with feedback
The value of a prototype is the feedback loop. For each round: decide what you want to learn, put the prototype in front of real users, observe what they do (not just what they say), and record the change you made as a result. Document each version so you can show the journey from rough idea to refined offer.
Linking forward
Your prototype demonstrates the value proposition and is a core part of the Business Idea Pitch and Prototype assessment. The feedback you gather feeds your testing evidence, your refinements and your final pitch, and the development story strengthens the external Business Plan.
Exam-style practice questions
Practice questions written in the style of SACE Board exam questions on this dot point, with worked answer explainers. The year tag is the paper they imitate, not the source.
SACE 20234 marksDistinguish between low-fidelity and high-fidelity prototypes, and explain why a venture should usually start with low fidelity.Show worked answer →
Low-fidelity prototypes are quick and cheap representations (paper sketches, cardboard models, storyboards, wireframes, role-plays) that test core concepts fast and are easy to discard. High-fidelity prototypes look and behave close to the real product (a working sample, a clickable app mock-up, a 3D-printed part) and test detail and usability but cost more time and money.
A venture should usually start low because the core idea may be wrong: testing a rough version early surfaces fundamental problems cheaply, before time and money are sunk into polish. Raising fidelity only as the concept earns it avoids wasting effort refining something customers do not want.
Markers reward a clear distinction on cost, realism and purpose, and a sound reason for starting low (cheap learning, avoiding wasted polish).
SACE 20246 marksEvaluate the role of iteration in prototyping, and explain how a venture should use customer feedback to refine a product or service across versions.Show worked answer →
Iteration is central because a prototype's value lies in the feedback loop, not the artefact itself. Each round should start by deciding what to learn, put the prototype in front of real users, observe what they actually do (not only what they say), and record the change made as a result.
Across versions, feedback drives refinement: a low-fidelity version tests whether people want the idea; later, higher-fidelity versions test usability and detail, with each design change traceable to a specific piece of feedback. Documenting the versions evidences the journey from rough idea to refined offer.
The evaluation should weigh the strengths (cheap learning, customer-centred refinement, reduced risk of building the wrong thing) against limits (small samples, the cost of many rounds, the risk of over-iterating on minor points). A balanced conclusion is that disciplined iteration driven by observed behaviour produces a stronger, validated offer. Markers reward the role of iteration, the feedback-to-change link, behaviour over opinion, and a balanced judgement.