# Supervisor Cognitive Overload

> Routing every parallel sub-agent's questions and approvals to one human reviewer — who quickly becomes the throughput bottleneck.

- **Category**: Agentic AI
- **Subcategory**: Anti-Patterns
- **Canonical URL**: https://designpattern.fyi/patterns/supervisor_cognitive_overload/

---

## Description
**Intent**: Each sub-agent in a parallel fleet routes its questions, clarifications, and approvals to one human supervisor — who is expected to hold context on all of them simultaneously.

**Context**: The team adopts multi-agent architecture to parallelize work. Oversight stays centralized. As agent count scales from 3 to 10 to 20, the human supervisor is answering every question from every agent. Approvals become rubber stamps. The parallelism gain evaporates.

**Solution**: Insert an aggregation layer between agents and the human. Batch and summarize sub-agent status. Surface only decisions that genuinely require human judgment. Let a lead agent or orchestrator absorb routine clarifications. Cap the number of agents one person realistically supervises. See selective escalation, orchestrator patterns.



## Use Cases
- You are reviewing a multi-agent design where every sub-agent reports directly to one human.
- Supervisors report thrashing or falling behind as agent count grows.
- Approvals are being rubber-stamped just to keep pace.






## Trade-offs




### Considerations & Drawbacks

- Oversight quality collapses as the supervisor thrashes between agents with no context on any single one

- Rubber-stamping becomes inevitable to keep pace — nullifying the human check entirely

- The human becomes the throughput ceiling, erasing the parallelism gain

- Supervisor fatigue makes the arrangement unsustainable at scale







---
**Reference**: [Original Source](https://www.agentpatternscatalog.org/patterns/supervisor-cognitive-overload/)