Note ·
Naming paths, not screens
A short method for describing interface flows so handoffs stay visible.
Screenshot galleries hide exceptions. Path language surfaces them: start state, actor, handoff, exit condition.
Mark where evidence ends. Guessing past that line is how briefs quietly invent architecture.
Practice this in the interface flow clinic with a product you already use at work.
