Why Firing a Leader After a Crisis Is Not Real Accountability

 Twelve World Cup coaches will not finish this tournament employed. Boards make the same move every earnings season: a leader is removed, a statement about "renewed focus" goes out, and the organization treats the crisis as closed. This post explains why that sequence is not accountability, and what building real accountability looks like instead.

The problem with treating removal as accountability

When a leader is dismissed after a crisis, the decision answers a narrow question: who was closest to the result when it happened. It does not answer the question that actually determines whether the next crisis goes better: where was ownership never clearly designed in the first place. By the time a federation removes a coach mid-tournament, the real execution gaps, recruitment decisions, preparation cycles, selection under pressure, were built into the structure months earlier. The result did not cause the failure. It exposed one that already existed.

What the PACE Framework says about accountability

The PACE Framework, developed by advisory thinking partner Bhaviik Kumar over fifteen years of transformation work across pharma, FMCG, and manufacturing, treats Accountability as one of four interdependent pillars alongside Planning, Communication, and Engagement. Within PACE, accountability is not about identifying who to blame. It is defined as the architecture of ownership that turns intention into measurable outcomes, and it has to be designed before pressure arrives, not assembled after a crisis exposes its absence.

The Ladder of Accountability

Organizations, like individuals, sit on different rungs of what Bhaviik calls the Ladder of Accountability in his book LEAD with PACE. The lower rungs include denial (there is no problem), blame (it's someone else's fault), and excuses (I couldn't because of circumstances outside my control). A leadership change made in the middle of a crisis is almost always a blame-rung decision dressed up as decisive leadership. Genuine ownership sits at the top of the ladder, and it is built well before a crisis forces the question.

A manufacturing case study

A manufacturing plant Bhaviik worked with had a recurring quality defect problem. Leadership's initial response was public blame sessions whenever defects surfaced, with supervisors calling out operators in front of their teams. The approach backfired. Operators began hiding minor issues to avoid public humiliation, and small problems compounded into major failures that went undetected until products had already shipped.

The plant head who resolved this did not remove anyone publicly. She replaced the blame sessions with structured "failure huddles" focused entirely on what the system had failed to catch, never on individual punishment. Operators began surfacing problems again because doing so was finally safe. Within six months, defect rates fell by 30%. The people had not changed. The structure around them had.

How to surface accountability gaps before a crisis forces them into the open

A practical diagnostic exercise for any leadership team:

1. Trace every missed outcome backward. For each significant miss, ask who the single accountable person was. If the honest answer is "the team," a gap exists.
2. Listen for diffusion language. Phrases like "we assumed they would" or "that wasn't in our scope" are early warning signals of an ownership void.
3. Check for duplication. Overlapping responsibility with no clear leader is as dangerous as having no owner at all.
4. Connect every missed metric to a name, not a department.

Doing this quietly, before a crisis, is far cheaper than doing it publicly during one.

The takeaway for leaders

Real accountability is not a verdict handed down after a bad result. It is architecture built before pressure arrives to test it. The next time your organization misses a number, the more useful question is not "who do we remove," but "how long has this gap been invisible."

Frequently Asked Questions

What is the PACE Framework?

PACE stands for Planning, Accountability, Communication, and Engagement, a framework developed by Bhaviik Kumar over fifteen years of transformation advisory work across pharma, FMCG, and manufacturing sectors, designed to turn execution chaos into sustainable, measurable results.

Why do organizational transformations fail? 

Most transformations fail not at the strategy stage but at the execution layer, often because ownership of critical handoffs was assumed rather than clearly designed and named before pressure arrived to test it.

How do you build accountability in a transformation? 

By naming a single accountable owner for every critical process handoff before a crisis begins, and regularly testing whether that ownership is real by tracing missed outcomes back to a specific name rather than a team or department.

What does a thinking partner do for a CXO? 

A thinking partner works in the room where decisions are made, helping design ownership architecture before a crisis, rather than delivering a diagnosis and a deck after the damage is already visible.

How do you measure ROI from organizational change? 

By tying accountability and execution improvements directly to operational metrics, such as defect rates, delivery timelines, or regulatory outcomes, rather than treating culture change as an intangible, unmeasurable investment.