Governance vs. Management in Clinical Development
The most frequent governance failure in clinical-stage biopharma is not a board that is too passive. It is a board that does not know the difference between governing and managing. Directors who cross the line from oversight to operation create problems that are every bit as serious as directors who rubber-stamp management's recommendations without scrutiny.
The governance-management boundary is conceptually simple: the board sets strategy and oversees execution; management executes and reports. In practice, this boundary is extraordinarily difficult to maintain in biopharma, because the decisions that management makes about clinical development have existential consequences for the company, and directors with expertise and strong opinions find it nearly impossible to resist the urge to direct rather than oversee.
Understanding where this boundary sits — and developing the discipline to respect it — is one of the most important governance skills a biopharma board member can cultivate.
Why the Boundary Matters
Accountability Requires Clarity
When the board makes management decisions, it destroys the accountability structure that governance depends on. If the board directs the CEO to use a specific trial design, a specific endpoint, or a specific regulatory strategy, the board cannot later hold the CEO accountable if that decision proves wrong. The CEO can reasonably say: the board told me to do it this way.
Effective governance requires that management own its decisions. The board's role is to ensure that management's decisions are informed, that the process for making them is sound, and that the risks are understood. But the decisions themselves must belong to management. This is the only way to maintain the accountability that allows the board to evaluate management's performance and, when necessary, to make leadership changes.
Expertise Does Not Equal Authority
Many biopharma boards include directors with deep clinical development expertise — former CMOs, experienced drug developers, physicians who have spent careers in the therapeutic area the company is pursuing. These directors bring enormous value to the board's oversight function. They can ask informed questions, evaluate management's recommendations with genuine understanding, and identify risks that less experienced directors might miss.
But expertise does not confer the right to direct. A former CMO who serves as a board member is not the company's CMO. Their role is to ensure that the actual CMO is making sound decisions, not to make those decisions themselves. The moment a board member begins directing clinical development decisions — specifying trial endpoints, choosing contract research organizations, determining dosing strategies — they have crossed from governance into management.
This is a difficult discipline for accomplished people. When you see something being done in a way you believe is wrong, the natural instinct is to correct it. But a board member who corrects management by taking over the decision is solving a short-term problem and creating a long-term governance failure.
Management Needs Room to Operate
Clinical development is complex, fast-moving, and requires hundreds of interconnected decisions that must be made by people who are close to the work. The trial must be designed, sites must be selected, patients must be enrolled, data must be monitored, regulatory interactions must be managed. These decisions require expertise, context, and speed that the board — meeting quarterly or monthly — cannot provide.
A board that involves itself in operational decisions slows the company down. Management spends time preparing materials and explanations for board-level discussions of decisions that should be made at the management level. The decision-making process becomes cumbersome. And talented executives — the people the company needs to succeed — become frustrated and leave because they did not sign up to have their professional judgment second-guessed by a part-time board.
Where the Board's Role Begins and Ends
The boundary is not a bright line. It is a zone, and reasonable people can disagree about where specific decisions fall. But some principles are clear.
The Board Governs Strategy; Management Executes It
The board should approve the overall clinical development strategy. This means the board should be involved in decisions like: Should we advance this program to Phase III? Should we pursue an accelerated approval pathway? Should we add a second indication? Should we prioritize the oncology program or the immunology program?
These are strategic decisions with major capital, risk, and timeline implications. They define the company's direction. They belong to the board.
What the board should not do is direct how the strategy is executed. Once the board approves advancement to Phase III, the design of the trial — the specific endpoints, the statistical analysis plan, the number of sites, the enrollment criteria — belongs to management and its scientific advisors. The board should review the trial design, ask questions, and satisfy itself that the approach is sound. But it should not redesign the trial.
The Board Oversees Risk; Management Manages It
The board's role in risk management is to ensure that management has identified the key risks to the clinical program, has plans to mitigate them, and is monitoring them actively. The board should understand what happens if enrollment is slower than projected, what the contingency is if a safety signal emerges, and how the company will respond if the competitive landscape shifts.
What the board should not do is manage the risks directly. If enrollment is slow, management — not the board — should determine whether to add sites, adjust inclusion criteria, or extend the timeline. If a safety signal emerges, the medical monitor and the data safety monitoring board should evaluate it. The board should receive timely information about these developments, but it should not direct the response.
The Board Evaluates the CEO; It Does Not Bypass the CEO
Perhaps the most important aspect of the governance-management boundary is the board's relationship with the CEO. The board oversees the CEO. It sets the CEO's objectives, evaluates their performance, determines their compensation, and if necessary, replaces them. This is the board's most fundamental governance responsibility.
What the board should not do is bypass the CEO to direct other members of management. When a board member calls the Chief Medical Officer directly to express a view on trial design, or tells the VP of Finance to prepare a specific analysis, they are undermining the CEO's authority and creating confusion about who is in charge.
If a board member has a concern about how clinical development is being managed, the appropriate channel is to raise it with the CEO — either in a board meeting or in a private conversation. If the concern persists, it becomes a performance issue for the board to address with the CEO through the governance process. Going around the CEO is not governance. It is interference.
The Gray Zone
Some decisions genuinely fall in the gray zone between governance and management. These are decisions that have strategic implications significant enough to warrant board involvement but that also require operational judgment that the board may not possess.
Key Regulatory Interactions
The company's interactions with the FDA — particularly pre-IND meetings, end-of-Phase II meetings, and pre-NDA meetings — are strategic events with major implications for the company's development timeline and regulatory risk. The board should be informed about the objectives of these meetings, should review the briefing documents at a high level, and should receive a thorough debrief on the FDA's feedback.
But the board should not wordsmith the briefing document or direct the company's regulatory strategy in the meeting. These are specialized activities that require regulatory expertise and real-time judgment. The board's role is to ensure the company has competent regulatory guidance, that the strategy is consistent with the board-approved development plan, and that the FDA's feedback is honestly communicated to the board.
Data Safety Monitoring Board Interactions
The Data Safety Monitoring Board is an independent body that monitors safety and efficacy data during clinical trials. The DSMB may recommend modifications to the trial, suspension of enrollment, or early termination. These recommendations have enormous implications for the company.
The board should understand the DSMB's charter, should know who serves on it, and should receive timely reports on the DSMB's recommendations. But the board should not attempt to influence the DSMB's deliberations or to override its recommendations. The DSMB exists as an independent safeguard, and a board that interferes with its independence is creating both scientific and legal risk.
Partnership and Licensing Discussions
When management is in discussions with a potential partner about a licensing or co-development arrangement, the board should be involved in the strategic parameters — what rights the company is willing to license, what territory, what economics are acceptable. But management should have room to negotiate within those parameters without bringing every counteroffer back to the board for approval.
The governance discipline is to set the framework and the boundaries, then let management negotiate. The board reviews and approves the final deal. If management cannot reach a deal within the approved parameters, they return to the board for revised guidance.
How to Fix a Board That Has Crossed the Line
If your board has developed a habit of managing rather than governing, the correction begins with honest self-assessment. The board chair or lead independent director should raise the issue directly, ideally in an executive session without management present. The discussion should focus on specific examples — decisions the board made that should have been management's, interventions that bypassed the CEO, operational discussions that consumed board meeting time.
The CEO has a role here too. A CEO who is frustrated by board overreach should be able to raise the issue with the board chair. In healthy governance relationships, this is a conversation, not a confrontation. The CEO says: I need the board to trust me to execute, and I commit to keeping you informed and coming to you when I need strategic guidance. The board says: we commit to respecting the boundary, and we expect you to keep us informed and to make sound decisions.
Both sides must follow through. A board that commits to respecting the boundary but reverts to micromanagement at the first sign of trouble has not changed. A CEO who commits to transparency but withholds information when it is unfavorable has not earned the board's trust.
The governance-management boundary is not a wall. It is a working agreement between people who share the same objective — building a successful company — but who serve that objective in different ways. Respecting the boundary is not passive. It is the most active and disciplined form of governance there is.