Systems & Organizations
Stop Adding Layers to Speed Decisions
When a senior manager at a global retailer stripped a middle‑management tier, the product pipeline sprinted forward instead of stalling.
2026-08-131 min read
The instinct to pile on reporting layers springs from the belief that more oversight equals fewer mistakes, yet each extra manager adds a waiting room for every decision. Information must travel up to a new gate, get signed off, then travel back down, inflating the time between idea and execution. This latency does more than waste hours; it reshapes incentives, rewarding those who can navigate the bureaucracy rather than those who can solve the underlying problem.
In the retailer’s case, a newly created regional director role sat between store‑level planners and the corporate merchandising team, forcing every assortment tweak to pass through two review cycles. When the director was removed, planners could present proposals directly to the merchandising lead, cutting the feedback loop to a single exchange. The speed gain unlocked a hidden capacity: teams began experimenting with micro‑pilots, learning faster and allocating shelf space more responsively.
The organization also noticed a cultural shift; employees felt trusted to own outcomes instead of shielding themselves behind approvals. However, the reduction exposed a new risk: without a clear escalation path, some conflicts escalated to senior leadership, forcing occasional ad‑hoc meetings. The key is to balance the need for alignment with the cost of waiting, ensuring that the structure itself does not become the bottleneck.
Key insights
Every additional manager adds a waiting period that compounds across the organization.
Removing a layer often uncovers hidden capacity for rapid experimentation.
Why it matters
Ignoring the coordination cost of extra layers leaves organizations perpetually chasing deadlines that never arrive.
Over‑structured hierarchies erode accountability, as people defer responsibility to the next gatekeeper.
Use this tomorrow
1Open the latest project tracker, locate the first decision‑required column, and count how many distinct manager approvals appear before a task moves to “in‑progress”.
2Pick a current cross‑functional request, reroute it to skip the lowest‑level manager, and note whether the requester receives a response within a day.
Go deeper
The phenomenon traces back to classic queueing theory, where each service station adds latency that grows non‑linearly as utilization rises. In practice, the “gatekeeper” role can be replaced by lightweight decision‑rights, such as clear thresholds that empower the next level to act autonomously.
A downside appears when the remaining layers become overloaded, turning a single gate into a new choke point. Organizations that flatten too aggressively may also lose a forum for strategic alignment, so a hybrid approach—flattening operational tiers while preserving a strategic council—often works best.
