Capacity limits and time-based decay are two independent mechanisms, and easing one doesn't substitute for the other

What it is

The blanket outcome "the user couldn't remember it" traces back to at least two independent causes: the number of items held at once exceeded the capacity ceiling, or the content was held for too long and faded naturally. Both causes often show up together in the same failure, but they're two different things — reducing how many items are shown at once fixes a capacity problem; shortening how long a user has to hold content fixes a decay problem. Treating the diagnosis correctly is what makes the fix work; treating one as a substitute for the other usually doesn't.

Why it happens

The two mechanisms can be manipulated independently without affecting each other, which is exactly the evidence that they're separate: increasing only the number of simultaneously presented items while holding the retention interval fixed degrades recall through exceeding capacity; lengthening only the retention interval while holding item count fixed degrades recall through decay; when both are combined, the failure rate typically approximates the sum of each effect's individual contribution rather than one effect swallowing the other. This shows that working-memory failure isn't the product of a single cause — it's the joint outcome of two independent limits, "how much fits at once" and "how long it lasts," and genuinely solving a memory-burden problem in design requires first working out which one is actually at fault.

Studying it

Experiments that separate the two mechanisms typically use a two-factor manipulation: one condition holds the retention interval fixed and varies only the number of simultaneously presented items, observing how performance drops with count; another condition holds item count fixed and varies only the length of the retention interval, observing how performance drops with time; a third condition varies both together to test whether the two effects are approximately additive. If each manipulation independently degrades performance, and no single factor can account for the other's effect, that confirms the two are separable, independent mechanisms.

Where it stops holding

This separation holds when describing the two mechanisms as independent in principle, but it doesn't mean they never interact in real usage — in practice, increasing item count often also lengthens the time needed to process those items, so both can degrade together. The point of this finding is to push designers to account for each factor's contribution separately, not to claim they necessarily show up in isolation in any given real scenario.

Applying it

• When troubleshooting a memory-related usability problem, diagnose the two dimensions separately first: how many independent items must the user hold at once at this step, and how long is the gap between seeing the information and needing to use it. Check each against its own tolerable range — don't assume the problem is solved just because one of the two was adjusted.
• If the diagnosis shows item count is within range but the gap is too long, the right fix is to shorten the flow so display and use happen closer together — not to trim the item count further. Conversely, if the gap is short but too many items must be held at once, the right fix is to split or externalize some of the items — not to expect users to speed up so they beat forgetting to the punch.
• How to check: run two separate modification tests on the same flow — one that only reduces item count, and one that only shortens the retention interval — and compare how much each improves the error rate. This shows whether the flow's actual bottleneck is capacity or decay, and which to fix first.

Related

• Same group: A6.02.1 The number of items working memory can hold at once is limited · A6.02.2 Retention is brief and vulnerable to interference · A6.02.3 Requiring users to remember content across pages is itself a design flaw · A6.02.4 The classic capacity estimate is closer to four chunks than the earlier figure of seven · A6.02.5 Without rehearsal, working memory content decays naturally within roughly ten to twenty seconds · A6.02.6 Rehearsal extends retention but draws on the same limited processing resource · A6.02.7 Capacity varies with item complexity, so simple and complex items can't be compared on one number
• Nearby: A6.03 Chunking · A9.02 Measuring cognitive load
• Search terms: working memory load versus delay · capacity limit · time-based decay