B4.01.1Seven Stages of Actiondesignresearch

Goal, plan, specify, perform, perceive, interpret, and compare are seven stages

Aliases: seven stages of action · Norman action model · action cycle

What it is

The seven stages of action divide a goal-directed action into forming a goal; planning possible actions; specifying the plan against the world; performing it; perceiving the change; interpreting perception; and comparing the result with the goal. The first four tend to run from intention to action; the last three run from world to understanding.

Why it happens

The model makes explicit the distance among “want,” “can do,” and “know whether done.” Goals are often abstract (save my work), while performance needs concrete actions (open a menu, name a file); specification requires visible possible actions; perception and interpretation depend on feedback; comparison determines whether users judge the goal satisfied. Every handoff can create a Gulf of Execution or Gulf of Evaluation.

Studying it

Use task analysis, think-aloud, and logs to map behavior to stages: record goal statements, candidate plans, selection reasons, input sequences, gaze or feedback, and end judgments. Experiments can manipulate visible actions, feedback timing, or result expression and observe which stage accumulates errors. Annotate task segments rather than assuming one click equals one stage.

Where it stops holding

The seven stages are an analytical framework, not a neural process or fixed sequence; skilled users automate many transitions. The model also does not cover all complexity of social collaboration, emotion, interruption, and competing goals. Accessible input, automated systems, and long tasks require extensions for waiting and delegated action.

Applying it

  • Fill in the seven stages for core tasks: user goal, visible plans, confirmation cues, controls, perceptible signals, interpretation support, and comparison evidence.
  • Check that every handoff has interface support: actions visible, state readable, result comparable.
  • Annotate task recordings by stage and prioritize repairs where users cannot plan, specify, or compare.

Related

  • Same group: B4.01.2 Stages can skip and loop rather than form a strict linear sequence · B4.01.3 The model locates which link contains the problem
  • Nearby: B2.01 Affordances · B2.06 Feedback
  • Search terms: seven stages of action · Norman action cycle · gulf of execution

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/B4.01.1