Behavior Prototype Checklist
What a prototype should test before it is styled: assumption, trigger, system response, visibility, user control, failure case, recovery path.
What behavioral belief is the prototype trying to prove or disprove?
What starts the behavior, and who or what initiates it?
What does the system do in response, over time or immediately?
What does the user need to see about state, reasoning, confidence, or consequence?
Where can the user steer, pause, override, or refuse the behavior?
What happens when the system is wrong, late, uncertain, or incomplete?
How does the user repair the situation without losing trust or context?
What it helps you see
It exposes the questions or checks that need to be answered before the product behavior can be trusted.
How to use it
Use this to scope the smallest running artifact that can answer a real behavior question. The output is a prototype brief.
Use it when
Use this when a product question in Prototype the Behavior needs structure before it becomes a screen, roadmap item, or portfolio claim.
Practice prompt
Choose a real product, project, or career decision and answer the framework's items in order. Carry forward the answer that changes the next move.
Source chapter
This framework was authored in Prototype the Behavior. Read the chapter for the full argument and the worked examples that produced this shape.