Cognitive load is also a team design problem

We often discuss cognitive load as an individual concern: focus harder, organise better, remove distractions. Software work makes the limits of that framing obvious. A developer’s attention is shaped by the architecture, the tools, and the coordination demands around the task.

The environment keeps a tab open

Every unclear dependency, undocumented convention, and pending decision occupies a little working memory. None is dramatic alone. Together they form a persistent tax on reasoning.

Reducing that tax is legitimate engineering work. Clear interfaces, predictable environments, and fewer hand-offs are not just efficiency improvements; they are cognitive supports.