Choose the question to answer
A useful prototype tests a specific uncertainty: whether the next step is clear, whether required information appears at the right time or whether a proposed flow fits the service. We agree the scenario and the screens needed to examine it, rather than simulating the entire future application.
Walk through decisions and states
Review the sequence with representative content and agreed participants. Capture misunderstandings, missing steps and decisions that need changing. Simulated submissions, availability or account states are examples for review; they are not proof of live data connections, secure access, persistent records or a production-ready business process.
Bring the idea and unresolved assumptions
Share the intended user, their goal, key rules and the questions that hold up a decision. We define the prototype boundary and review criteria. Findings inform the next scope discussion; building the working product and verifying its real integrations remain separate implementation tasks.