Series B Biotech COO: Why Full Autonomy Creates Paralysis

When Founder Proximity Stops Scaling: The Series B Authority Gap

They gave the new COO “full autonomy.” Six months later, he had stopped making decisions.

Not because he lacked experience. He had run complex operations inside a much larger pharmaceutical company — two launches, a strong bench, a reputation that made the board exhale. He stopped because every decision carried an invisible second question: is this actually mine?

Could he change the manufacturing partner, or was that relationship still the founder’s? Could he hire the regulatory leader, or was that a board-level appointment? When a clinical vendor missed an enrollment milestone, was resetting it his call — or would escalating signal he couldn’t handle the role?

He had accountability. He had a senior title. He had no map of the authority underneath either one.

The company called it autonomy. What it had built was drift. Not a crash — drift, which is harder to detect and, in some ways, more dangerous. The role had transferred. The founder’s operating system had not.

Founder Proximity Is an Operating System — Until It Stops Scaling

At Series A, proximity carries context. In a fifteen-person company, the founder knows the CRO terms because she negotiated them herself, knows which board member cares most about regulatory sequencing, knows which scientific compromises are non-negotiable and which are merely preferences. The team absorbs all of it through access — the hallway conversation, the overheard call, the ambient awareness of everyone working within earshot of everyone else.

Then the Series B closes, and the company goes from fifteen people to forty-five in eight months. New VPs, a COO, a head of HR, new vendors, new programs, new investors. The hallway stops working. The unwritten rules, the implicit priorities, the “we’d never do that” instincts — they stop circulating.

But nobody notices, because the founder still has the information. She has simply stopped transmitting it.

This is where many companies misread the moment. They believe they are delegating work. They are actually handing over decisions that depend on a body of knowledge that still lives inside one person’s head. The accountability moves before the context does.

That is the Series B authority gap. And the failure it produces rarely looks like one catastrophic decision. It looks like accumulated delay: milestones slip, vendors wait, hiring stalls, and choices migrate upward because no one can see where authority actually sits.

The mechanism is quiet. The operator makes a decision. It bumps into an invisible boundary — the founder’s unstated preference, the board’s unspoken expectation, an advisor’s informal influence. He gets corrected. Not harshly: a raised eyebrow, a “let’s talk about that.” And he recalibrates — not toward better decisions, but toward fewer decisions. Autonomy doesn’t get revoked. It erodes.

Track Limits: Why Visible Boundaries Increase Decision Speed

There is a useful parallel in Formula 1, and it points to a principle I’ve written about at length: the Track Limits Principle. Here it functions as the supporting mechanism, not the whole story.

In F1, a white line defines the legal edge of the circuit. Put all four wheels beyond it and the lap can be deleted or a penalty can follow; repeat it and the black-and-white warning flag comes out. The line restricts the driver. It also makes speed possible. A driver can place the car right against a visible, consistently enforced edge, lap after lap, because the boundary is known.

Senior executives operate the same way. They do not need approval for every decision. They need to know what they own, which inputs are mandatory, what must be disclosed, what triggers escalation, and which decisions remain reserved to the CEO or board. Ambiguity does not create entrepreneurial freedom. It shifts capacity from execution toward political risk management.

Kimi Räikkönen’s famous “leave me alone, I know what I’m doing” radio message at the 2012 Abu Dhabi Grand Prix — sent as his engineer relayed the gap to Alonso behind him — was not a rejection of his team. It was an experienced driver asking the pit wall to stop narrating a race he believed he understood. He won. That is the operating condition founders say they want: a senior leader who can execute without constant intervention. But that moment has to be earned through shared context and visible boundaries built before the race gets difficult — not granted by the words “full autonomy.”

The Series B COO gets the freedom without the boundaries, and then learns where the edges are only by crossing them.

The Series B Authority Transfer

The fix is not a bigger promise of autonomy. It is a transfer — of six things the founder currently holds and the organization now needs.

1. Transfer the decisions, not the category. “You own operations” is not a delegation; it’s a fog. Name the actual recurring decisions and say which move with the role and which stay reserved: clinical-vendor performance, manufacturing partnerships, headcount, program resource shifts, regulatory hiring, development timelines, vendor termination, budget movement. Every major domain needs a single process owner — the final voice, not the only voice. The COO can own the manufacturing-partner decision while CMC defines technical requirements, Quality retains required approval, Regulatory assesses filing consequence, and Finance models exposure. Shared input is necessary. Shared ownership is where velocity goes to die.

2. Transfer the context. Authority without history invites avoidable errors. The new leader needs the story underneath the decisions: what was already committed, which alternatives were rejected and why, which scientific constraints are fixed, what the board expects, which relationships are sensitive, what runway assumptions sit beneath the plan. A one-page authority map cannot substitute for this. It tells you who decides; it does not tell you what the decider needs to know.

3. Transfer the relationships. The founder holds personal trust with investors, investigators, advisors, and scientific partners. An introduction is not a transfer. The COO has to become a legitimate counterpart before being held accountable for the relationship — otherwise the founder remains the real owner and the COO carries the blame without the standing.

4. Define escalation by consequence, not anxiety. Escalation should trigger on patient or regulatory impact, deviation from approved strategy, unbudgeted financial exposure, irreversibility, material timeline effect, or board-reserved matters — not on whether a choice happens to make the founder uneasy. And financial authority should not rest on dollar amount alone. A $200K unbudgeted commitment that changes the development plan can warrant more scrutiny than a $1M payment already inside the approved manufacturing budget. Weigh budgeted vs. unbudgeted, reversible vs. irreversible, single-year vs. multiyear, operational vs. strategic.

5. Externalize the operating judgment. The founder’s instincts about how the company decides need to become text once she is no longer in every conversation. In life sciences that means principles with a hierarchy, not slogans: patient safety overrides schedule; evidence determines the decision while runway determines the sequence; reversible decisions move fast and irreversible ones earn scrutiny; bad news travels upward faster than good news; debate stays open until the decision and accountability begins after it. And the one that anchors the whole piece: no executive is accountable for a decision they lack the information or authority to make.

6. Test the system under disagreement. The authority model is not proven when everyone agrees. It is proven the first time the COO makes a legitimate decision the founder would not have made — and the founder lets it stand. A map is not governance. Governance is what happens when the first hard exception arrives.

Series B Biotech COO: Green, Yellow, Red — With One Rule

Translated into something a new COO can internalize in an afternoon:

Green — decide and communicate. Full authority. The leader decides and notifies as needed: hiring below VP level, vendor contracts under the defined threshold, operational process changes, internal communications. No permission. No “checking in.”

Yellow — decide after required consultation. The leader still owns the decision, but named parties must give input before commitment: VP-level hiring, contracts near the upper threshold, shifts in resource allocation between programs, changes to clinical-operations timelines. The consultation is for input, not approval, and it happens before the decision, not after.

Red — reserved. The CEO or board decides; the COO prepares the recommendation and owns execution once approved: strategic pivots, commitments above the board threshold, changes to the clinical development plan or regulatory strategy, anything touching patient safety.

The one rule that keeps the system honest: yellow must never become hidden approval. If a required consultation can quietly veto the decision, it isn’t yellow — it’s red, and it should be labeled that way. Mislabeled yellow is exactly how autonomy erodes without anyone deciding to take it away.

The Founder Is Not the Only Bottleneck

It is tempting to locate the whole problem in the founder — the brilliant scientist who says “I trust you” and means it, then corrects every decision that doesn’t match her instincts. That story is real, and it deserves the vulnerability to name it. Founders build companies by holding everything; scaling requires releasing things; and you cannot hand off what you have never had to describe.

But the founder is usually the visible bottleneck, not the only one. The board frequently helped build it. Directors call the founder directly instead of the COO. Investors issue operating instructions outside formal governance. Scientific advisors exercise informal vetoes. The board tells the founder to delegate while continuing to route every difficult question back through her. That produces a role with formal authority and an organization trained to go around it.

So before a board concludes the COO search failed, it should ask a harder set of questions. Did we define the mandate? Did we transfer enough authority — and the context behind it? Did we stop bypassing the role? Did we align the founder’s scientific authority with the COO’s operating authority? Sometimes the candidate was wrong. Sometimes the system never let the candidate become right. The board cannot ask a founder to delegate while it keeps treating her as the answer to every hard decision.

The COO Profile Depends on What the Founder Can Transfer

This is where the search begins — upstream of the résumé. A Series B biotech does not automatically need the most senior pharma operator it can attract. The mid-cap veteran often struggles not for lack of talent but because they expect inherited institutional boundaries that a forty-five-person company simply does not have.

The right profile depends on what the founder can actually transfer. It may call for a builder who creates structure where none exists, an integrator who connects science and execution, a translator among founder, board, and operating team, or a scaling leader who can build the management layer beneath them. So the assessment should test less for what the candidate has run and more for how they behave in the gap: How do they create clarity when none is handed to them? How do they negotiate authority with a founder without making the founder the enemy? Can they operate under scientific uncertainty, and escalate without surrendering ownership? Can they tell the difference between a missing process and a missing measure of trust?

The strongest candidate is not the one who needs no boundaries. It is the one who can help the company draw the right ones — and then push to the edge of them.

What You’re Actually Building Toward

The goal is not to constrain the COO. It is to reach the point where the founder no longer has to interpret every decision and the COO no longer has to predict every invisible reaction.

That point does not arrive when the founder says “I trust you.” It arrives when the decisions, the context, the relationships, the escalation logic, and the operating principles have moved far enough out of the founder’s head that the company can run without her proximity. Decision velocity improves. Fewer issues escalate reflexively. The founder and COO still disagree — but now they can tell whether the disagreement is about judgment, about authority, or about a rule no one ever wrote down.

The title can transfer in a single announcement. The operating system cannot. That is the work Series B companies underestimate.

The COO does not need unlimited freedom. He needs enough of the founder’s context — and enough visible authority — that the company stops depending on either one of them to move.

That is when a senior leader can finally say leave me alone, I know what I’m doing — and be right.

---

Charlie Solórzano is a Managing Partner at Alder Koten, a boutique executive search firm specializing in C-suite and board placements across the U.S. and Mexico markets, where he leads the firm's life sciences practice. He advises founders, investors, and boards across biopharma, medical devices, and diagnostics on leadership transitions using The Race Conditions Model™, a proprietary diagnostic framework built on the thesis that leadership success is determined by conditions, not credentials. He also works closely with the IMD Search Group on international assignments