# Measure workload before blaming attention

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Measure workload before blaming attention

ID: MHC-D-RESEARCH-0489 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/measure-workload-before-blaming-attention

Attention is not an unlimited resource you can restore with a motivational email.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- Errors increase and the explanation is that people need to 'focus more.'

### Avoid when

- NASA-TLX and similar measures are subjective workload tools; they do not diagnose fatigue, competence or intent.

### Explanation

Assess the task's mental demand, time pressure, effort, frustration and related workload dimensions before concluding the worker is careless. Compare workload across normal and failure-prone conditions. Use the result to simplify interfaces, redistribute work, change timing or reduce concurrent demands.

### Steps

1. How mentally demanding is the task?
2. What time pressure exists?
3. How much effort is spent managing the interface rather than the goal?
4. When do errors rise relative to workload?
5. Which demand can be removed or redistributed?

### Example

If errors spike only while one analyst monitors three interfaces during cutover, redesign coverage before retraining concentration.

### Check

A corrective action addresses measured task demand or leaves evidence that workload was not the main contributor.

### Limits

- NASA-TLX and similar measures are subjective workload tools; they do not diagnose fatigue, competence or intent.

### Evidence and sources

- supports: NASA TLX is an established subjective instrument for assessing workload across human-machine tasks. — RS-643BDA404840CB30. A workload score does not diagnose why the workload is high or whether an individual is fit for duty. (NASA TLX overview and publications)
- supports: FAA human-factors practice explicitly treats automation, alerts, workload, complexity and fatigue as design concerns affecting safe human performance. — RS-AC253E08891D8C2A. Aviation certification practices are highly domain-specific; only general human-system design principles transfer. (Flight Deck Human Factors)
- RS-643BDA404840CB30: NASA Task Load Index (TLX) — https://www.nasa.gov/human-systems-integration-division/nasa-task-load-index-tlx/
- RS-AC253E08891D8C2A: Technical Discipline: Flight Deck Human Factors — https://www.faa.gov/aircraft/air_cert/step/disciplines/flight_deck_human_factors

No review details supplied.
