Norman's Action Cycle
Updated 2026-08-16
INTRODUCTION
English translation pending.
CORE DEFINITION
Donald Norman's action cycle describes any interaction as seven stages: forming a goal, forming an intention, specifying the action sequence, executing it, perceiving the system state, interpreting that state, and evaluating it against the goal. The diagnostic value comes from the chain rather than the count: an experience fails whenever any single link is broken, so a user who reports that something is awkward is reporting a break, and the model tells you which link to inspect rather than where to guess.
SCAFFOLDING EFFECT
Reduce cognitive load
- Walk the chain: trace the seven stages for the failing task instead of reacting to the complaint. - Find the break: name the specific stage where the chain severs, and fix there rather than at the surface. - Check both halves: execution gaps and evaluation gaps produce identical frustration but need opposite fixes.
Anchor fast decisions
Interaction is a loop that must close: the user's goal must be turned into actions, and the system's response must be turned back into feedback that can be compared with that goal. Each stage is a potential discontinuity, and the user's subjective experience of badness is a symptom that says nothing about the location of the cause. Staging the interaction decomposes one vague complaint into seven specific, separately testable questions, which is why it converts unusable feedback into a targeted fix.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/The_Design_of_Everyday_Thingsverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS