A prototype is a working model of a product or screen flow that people can click through or try, built to test ideas before full development.
Design · Reviewed by Ray Rasouli
Ask about prototype
Plain answers, with your setup in mind.
Ask anything about prototype. For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
A prototype lets people experience a design instead of imagining it. It might be a set of linked screens in a design tool, or a rough coded version with fake data. Either way, users can tap, type and move through steps.
A manufacturer planning a new dealer portal could prototype the quote request flow in a week, put it in front of five dealers and learn that they need to upload drawings, something nobody had mentioned in meetings.
Prototypes are meant to be thrown away or reworked. Their job is to find the expensive mistakes while they are still cheap.
The usual flow, step by step.
In practice
It looks too finished.
A polished prototype makes stakeholders think the product is almost done, which skews timelines and feedback.
It is never tested with real users.
Showing it only to the internal team misses how customers or staff actually behave.
Prototype code goes to production.
Quick code built to test an idea becomes the real product without being rebuilt properly.
The question is unclear.
Without a specific thing to learn, testing sessions produce opinions instead of answers.
Only as detailed as needed to answer your question. Early ideas can use rough clickable sketches; later tests may need realistic data.
A prototype is for learning and is often thrown away. An MVP (minimum viable product) is a real, usable product released to customers.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.