Skip to content
Software Behaviorby Joost van der Zwan
Index

Framework · Sequence · from Chapter 11

Behavior Prototype Checklist

Scopes a prototype as an instrument for a named risk, from a sketch or clickable flow to running behavior.
Read the chapter

The framework

Fig. · Behavior Prototype Checklist
  1. Assumption: What behavioral belief is the prototype trying to prove or disprove?
  2. Trigger: What starts the behavior, and who or what initiates it?
  3. System response: What does the system do in response, over time or immediately?
  4. Visibility: What does the user need to see about state, reasoning, confidence, or consequence?
  5. User control: Where can the user steer, pause, override, or refuse the behavior?
  6. Failure case: Which must-act and must-not-act cases expose what happens when the system is wrong, late, uncertain, or incomplete?
  7. Recovery path: How does the user repair the situation without losing trust or context?
  1. 01

    Assumption

    What behavioral belief is the prototype trying to prove or disprove?

  2. 02

    Trigger

    What starts the behavior, and who or what initiates it?

  3. 03

    System response

    What does the system do in response, over time or immediately?

  4. 04

    Visibility

    What does the user need to see about state, reasoning, confidence, or consequence?

  5. 05

    User control

    Where can the user steer, pause, override, or refuse the behavior?

  6. 06

    Failure case

    Which must-act and must-not-act cases expose what happens when the system is wrong, late, uncertain, or incomplete?

  7. 07

    Recovery path

    How does the user repair the situation without losing trust or context?

4 · Do

How to use it · Prototype brief

Choose only the fidelity needed for the risk. Add representative must-act and must-not-act cases when behavior is variable. The output is a prototype brief.

5 · Save

The Product Architect · Behavior Prototype Checklist

Framework · Sequence