A project misses its date. The executive decision that created the date is described as ambitious. The team that worked nights is described as committed. The middle manager is described as needing stronger execution discipline.
The blame lands in the middle because the middle is the easiest place for it to stop.
Middle managers translate strategy into work and work into status. They face upward as representatives of delivery and downward as representatives of leadership. That position makes them useful absorbers of failure. They are visible enough to blame and insufficiently powerful to redirect blame toward the decisions that created the failure.
This is scapegoating with organizational structure around it.
Blame Follows The Reporting Path
Executives are protected by distance. They set direction, allocate constraints, and approve priorities. When outcomes fail, the failure is often interpreted as execution trouble rather than strategic error.
Individual contributors are protected by limited authority. They did the work assigned to them. If the plan was wrong, they can say they lacked the power to change it.
Middle managers sit between those protections. They are close enough to the work to be associated with the failure and senior enough to be expected to prevent it. They rarely control the original conditions.
That makes them structurally convenient. The organization can acknowledge failure without questioning the senior decisions that shaped it or blaming the employees who had little authority.
Translation Turns Decisions Into Commitments
The mechanism is subtle.
An executive says the company needs the product shipped this quarter. The middle manager turns that direction into sprint plans, staffing discussions, delivery commitments, and team expectations. The executive’s pressure becomes the manager’s promise.
To the team, the manager committed to the date. To the executive, the manager accepted the target. When the date slips, the manager appears to have failed at commitment management.
The original decision may have been unrealistic. The team may have warned about risk. Dependencies may have been outside the manager’s control. The translation step still made the manager the visible owner of the outcome.
Root Causes Are Politically Hard To Name
Middle managers often know why work failed.
The timeline was set before discovery. The budget was too small. A dependency team had different priorities. Technical debt consumed capacity. Hiring was frozen. Scope expanded while the date stayed fixed.
Saying those things plainly can be risky. It can sound like blaming leadership, criticizing peers, or failing to take ownership. So the manager softens the diagnosis.
They say the team needs better planning. They say communication could improve. They say risks should have been escalated earlier. These statements may be partly true. They are also safer than saying the project was structurally underpowered from the start.
The organization learns a cleaner lesson and repeats the same setup.
The Buffer Function
Middle managers protect both directions.
They protect executives from the full reputational cost of bad constraints. The strategy remains sensible; execution fell short. The deadline remains bold; delivery needed more discipline.
They protect teams from being blamed individually for working inside impossible conditions. The manager absorbs the criticism, rewrites the plan, and keeps morale from collapsing.
This buffering is sometimes part of good management. It becomes corrosive when the buffer becomes the accountability sink.
The manager’s reputation erodes through repeated failures they could explain but cannot safely attribute. Eventually the organization concludes the manager is not scaling. A new manager inherits the same structure.
Why Replacement Does Not Fix It
When a middle manager is removed after a structural failure, the system gets a short burst of closure. Someone was accountable. Action was taken. Leadership can say the organization learned.
Then the next manager meets the same conditions: dates set elsewhere, resources controlled elsewhere, priorities contested elsewhere, authority unclear at interfaces.
If the role still lacks the power to change those conditions, the next failure will follow the same path. The person changed. The blame architecture stayed.
This is why middle-management churn often accompanies chronic execution problems. The organization keeps replacing the part designed to absorb stress instead of reducing the stress.
How To Stop Using The Middle As A Shock Absorber
Start failure reviews above the delivery layer.
Before asking how the manager executed, ask which decisions set the constraints. Who set the date? Who approved scope? Who controlled staffing? Who owned dependencies? Which risks were accepted, and by whom?
Then compare the manager’s accountability with their authority. Could they reject scope? Move resources? Change commitments? Escalate with consequence? Override conflicts?
If the answer is no, blaming the manager will not improve the system. It will only teach the next manager to document more carefully and speak less directly.
Middle managers should be accountable for the decisions they actually make: sequencing, coaching, communication, local prioritization, and execution judgment. They should not be used to launder structural failure into personal underperformance.
Blame accumulates in the middle when organizations want accountability without exposing power. The middle can absorb that cost for a while. Eventually it turns into burnout, churn, and a management layer trained to survive rather than decide.
