A6.08.5State-dependent memoryresearchdesign

Internal states such as mood and arousal are also part of the context

Aliases: mood-dependent memory · physiological state and retrieval

What it is

The encoding context isn't limited to visible surroundings — it also includes the internal bodily and emotional state present at the time: calm or tense, low or high physiological arousal. This phenomenon, where the match is based on internal state rather than external environment, is state-dependent memory: the closer the internal state at retrieval is to the state at encoding, the smoother retrieval goes — even when the external environment (the interface, the device) is exactly the same, a large enough gap in internal state can still hurt retrieval performance.

Why it happens

Mood and arousal change the overall pattern of nervous-system activity at the time, and that pattern becomes part of the memory trace alongside whatever content was being encoded. When retrieving that memory later, an internal state close to the one at encoding effectively supplies an extra matching cue that helps reactivate the trace. If the encoding happened in a calm, focused state but retrieval happens under acute stress or panic, that internal-state cue simply doesn't line up — even with identical external cues (the same interface, the same wording) one layer of matching signal that would normally help is missing, which makes retrieval harder.

Studying it

Classic evidence for state-dependent memory comes from having participants learn material under an induced state (a particular substance, an induced mood) and then testing recall under either the same or a different state — recall tends to be better when the states match. This effect is notoriously harder to replicate reliably than context-dependent memory tied to external environments: the induced internal state itself is difficult to control and quantify precisely, individual differences are larger, and the same manipulation produces inconsistent effect sizes across studies — a recognized methodological difficulty in this area.

Where it stops holding

State-dependent effects are less robust than external context-dependent effects; effect sizes are generally small and easily swamped by individual variation, so this shouldn't be treated as a design input with the same reliability as external cues. Its real value is as a reminder that "the calm state during training" and "the urgent state during actual use" are two different contexts — not as a formula that predicts precisely how much retrieval performance will drop.

Applying it

  • For features meant to be used under high-pressure, high-arousal conditions (emergency procedures, error recovery, alarm response), don't assume users will recall steps as smoothly as they did in a calm training environment. Design to minimize reliance on recall, putting critical information directly on screen instead of expecting users to remember it.
  • For training or onboarding tied to emergency scenarios, where feasible, rehearse under a degree of induced urgency or mild pressure rather than teaching once in a fully relaxed setting and assuming that transfers.
  • Verification: test the same cohort of trained users' performance on the critical procedure under both calm and simulated-urgency conditions. A marked drop in completion rate under urgency indicates the current design leans too heavily on the internal state present during training, and more information needs to be externalized.

Related

  • Same group: A6.08.1 Retrieval is easier when cues match the encoding context · A6.08.2 The interface itself can serve as an external retrieval cue · A6.08.3 Changing an interface removes a user's memory cues · A6.08.4 Context-dependent memory explains why switching devices carries a nonzero relearning cost · A6.08.6 Context-dependence affects recognition tasks less than recall tasks
  • Nearby: A6.06 Forgetting curve
  • Search terms: state-dependent memory · mood-dependent memory · arousal and retrieval

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/A6.08.5