The Manager Who Deflects Accountability: When Delay Becomes the Operating Model

One colleague’s late delivery stopped being occasional and became a stable pattern. At first, workload seemed the obvious explanation: too many priorities, too little time. The evidence eventually pointed elsewhere.

Each delay came with a justification. A dependency not met. An input received too late. A requirement not clearly defined. Individually plausible. Repeated, a strategy.

What made it serious, El Hassane Ben Ahmed writes in Chapter III.5 of The Lessons That Stayed, was the colleague’s role. He was managing a team. Yet there were no real discussions with that team about priorities, no anticipation of constraints, no shared understanding of objectives or timelines. Decisions stayed at his level. Information did not flow downward. And whenever a delay occurred, the same mechanism activated: identify an external cause, document it, shift responsibility.

Over time, the author understood what he was watching. Not a busy manager under pressure, but a structural pattern: the deliberate separation of responsibility from ownership.

“The issue is not lateness. It is the deliberate separation between responsibility and ownership. When a manager operates that way, delay is no longer a risk. It becomes the operating model.”

What accountability avoidance looks like

The chapter describes three signatures.

The justification infrastructure

The deflecting manager invests real energy in maintaining a record of unmet dependencies, late inputs and unclear requirements, ready to explain any shortfall. The effort that goes into building the defence is effort that does not go into delivery.

Documentation as defence

Documentation should be a communication tool: it tells people what is happening so they can act. In this pattern it becomes a liability management tool. Emails are written to establish who was told what, not to solve anything.

No anticipation

This is the most diagnostic feature. Ordinary difficulty is unexpected; a capable manager sees it coming more often than not, raises it early and adjusts the plan. Structural accountability avoidance never anticipates. It explains afterwards.

The double failure

Upward: a distorted picture

Leadership receives a steady account of external causes instead of an accurate picture of performance. Decisions about resources, priorities and people are made on false information.

Downward: a disconnected team

The team is deprived of the information, direction and engagement it needs. It cannot help solve problems it was never told about. Richard Hackman’s research on team design shows that a team’s capability depends heavily on clear direction and enabling structure, exactly what this pattern withholds. There is also an uncomfortable logic to it: a team that is kept uninformed cannot be used to hold the manager accountable.

What the team learns

Initiative erodes

Adam Grant and Susan Ashford define proactive behaviour as self-initiated action to improve a situation. It requires confidence that taking initiative will be supported. Under a deflecting manager, initiative creates exposure, so people stop taking it.

Collaboration turns into positioning

Collaboration requires believing that working together will produce better results, and that credit and accountability will be shared fairly. When the manager’s model is to move blame elsewhere, team members start protecting themselves from each other too.

Addressing the pattern

If you manage the manager

Do not rely only on formal reporting. Engage directly with the team, transparently, and ask about risks before deadlines rather than causes after them. Hold the manager accountable for anticipation: “What did you see coming, and when did you raise it?”

If you are a peer

Document your own commitments and information-sharing precisely. The book is clear that this is not meant as a defensive move. It creates the clarity the deflecting manager is not providing, and it makes the pattern easier to see for everyone.

If you recognise yourself

The corrective is straightforward: shift from documenting causes to anticipating risks. Each week, ask what could delay the work in the next month, raise it with the people who can help, and share it with your team. That one change converts documentation from a shield back into a tool.

Warning signs

• Every missed deadline has a different external cause, but the misses keep coming.
• Status reports explain the past in detail and say little about upcoming risks.
• The team cannot describe the project’s priorities or timeline.
• Escalations arrive only after deadlines are missed, never before.
• Team members have started copying each other on emails “for the record”.

The cost of separation

Separating responsibility from ownership is not a minor dysfunction. Its costs are real and measurable, and they stay largely invisible until the gap between the official narrative and operational reality becomes too wide to hold. What eventually became clear to the author about the colleague he describes was not that he was malicious. It was that the pattern had become his way of working, and his team’s way of surviving.

“When a manager operates by separating responsibility from ownership, delay is no longer a risk. It becomes the operating model. And the team does not learn how to deliver. It learns how to protect itself.”