The Person They Call When Things Break

In banking, someone has to hold the broken things. The failed integration. The regulatory finding. The team that fell apart after the third restructuring in two years. Someone has to step in, map the damage, and reassemble it — usually on a timeline that makes no allowance for the fact that the damage took years to accumulate.

Everyone in the industry knows who that person is. Every floor has one. Every leadership team relies on one. The person whose phone rings on a Sunday evening. The person whose LinkedIn profile shows more role changes than anyone in their peer group, and each one looks like a promotion. From outside.

From inside, each one is the same thing: someone else's fire.

...

In the banking leaders I work with, a pattern appears that is rare elsewhere. The Fixer. If I solve it, I am needed. If I am needed, I have a place. If I have a place, I exist.

The pattern did not appear from nowhere. Post-2008, European banking went through something that reshaped its leadership culture from the inside. Systemic failure became personal responsibility — not philosophically, but operationally. Someone had to hold the pieces when the institution could not hold itself. The leaders who stepped into that space were rewarded for it. Promoted for it. Given the next crisis for it.

And then the next. And the next.

The Fixer's career is a sequence of emergencies that never becomes a direction. Each role change is an escalation. Each escalation feels like trust. The institution says: "We need you on this." The Fixer hears: "You matter." The distinction between the two collapses, and the collapse is invisible because the fires are real.

A client described it to me once. Senior director. Two decades in the same institution, though the titles changed every eighteen months. He walked me through his career — systematically, precisely, every stakeholder mapped, every crisis catalogued. He spoke for fifteen minutes.

I said: "You described the system. You didn't describe yourself inside it."

He went still. His breathing changed — slower, shallower, as though the air in the room had become something he needed to ration. Then, very quietly: "I don't know who I am if things don't need fixing."

The loyalty trap

The Fixer cannot leave. Not because of a contract. Because leaving means the thing he has been fixing will break again. His loyalty is to the problem, not the institution. The institution merely employs him. The problem needs him.

This is the trap nobody names. Every leadership development programme tells him to think strategically, to build rather than rescue, to delegate the operational work. He can do all of this. He has the systemic intelligence to see the entire board — where the pressure points live, where the failure modes are, where the institution is vulnerable. That intelligence is extraordinary. And he deploys it, every time, for rescue rather than architecture.

He delegates the stable work. He keeps the broken work. Not because he lacks delegation skills. Because stable work does not tell him he is needed. And the need is the fuel.

The loyalty trap has a specific cost that takes years to see. The colleague who gets promoted to the board is less experienced, less capable by the Fixer's measure — but a builder. The institution promotes the person who constructed something new over the person who prevented everything old from collapsing. The Fixer understands this rationally. He cannot make himself build. Because building means letting the broken things be broken. And the broken things are where he lives.

The conscious pattern

Here is what makes the Fixer different from most leaders I work with. He can name it. He can describe the coping mechanism, trace its origins, map its cost. He can tell you exactly what he is doing and why. He uses language like "triage" and "contain" and "remediate" — operational words that keep the emotional truth at arm's length, but the operational map is accurate.

He knows he is avoiding discomfort. He knows the avoidance is a strategy. He knows the strategy was built in the years after the crisis, when the institution needed someone to absorb risk personally so the institution did not have to.

What he cannot do is stop. Because the system has not stopped being broken. And as long as the system is broken, the pattern is correct. The difficulty with a correct pattern is that it never announces its own redundancy. It simply keeps solving, and the solving keeps confirming that solving is what matters.

This is the version of stuckness that no amount of self-awareness resolves. Consciousness without choice. He can see the pattern, hold it in his hands, describe its weight — and put it back on, because the organisation is already calling with the next fire.

...

The question for the leader who fixes is not whether the system needs saving. It usually does. The question is whether his identity requires the system to stay broken — and what becomes possible the morning he lets something stay unfixed and discovers he is still there.

...

Related articles