The secondary-task method infers the primary task's remaining resources from the performance drop on an added task

What it is

The secondary-task technique has participants perform an additional secondary task while completing a primary task, and infers how much cognitive resource the primary task consumes from how much the secondary task's performance drops — the more the secondary task's performance falls, the less capacity is left for it, and the higher the primary task's load is inferred to be.

Why it happens

For this method to work at all, the primary task's priority must always be held above the secondary task: participants are explicitly instructed to protect primary-task performance first, and the secondary task is only allowed to run on whatever capacity the primary task leaves over. Under that condition, secondary-task performance can be read as an indicator of remaining resource — when primary-task load is low, resources are ample and the secondary task performs well; when primary-task load is high, resources get squeezed and secondary-task performance drops accordingly. If that priority ordering doesn't actually hold — if participants quietly divert attention to the secondary task, or the secondary task is hard to ignore — the drop in secondary-task performance reflects the participant's own allocation strategy rather than the resources genuinely consumed by the primary task, and the entire inference chain breaks down. This priority precondition is exactly the line that separates a valid load reading from an invalid one.

Studying it

A typical paradigm assigns a primary task (a driving simulation, an interface operation) and a simple secondary task (intermittent auditory detection, simple mental arithmetic) alongside an explicit instruction to "always prioritize the primary task." The independent variable is the primary task's difficulty condition; the dependent variable is the secondary task's reaction time or accuracy. Studies typically measure the secondary task's baseline performance without any primary task first, then compute the performance drop once the primary task is added as the load reading. Methodologically, the priority ordering must be verified as actually followed — one indirect check is confirming that primary-task performance itself hasn't degraded because of the secondary task; if primary-task performance falls together with the secondary task's, priority was never truly established, and the data can't be interpreted through the standard secondary-task logic.

Where it stops holding

When researchers cannot effectively verify that participants really did treat the secondary task as subordinate, the method's readings lose their meaning. The technique also requires that the primary task actually leaves some spare processing capacity for the secondary task to draw on — if the primary task already consumes all available resources, the secondary task gets abandoned outright rather than showing a graded decline, and the method can only support the coarse conclusion "already saturated," without finer distinctions.

Applying it

• To use the secondary-task method to assess the load of an interface or flow, choose a secondary task simple enough that it doesn't require participants to actively allocate much attention to understand its rules, and repeat the primary-task-first instruction in the briefing.
• During analysis, first check whether primary-task performance stayed consistent with and without the secondary task — only once that precondition is confirmed can a drop in secondary-task performance be treated as valid evidence of primary-task load.

Related

• Same group: A9.08.1 Unchanged primary-task performance does not mean load hasn't increased — resources may simply have slack left · A9.08.3 The secondary task's own presence changes how the primary task is performed — the measurement interferes with what it measures · A9.08.4 The secondary-task method is sensitive when the two tasks compete for the same resource, and underestimates load when they don't
• Adjacent: A9.10 Multiple Resource Theory · A9.02 Measuring Load
• Search terms: secondary-task technique · dual-task paradigm · task prioritization · residual capacity