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.
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.