Prototypes often start as small versions of the whole product: every screen, every feature, a little of everything. They take weeks, look impressive and leave the team unsure what was actually learned. Speed in prototyping does not come from typing faster. It comes from building less, on purpose.
The discipline is simple to describe and hard to keep: one prototype, one question, one clear answer. Everything else can wait for the next round.
Write the question first
Before anything is built, write the question the prototype must answer, in one sentence. Will shop owners understand the stock screen without training? Can a customer finish checkout on a small phone with one hand? Does the new home screen make the main action obvious?
If the team cannot agree on the question, it is not ready to build. That disagreement is worth resolving first.
Build only what the question needs
Once the question is clear, most of the product becomes irrelevant. Testing the checkout needs the cart, the address step and payment, not the account settings or the order history.
Everything outside the question can be a placeholder, a static image or simply missing. Leaving it out is what makes the prototype quick. Tell testers what is missing, so they do not spend the session looking for it.
Decide what counts as an answer
Agree in advance what result would change your mind. If most people in a test cannot find the payment options, the design needs rethinking. If they find them quickly and comment on something else, move on. Writing this down protects the team from reading whatever it hoped to see into the results.
Also decide who will make the call. A clear answer is wasted if nobody has agreed to act on it.
Keep a record of what was learned
After each round, write a short note: the question, what was built, who tried it, what happened and what was decided. Keep these notes together.
Months later, when someone asks why the product works the way it does, the answer is there. It also stops the same question being tested twice because nobody remembered the first time.
Then ask the next question
A good prototype usually answers its question and raises a better one. That is progress. A series of small prototypes, each settling one thing and each built in days rather than weeks, moves a product forward faster than one large prototype trying to settle everything.
