Slide 1 of 24
PreviousNext
Session 14
A flow turns standards into behavior
- A flow is connected behavior, not a row of screens.
- Each screen needs a job, action, state, and transition.
- A feature brief explains the flow so a team can review it.
Practice sequence
- 1FrameStart with user story, criteria, constraints, and chosen option.
- 2FlowDefine screen jobs, actions, states, and transitions.
- 3StressAdd branches, recovery paths, and accessibility notes.
- 4BriefCapture scope, signals, risks, and handoff notes.