UX
Prototype Testing
A practical UX method for testing early designs, validating concepts, and reducing risk before development starts.
How to use prototype testing to evaluate early ideas, uncover issues before build, and improve designs while changes are still cheap.
What it is
glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term testing is a UX serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service method used to evaluate early glossaryVersionA version is a specific iteration of software or a product at a point in time.Open glossary term of a product before it is fully developed.
glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term can range from low-fidelity wireframes to high-fidelity interactive designs that simulate real glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term.
Users are asked to complete tasks using the glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term, allowing you to observe glossaryUsabilityUsability is how easy and efficient it is for users to complete tasks within a product. It focuses on clarity, simplicity, and reducing effort so users can achieve their goals without confusion or friction.Open glossary term, understanding, and glossaryInteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term patterns.
Unlike testing live products, glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term testing allows you to explore and validate ideas without the cost of development.
The goal is to identify issues early, validate concepts, and reduce risk before building.
Prototype testing is most useful when you need to learn early, while the design is still flexible enough to change.
When to use it
Use this method early in the design glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term.
It is most useful when:
It is less useful when:
Prototype testing is often used alongside usability testing and interviews to refine designs before launch.
Key takeaway
Use prototype testing when the main goal is validating ideas early enough to improve them before development cost starts to rise.
How to run it
Set up properly
Be clear on what the glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term can and cannot do, and design tasks that stay inside it. Most prototype test failures are participants hitting an unbuilt path.
Decide how you will handle the gaps before the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term (a spoken explanation, a static screen, or a redirect) and keep it consistent.
Run the method
glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term testing puts an incomplete thing in front of real users. The skill is in managing the gap between what exists and what is implied without answering the question you came to ask.
- Give realistic scenarios and tasks that the glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term can actually support.
- Ask people to interact with it directly rather than talking through what they would do.
- Observe glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term and glossaryInteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term, noting where the fidelity misled them rather than the design.
- Encourage think-aloud, which matters more here because the glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term cannot respond to everything.
- Capture successes and issues, and separate genuine glossaryUsabilityUsability is how easy and efficient it is for users to complete tasks within a product. It focuses on clarity, simplicity, and reducing effort so users can achieve their goals without confusion or friction.Open glossary term problems from glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term limitations.
Set expectations honestly at the start. Telling somebody that parts are unfinished costs you nothing and prevents them apologising for your glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term for half an hour.
Capture and make sense of it
The value comes from testing before building. After the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term, document:
- Problems with the design, separated from artefacts of the glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term
- Where people expected glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term that did not exist
- Which assumptions the glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term validated and which it did not
- What needs a higher-fidelity test before it can be settled
Use this to reduce risk before committing to glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term. The cheapest change is always the one made to a glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If the glossaryPrototypeA prototype is an early version of a product used to test ideas, interactions, and concepts.Open glossary term is not usable, the glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term will not be either.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps you get it right before you build it.
Get in touch
If this sounds like something you need, we can help you test ideas early and avoid costly mistakes later.
No guesswork. No assumptions. Just clear insight you can act on.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is prototype testing in UX?
Prototype testing is a method used to evaluate early designs before development.
When should you use prototype testing?
Use it early in the design process to validate ideas and reduce risk.
What level of fidelity is needed?
It depends on the goals, but the prototype should support realistic interaction.
Can prototype testing replace usability testing?
No. It complements usability testing but does not replace testing on live products.
Does prototype testing improve UX?
Yes. It allows you to fix issues early and refine designs before development.
Quick take
If you want to test ideas before building them, use prototype testing.
Related Services
