Context-switching cost
Context-switching cost is the productivity lost when an engineer moves between tasks, projects, or interruption types. The widely-cited research (Gerald Weinberg 1992) finds a single context switch costs roughly 20% of productive time on each project; switching between five projects leaves only ~5% productive time on each. Modern replication studies put the per-switch recovery time at 10-23 minutes.
Context-switching cost is the engineering productivity tax that doesn't appear in any sprint board metric. The biggest sources: meeting density (especially scattered single-occurrence meetings rather than blocked time), interruption from chat tools (Slack, Teams), and being staffed across multiple projects simultaneously. Mitigations with strong evidence: maker schedules (Paul Graham 2009) blocking half-days for deep work; team norms that batch meetings on specific days; explicit WIP limits per engineer (1 active story, not 4). Stride's research on engineering burnout finds context-switching cost is a stronger predictor of emotional exhaustion than total workload.
Related terms
- Deep work
Deep work, a term coined by Cal Newport in his 2016 book of the same name, is professional activity performed in a state of distraction-free concentration that pushes cognitive capabilities to their limit.
- Cognitive load
In engineering-team contexts, cognitive load is the amount of mental effort required for a team to be effective at its work — encompassing the domain knowledge, technical knowledge, and tool/process knowledge the team must hold in working memory.
- WIP limit
A work-in-progress (WIP) limit caps how many items the team can have in flight at once, per workflow stage.
- Emotional exhaustion
Emotional exhaustion is the first dimension of burnout in the Maslach framework: the chronic depletion of emotional and physical resources from sustained work demand.