Give your prototype one question to answer

Name the uncertainty

A prototype can look polished and still teach you very little. Before opening a design tool, write the question it should answer. “Can someone find the next action?” is narrow enough to observe. “Do people like the product?” bundles too many questions together.

Choose a believable slice

Build the part of the journey that contains the uncertainty. If the question concerns a handoff, you may need one task, a decision record, and a recipient. A dashboard, billing screen, and account settings may add work without making the test more informative.

Watch what happens

Give the participant a realistic task and let them attempt it. Record where they hesitate, what they expect to happen, and what they do next. A participant’s compliment can be encouraging, but it is not a substitute for observing the behavior the prototype was meant to support.

Make a bounded decision

Afterward, decide whether to change the concept, narrow the audience, or run another test. Preserve the observation behind the decision so another teammate can understand it later. Avoid turning one session into a general claim about every potential user.

The fictional Current brief provides a simple handoff scenario. Read Bird’s approach for how this kind of small experiment fits into a broader studio rhythm.