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. Cognitive load is the limiting factor on team capacity more often than headcount or hours; an overloaded team works slower, makes worse decisions, and burns out.
The concept comes from John Sweller's 1988 cognitive-load theory, applied to team design by Team Topologies (Skelton & Pais 2019). The three flavours: intrinsic (the inherent complexity of the work), extraneous (the unnecessary complexity from poor tools, process, or documentation), and germane (the productive load of learning). The pragmatic move for engineering leaders is reducing extraneous load — better internal documentation, self-service tooling, fewer team-spanning meetings — before adding headcount. Team Topologies explicitly bounds the surface area each stream-aligned team owns to fit the team's cognitive-load budget; platform teams exist specifically to reduce stream-aligned teams' extraneous load.
Related terms
- Team Topologies
Team Topologies, codified in the 2019 book by Matthew Skelton and Manuel Pais, is a framework for organising engineering teams using four team types and three interaction modes.
- Context-switching cost
Context-switching cost is the productivity lost when an engineer moves between tasks, projects, or interruption types.