Keeping a goal visible or providing progress cues maintains its representation
Aliases: external goal cue · persistent progress indicator
What it is
Since the root cause of goal loss is that the resource needed to internally maintain the representation gets interrupted or drained by delay, the most direct countermeasure is to stop relying on internal maintenance alone — put the goal, or the progress made so far, somewhere external that the person can directly see, letting external perception hold up the representation instead of internal activation. Once a goal is visible, even after being interrupted the person doesn't need to reconstruct "what was I doing" purely from memory on return; a glance is enough to pick it back up, which shifts the burden of holding that memory from the brain onto the interface.
Why it happens
An internally maintained goal decays because it depends entirely on a limited pool of cognitive resources to continuously resist forgetting; once a goal has an external perceptual anchor — a piece of visible text, a progress bar, a highlighted position marker — retrieving that information no longer requires active memory search, it becomes a simple act of perceptual recognition, which costs far less cognitive resource than retrieval and doesn't fail just because something interrupted in between. This is also why an external cue can counter both interruption and delay: those two erode the resource used for internal maintenance, while the perceptual-recognition pathway doesn't draw on that same resource at all, so it isn't damaged by an interruption.
Where it stops holding
An external cue only works if it's actually seen at the moment of resumption — if the goal information is recorded somewhere the user has no reason to check on their own (buried in a log, tucked inside a collapsed menu), it does nothing to prevent goal loss, because the person would first need to remember "there's a place I could look," which is exactly the memory that's already been lost. An external cue also only prevents "the goal being forgotten" — if what's forgotten is "the situation in which this should be done" (remind someone the next time you see them, say), a persistently visible piece of text alone has limited effect; the cue also needs to be tied to the triggering situation to work.
Applying it
For any intention that requires the user to cross a potentially interruptible time window before it can be cashed out, keep the goal or its progress persistently displayed somewhere the user naturally passes through during that window, rather than recorded somewhere they'd have to actively go look — for example, pin a pending trailing step to a fixed spot in the interface, or automatically surface the progress state in the first place the user's eyes land when they return. To verify: in a usability test, deliberately insert an interruption mid-task and compare, between a condition where goal information stays persistently visible and one where it requires an active lookup, the proportion of users who correctly resume the goal — the persistently-visible condition should score noticeably higher.
Related
- Same group: A10.12.1 Mid-sequence, the goal representation driving an action gradually decays until it is lost · A10.12.2 After a goal is lost, the action may stop or get replaced by a more salient one · A10.12.3 Interruption and delay are the main triggers of activation loss
- Nearby: A10.03 Omission vs. commission errors · A6.21 External memory and cognitive offloading
- Search terms:
external cue·goal visibility·cognitive offloading