Picture a capital committee meeting. The chief medical officer wants a second hybrid operating theatre. The finance director wants to know the payback period. The CMO talks about complication rates and waiting lists. The finance director talks about depreciation and case mix. Both are right. Neither is persuaded. The item is deferred to next quarter, which is how hospitals say no without anyone having to say it.
This scene plays out constantly, and the usual diagnosis is a culture clash between clinicians and managers. That diagnosis is too comfortable. The real problem is that each side has been allowed to treat the other’s language as optional.
The evidence is thinner than both camps claim
Advocates of clinical leadership often cite a 2011 study in Social Science & Medicine by Amanda Goodall. She looked at the top 100 US hospitals in three specialties in the 2009 US News & World Report rankings, traced the backgrounds of their 300 chief executives, and found a strong association between physician CEOs and higher quality rankings.
In England, Gianluca Veronesi, Ian Kirkpatrick and Francesco Vallascas published a study in the same journal in 2013 looking at NHS hospital trust boards. They found that a higher share of doctors on the board was associated with better ratings from the regulator, including, interestingly, ratings for financial management.
Both papers are useful. Neither shows that clinicians make better leaders. Goodall herself stressed that her findings did not prove causation. High-performing hospitals may simply attract physician leaders, or choose them. The honest reading is narrower: organisations where clinical expertise sits at the top table do not appear to suffer for it, and may benefit.
That narrower reading is also the more interesting one. It suggests that what matters is less the job title of the person in charge than whether clinical and financial reasoning are actually present in the same decision.
What clinical fluency means for an executive
Nobody expects a chief financial officer to read an echocardiogram. Clinical fluency is something more practical. It is knowing enough to ask the question that exposes the real cost of a decision.
An executive with clinical fluency understands that length of stay is not only a bed-management problem, but a consequence of when consultants round, when diagnostics are available at weekends and how discharge medications are dispensed. They know that a new service line is not just a building and a business case, but a set of rotas that has to be staffed at three in the morning. They can tell the difference between a clinician asking for equipment out of genuine clinical need and one asking out of professional interest, because they understand the pathway well enough to see where it actually changes outcomes.
Without this, executives manage what they can measure. Financial metrics are easy to measure. Clinical risk mostly is not, until something goes badly wrong.
What business fluency means for a clinician
The reverse gap is just as costly and more often excused. Many senior clinicians still treat budgets as an administrative obstacle rather than a clinical constraint. That is a luxury. Every pound or dollar spent on one pathway is not spent on another, and the patients on the other pathway are just as real.
Business fluency for a clinician means reading a service-line profit and loss statement without assuming it is a trick. It means understanding why a procedure that generates revenue for the hospital might still be a poor use of theatre time. It means knowing how the organisation is paid, because payment rules shape what gets funded far more than clinical evidence does.
Clinicians who acquire this fluency become dangerous in the best sense. They can walk into that capital committee and argue in the finance director’s terms: here is the throughput, here is the avoided cost of complications, here is what happens to our waiting-list penalties if we do nothing.
The same theatre, argued properly
Go back to the capital committee and replay it with both kinds of fluency in the room. The illustrative numbers here are invented for the sake of the example; the structure is the point.
The clinical case begins not with complication rates in general but with a specific pathway. Patients who need combined open and endovascular procedures are currently waiting, some are being transferred elsewhere, and some are having two procedures where one would do. Each of those facts has a financial shadow. A transfer out is income lost and often a bed-day cost absorbed first. A staged procedure uses theatre time twice. A complication extends a stay that, under most activity-based payment systems, the hospital is not fully paid for.
The financial case, meanwhile, stops pretending that depreciation is the only cost. A second hybrid theatre needs radiographers, specialist nurses and anaesthetic cover. If those people do not exist in the local labour market, the business case is fiction, however good the payback period looks. A finance director with clinical fluency asks about the rota before the spreadsheet.
When both sides argue this way, the committee is no longer choosing between quality and money. It is choosing between two fully costed versions of the future. Sometimes the answer is still no. But it is a no that both sides understand, and that can be revisited when the facts change.
Where the money rules come in
One reason the translation problem persists is that the payment system speaks a third language neither side has fully learned. Under diagnosis-related group or tariff systems, a hospital is paid a fixed amount for a category of case. That creates incentives that are invisible to a clinician who does not know the rules and puzzling to a finance director who does not know the medicine.
A procedure that shortens length of stay can be financially attractive under a fixed tariff and unattractive under per-diem payment. A complication can generate extra income in one system and a penalty in another. Readmission rules, quality-linked payments and waiting-time targets all shift the calculation. The executive who understands both the clinical pathway and the payment rules can see where they collide, and that is often where the largest gains, and the worst perverse incentives, are hiding.
The incentive that keeps the gap open
If both kinds of fluency are so obviously useful, why are they rare?
Partly because professional identity rewards staying in one lane. A surgeon who spends time on spreadsheets risks being seen by peers as having “gone over to management.” A finance director who asks detailed clinical questions risks being told to stay out of medicine. Each side protects its expertise by keeping the other at arm’s length.
Partly because organisations are structured to keep them apart. Clinical and financial reporting lines often meet only at the executive table. Training programmes are separate. Career paths rarely cross.
And partly because ignorance is useful. A clinician who does not understand the budget can always blame management for saying no. An executive who does not understand the clinical pathway can always blame the doctors when targets are missed. Mutual incomprehension gives everyone an alibi.
The case for staying in your lane
There is a respectable counterargument. Specialisation exists because it works. A chief financial officer who spends time learning clinical pathways is spending less time on treasury, audit and the payer contracts that keep the hospital solvent. A surgeon learning to read a profit and loss statement is not operating. Organisations, the argument goes, should build good interfaces between experts, not ask each expert to become half of the other.
That argument partly holds. Nobody needs a board of polymaths, and the hybrid who is mediocre at both disciplines is a real risk. There is also a failure mode in which clinicians who acquire business fluency start speaking only in the language of margins, and lose the clinical perspective that made them valuable at the table.
But the interface argument assumes the interface works, and the capital committee scene shows it often does not. The fluency being asked for is modest: enough to know which question to ask and to recognise a bad answer. That is not a second career. It is the minimum needed to make joint decisions without one side simply deferring to the other.
Who has to move first
Chief executives set the tone, and the most effective single thing they can do is refuse to take decisions on business cases that have only been argued in one language. Send them back. It takes two rounds before people start writing them properly.
Boards and non-executive directors can ask the same questions of both sides. A board that questions a clinical director about financial assumptions, and a finance director about clinical assumptions, signals that neither can hide behind expertise.
Medical schools and residency programmes can introduce the basics of how hospitals are paid, not as a management elective but as part of understanding why care is organised the way it is. And finance and management training programmes in health can include structured clinical exposure, which some already do, as standard rather than an optional extra.
Payers and regulators have a role too. The more payment rules change, the more the translation gap costs. Simpler, more stable rules would reduce the premium on translation. In the meantime, the useful signal to watch in any hospital is simple: are clinical directors given real budgets and real financial data, or are they consulted and then overruled?
Closing the gap without a new degree
The fix is less glamorous than an MBA or a clinical leadership fellowship, though both have their place.
- Pair decisions, not people. Require every significant business case to be jointly signed by a clinical and a financial lead, each accountable for the other’s assumptions.
- Rotate exposure. Have executives spend structured time on wards and in theatres, and clinicians spend time in the finance and contracting teams, with a specific question to answer.
- Share the same numbers. Give clinical directors the same service-line financial data that executives see, without first translating it into a friendlier format.
There is also a quiet test of whether any of this is working. Look at the business cases that were rejected last year and ask who wrote the rejection. If the answer is always finance, the organisation has a translation problem, because either clinicians are submitting cases that cannot survive financial scrutiny, or finance is rejecting cases it does not understand. If rejections come from joint review, with the clinical lead sometimes arguing against a colleague’s proposal on clinical grounds, the languages have started to merge.
The same test works in reverse. How many cost-saving schemes were stopped, or changed, because a clinician showed where the saving would reappear as harm or as cost somewhere else? In hospitals where the answer is none, clinical reasoning is probably not reaching the decisions that matter.
The aim is not to turn doctors into accountants or accountants into doctors. It is to make it impossible for either to hide behind the other’s language.
The hospitals that do this well will not necessarily have physician chief executives. They will have boards where nobody is allowed to say “that’s not my area.”
Where have you seen clinical and financial leaders genuinely speak each other’s language, and what made it work? Share your experience in the comments.
