Choose the question before the format
A prototype is a limited version of an idea made so you can learn from it. It might be a paper mock-up, a short sequence of images, a rough audio clip or a simple event plan. Its purpose is not to prove that the idea is good. It is to make an uncertain part of the idea visible enough to discuss or try.
Start by writing the concept in one sentence: who is it for, what will they encounter and what should they take away? Then name one question you cannot answer from your desk. If you are planning a neighborhood photography zine, for example, you might ask whether readers can follow the story without captions. That is more useful than asking whether they generally like the zine. A focused question tells you what to make and what to leave unfinished.
Build the smallest version that can answer it
Make only the parts needed to explore your question. For the zine, select a few photographs and arrange them as a folded paper spread. There is no need to settle the cover, printing method or complete visual identity if you are testing the sequence of images. Keeping those decisions open makes it easier to change direction later.
The prototype still needs enough context to give someone a fair experience of the idea. If the finished work is meant to be held and browsed, a physical fold may tell you more than a set of images on a screen. If the concept depends on a workshop conversation, test a short version of the activity rather than showing people a written description. Aim for rough but legible: participants should be able to respond to the concept without having to guess which unfinished details matter.
Let people try it before you explain it
Invite a few people who resemble the intended audience, or who will use the work in a relevant setting. Explain what you are asking them to do, but avoid presenting your intended interpretation first. For the zine, you could hand someone the folded spread and ask them to look through it as they normally would. Notice where they pause, what they return to and whether they turn the pages in the order you expected.
Afterward, ask open questions tied to your original uncertainty: “What story did you get from these images?” and “Was there a point where you wanted more context?” These questions invite specific responses without requiring people to become art directors. Separate what you observed from what participants said. Someone stopping at an image is an observation; assuming they found it confusing is an interpretation you may need to check.
Look for patterns without treating feedback as a vote
Write down responses soon after each test, including surprising uses and moments of hesitation. Keep the notes simple: what happened, what the person said and what you think it might mean. If several readers interpret the image sequence differently from your intention, the order may need work. If one person dislikes the paper stock, that may be worth recording but may not matter to the question you set out to test.
Feedback is most useful when you consider the conditions around it. Was the person seeing the work in a quiet room even though it will appear in a busy public place? Did you have to explain a step that the finished piece will need to communicate on its own? A prototype cannot settle every decision. It can, however, show which assumptions seem sound, which need another test and which are less important than you expected.
Make one deliberate change and test again
Finish the test by writing a short decision statement: what you learned, what you will change and what remains uncertain. For the zine, you might decide to move the opening photograph, add a brief introductory line and leave the cover design for later. Change one or two things that address the clearest issue, then show the revised version to someone who has not seen the first. This helps you judge the revision without relying on a participant’s memory of the earlier version.
Not every prototype has to lead to another prototype. Sometimes the result gives you enough confidence to develop the full work; sometimes it shows that the central idea needs rethinking. Either outcome is useful. By keeping the test small and the question clear, you give yourself room to learn while the project is still easy to shape.
