What Pharma Does to Its Leaders

pharmaleadershipidentitycontrolexpert-to-leader

In pharma, consensus is the currency of survival. Every decision moves through a committee. Every committee moves through a process. The process is the point.

Everyone in the industry knows this. The regulated environment demands it. Patient safety requires it. The matrix validates it at every turn. And the leaders who thrive inside that structure — the ones who get promoted, who earn the trust of regulators and stakeholders alike — are the ones who master thoroughness.

What nobody examines is what thoroughness does to the person practising it.

...

In the leaders I work with across pharma, two patterns show up with remarkable consistency. The first is control — genuine, necessary, rooted in real consequences. The wrong compound released, the wrong data filed, the wrong process skipped: people get hurt. The control is earned. It is also, over time, total.

The second is orchestration. The matrix rewards the leader who can hold eight stakeholders in a single decision, who consults every voice, who moves the process forward without appearing to push. In pharma, pushing is suspect. Thoroughness is currency. The leader who orchestrates consensus is the leader who advances.

These two patterns — the Protector and the Conductor — create something specific. A leader whose caution is both professionally necessary and personally fortifying. A leader for whom the committee process is simultaneously the right way to make decisions and a permanent shield against being wrong.

The question is where one ends and the other begins.

A client once described it to me. Senior engineering director. Two decades in the industry. PhD. The kind of leader whose technical reviews were meticulous and whose team delivered consistently. He said: "I just want to make sure we have the data before we decide." Reasonable. Responsible. Exactly what his role required.

But when I asked what would happen if he made a decision without full data — if he trusted his judgement and moved — his jaw tightened. His hands, which had been resting on the table, moved to the arms of the chair. His body answered before his mind did.

It was not the data he was protecting.

The functional split

Here is where pharma gets particular. The engineering director and the marketing director sit in the same leadership team meeting. They share the same matrix, the same consensus culture, the same regulatory pressure. They hold entirely different beliefs about what keeps them safe.

He will not ask a question in a meeting unless he already knows the answer. For him, questions are admissions. Thirty years of a culture that promotes expertise have taught him that not knowing is not a gap — it is a disqualification. "Can you show me the evidence for that?" is his professional sentence. Underneath it lives a belief: if it cannot be measured, it does not exist. And if it does not exist, he does not have to feel it.

She will not assert a position unless the room has already arrived there. For her, directness is disruption. The same consensus culture that rewards his thoroughness rewards her collaboration — and penalises her visibility. She hedges: "I think maybe we could consider..." She frames her strategic thinking as team insight. The room hears agreement. She means something sharper, but sharper would violate the unspoken contract.

Each reads the other's behaviour as proof of their own pattern. He sees her hedging and thinks: she does not have the data. She sees his certainty and thinks: he does not have the room. Both are running survival strategies that were built for this environment. Both are invisible to themselves.

...

When pressure arrives — AI adoption, restructuring, the compression of timelines that pharma has always resisted — something specific happens. The thoroughness that protected patients begins to protect something else.

I see it in session after session. The leader who built a career on careful, consensus-driven decision-making encounters a situation that demands speed. The regulatory argument is ready: we cannot move faster, the process exists for a reason, patient safety requires diligence. All true. And underneath, a different sentence: if I move faster, I lose the structure that tells me I am doing this right.

The control pattern that was built to protect the patient is now protecting the leader's identity. The process that was designed for safety has become a fortress against uncertainty. The consensus that was genuine has become a way to never be the single person who decided.

This is not a flaw. It is a brilliant adaptation that served the leader and the organisation for years. The difficulty is that brilliant adaptations do not announce when they have outlived their purpose. They simply keep running — and the leader keeps obeying.

In a culture that rewards caution, the question that matters most is the one nobody asks: is the caution protecting the patient, or is it protecting you?

...

Related articles