The best technical expert in the room is often the least prepared person to define strategy, operational and financial targets. Promotion pipelines predictably produce this outcome, rewarding technical mastery all the way up to the point where someone has to run a function rather than a project or a team.
A well-known study of more than a thousand promotions across U.S. sales organizations found that the strongest individual performers were the most likely to get promoted into management, and the least likely to succeed once they got there. A doubling of someone’s pre-promotion performance corresponded to a measurable decline in their management effectiveness once promoted, according to research published in the Quarterly Journal of Economics and summarized by Harvard Business Review.
Life sciences runs the same pattern with a different kind of expertise. Deep scientific or technical mastery gets someone into a leadership role. It does not prepare them to run an organization.
Deep Expertise Gets You Promoted. It Doesn’t Prepare You to Run a Function.
Life sciences organizations reward technical excellence, and they should. The people who understand the science best are often the people best positioned to make sound scientific decisions at scale. The problem shows up when that same expertise becomes the sole basis for promotion into roles that require an entirely different set of judgments: setting strategy, operational and financial targets, defending a portfolio decision to an executive team or board, and understanding why a scientifically sound project might still not be commercially viable.
Nobody teaches that transition explicitly because the assumption underlying most promotion decisions is that competence in one domain transfers to competence in another. It rarely does on its own. A brilliant translational scientist can spend a decade mastering their discipline and still have never built a financial model, negotiated a budget against competing priorities, or made a resourcing decision that trades one promising program against another.
What Business Acumen Requires at This Level
Business acumen at the senior level in life sciences is specific, not general. It means reading a P&L well enough to know which questions to ask finance, rather than accepting the numbers at face value. It means understanding how a portfolio decision made in research today shows up as a resourcing constraint in commercial three years from now.
It also means learning to set and manage execution against strategy, not just develop the strategy itself. Plenty of technical leaders can build a compelling five-year plan. Far fewer have practiced translating that plan into quarterly resourcing decisions, then holding their own teams accountable to it when the science does not cooperate with the timeline.
Short- and long-range planning are their own skills, separate from scientific planning. A research timeline follows the logic of the science. A business planning cycle follows the logic of budgets, investor expectations, and competitive pressures, and these logics do not always move at the same pace. Leaders who have only ever operated inside the first one struggle to reconcile it with the second.
How the Gap Shows Up Differently Across Functions
The specific content of the gap changes depending on which function someone comes up through. A Research leader promoted into a portfolio role often struggles most with prioritization: deciding which of several scientifically sound programs gets funded when the budget cannot support all of them. A Tech Ops leader promoted into a plant or network leadership role often struggles with capital allocation, weighing a compliance-driven capital request against a capacity-expansion request from the same limited pool of money. A Regulatory Affairs leader stepping into a broader role often has the deepest command of risk in the room and the least practice defending a regulatory strategy to a cross-functional team.
Business acumen training that treats all three of these leaders the same way misses the point. Each of them needs the same underlying capabilities: reading a P&L, understanding portfolio trade-offs, and planning across time horizons, but they need to practice applying them to the specific decisions their own function faces.
Where to Start
Business acumen doesn’t develop by accident, and it doesn’t develop from a single coaching relationship either. It develops through repeated practice with the actual decisions someone’s new role requires: reading a P&L, weighing portfolio trade-offs, reconciling a research timeline against a budget cycle.
The next time someone with deep technical expertise gets promoted into a role that owns a budget or a portfolio decision, don’t just assign them an executive coach and consider the transition handled. Ask whether that coach has run a similar function. Ask who is teaching the new leader to read a budget, not just to lead a meeting about one. And ask whether the training reflects the specific trade-offs their function faces, not a generic version of business acumen that could apply to anyone.
