Supervisor Cognitive Overload

Problem

Parallel agents multiply the supervision surface faster than a human can absorb it. Each agent needs context-setting, mid-task clarification, and review; when all of that lands on one person simultaneously, the supervisor thrashes between agents, loses track of which said what, and either rubber-stamps to keep up or becomes the slowest part of the system. The parallelism that was supposed to speed things up is throttled by a single human's working memory.

Solution

Recognise the anti-pattern and redesign the oversight surface. Insert an aggregation layer between the agents and the human: batch and summarise sub-agent status, surface only the decisions that genuinely need a human, and let a lead agent or orchestrator absorb routine clarifications. Cap the number of agents one person supervises, or move from per-agent conversation to a single dashboard with prioritised exceptions. The corrective patterns are selective escalation and a coordinating layer, not more human bandwidth. Japanese practitioner reports flag this directly: when the human must talk to every agent, cognitive load becomes the limiting factor.

When to use

• You are reviewing a multi-agent design where every agent reports to one human.
• Supervisors report thrashing or falling behind as agent count grows.
• Approvals are being rubber-stamped to keep pace.
• You are deciding how many agents one person can realistically oversee.