When the company outgrows the team running it

We recently held a webinar with Nirav Sheth, Executive and Team Performance Coach and Founder of Stratosphere, LLC., focusing on what happens when leadership teams stall, and what CEOs can do about it. Here are some takeaways. Click here to watch the full webinar.

Ask a medtech leadership team what the number one priority is and ask each person separately. If you get four different answers, the problem is not focus. It is the way the team was built to make decisions. 

Most early-stage medtech teams are not short on talent. They are short on the thing that makes talent add up. Every function is doing its job well. R&D optimizes development. Regulatory manages risk. Commercial pushes for speed. Finance protects the runway. And still, milestones slip, decisions wait on one person and the hard conversations happen after the meeting rather than in it. 

Our team spends most of its time with companies in exactly that stretch, and the pattern is consistent enough to be worth naming. The ceiling these companies hit is usually not a talent ceiling. A leadership team is a system, and a system built for fifteen people does not automatically work at eighty. That is a hopeful diagnosis, because design problems can be fixed. 

Here is how the stall tends to unfold, what sits underneath it and how a team can find out where it actually stands. 

The stall rarely announces itself 

Stalls build slowly and every step along the way is reasonable at the time. 

In the early years the founder is the fastest path to a good decision, because the founder holds the most context. That is efficient, so it becomes the habit. Then the company hires real functional leaders. Each of them is excellent. R&D optimizes the development plan, regulatory protects the submission, commercial protects the launch date and finance protects the runway. What nobody notices is that no one is consistently responsible for the success of the whole company, so the decisions that span functions keep drifting back up to the person who always made them. 

Priorities separate next, and quietly. Ask four leaders what matters most this quarter and one says the clinical milestone, one says the submission, one says the raise and one says the launch. All four are right about their own function. None of them are working from the same plan. 

By the time the team is large enough for that to hurt, the meetings have gone cordial. Everyone agrees in the room. The real conversation happens in the hallway twenty minutes later, between two people who both had doubts and neither of whom said so. When commercial and quality finally collide before a launch, there is no shared way to resolve it, so the founder becomes the referee. When a milestone slips, every function can explain exactly what it did right, because the thing that failed lived in the space between two of them. 

And the hardest one sits on top of all of it. The early leader who was essential at 20 people is not scaling at 100. Everyone sees it. Nobody says it, out of loyalty or out of fear, and the standard quietly moves. 

None of that was ever decided. It accumulated. 

Ask: 

• If we polled the leadership team today, would we get one top priority or five? 

• When was the last time a real disagreement was aired in the room rather than after it? 

• What decision is currently waiting on one person who does not need to be in it? 

• Which milestone slipped without anyone being clearly wrong? 

A stalling team rarely looks broken. It looks busy. 

Scaling the company means scaling the team that runs it 

Every symptom in that story traces back to one root cause. The company scaled and the leadership team did not. The habits that worked at 20 or 30 employees are still running the place at a much larger size, so roles stay ambiguous, decisions stay informal and complexity quietly wins. 

This costs more in medtech than in most industries, because the speed-versus-risk tension here is not a dysfunction to be eliminated. It is structural. Quality and commercial are supposed to pull against each other. Regulatory and R&D are supposed to see the same timeline differently. A team with a working operating system turns that tension into a better decision. A team without one turns it into personal conflict, escalation and delay, and in a company with finite cash that delay has a number attached to it. 

Talent still matters. But past a certain size, how talented leaders work together starts to matter more than how talented any one of them is. That is the encouraging part, because the way a team works together is learnable and changeable in a way individual capability often is not. 

The operating model that got a company off the ground is rarely the one that carries it to altitude. 

It starts with a purpose that includes the person 

Four conditions sit underneath everything above, and they build in order. The first one looks like the easiest and is the one most teams only half finish. 

Purpose comes in three parts. The first is external. What are we doing for patients, customers and the people who depend on this working? Medtech startups almost always have this one, and it is a real advantage. The mission is genuinely moving, and it is the reason good people took the pay cut to be there. 

The second is collective. What is this leadership team, specifically, responsible for together? Many companies have a version of this written down somewhere. 

The third is personal, and it is the one that rarely comes up at all. Why is this particular person on this team, and what does being here mean for them? A VP can believe completely in the mission and still be running on empty because nobody has ever asked what they want out of the next two years. That third question is what determines discretionary energy. It is the difference between a leader who does what the role requires and a leader who brings everything they have. 

Ask: 

• Can each leader state what this team is collectively responsible for, and would the answers match? 

• Does the team put enterprise success ahead of functional success when the two conflict? 

• Has anyone asked each leader what they personally want out of the next two years? 

A shared mission tells people where the team is going. A personal purpose tells them why they are still on it. 

Trust is a track record, not a value on the wall 

The second condition is trust, and it is worth being precise about what builds it. Not offsites. Not a stated value. Trust accumulates through repeated behavior, and the behavior that counts is the kind that costs something: saying the schedule is not going to hold, admitting a call was wrong, asking for help before the problem is unrecoverable. 

Consider how this plays out in practice. An engineer notices something at week three that could affect the submission. Raising it means slowing a timeline the whole company is counting on. If this team has spent two years watching people get quietly punished for bad news, that concern surfaces at week nine instead, when it is far more expensive. Nothing in that sequence is a character flaw. It is a rational response to a track record. 

Which is where founders have unusual leverage. In a company where the same 10 people see everything, a leader who names their own mistake before anyone else has to raise it changes the calculation for everyone in the room, and the signal travels in about a day. 

Ask: 

• When someone here is struggling, do they ask for help early or hide it until it is a problem? 

• Do we assume positive intent when something goes wrong, or do we assume a motive? 

• When was the last time a leader here openly named something they got wrong? 

Psychological safety is not a policy. It is a track record. 

The debate has to happen in the room 

Trust makes the third condition possible. Healthy conflict means a team can argue about what matters without the argument becoming personal. 

The failure mode here is not shouting. It is the pleasant meeting. Everybody nods, the decision gets made, and the objections show up afterward in ones and twos where they cannot be resolved by the group. Nothing was suppressed exactly. It just never had anywhere to go. 

The fix is a rhythm the team agrees to in advance. Surface the tension while the decision is still open. Argue the problem rather than the person. Decide. Then commit as a group, including the people who argued the other way. That last step is what separates healthy conflict from a disagreement that resurfaces every third week, and it is also what gets the founder out of the referee chair. A team that can resolve the quality-versus-launch-date question on its own has just handed its CEO back several hours and one recurring headache. 

Ask: 

• In our last three hard calls, did the disagreement happen in the room? 

• Do we attack the problem or the person? 

• Once a decision is made, does the team commit or does it relitigate? 

Silence in a meeting is not alignment. It is a decision deferred to the hallway. 

Accountability has to move sideways 

The fourth condition is mutual accountability, and it only stands up on the first three. The test is simple. When a peer misses a commitment, does another peer raise it directly, or does it travel to the CEO and come back down as a correction? 

When everything routes through the founder, what a company has is supervision. It produces policing, peer avoidance, weak follow-through and more founder dependency, which is the same trap the company started in. When accountability runs between peers, the team starts owning outcomes rather than deliverables, and the outcomes that live between two functions finally have someone watching them. 

This is also the condition teams most often try to install first, usually by adding a tracker or a new meeting. It does not take. Peer accountability is only received as a gift rather than a threat when trust and healthy conflict are already there. Without them, the same behavior reads as an attack, and people respond accordingly. 

Ask: 

• When a peer misses a commitment, does another peer raise it or does it go to the CEO? 

• Do we hold each other accountable for behavior, not just for results? 

• Who owns the outcomes that sit between two functions? 

When accountability runs through one person, it is supervision. When it runs between peers, it is a team. 

The cheapest diagnostic a team will ever run 

All four conditions are measurable, which makes this easier to act on than most culture work. A team can score itself on each one using a handful of plain statements rated from zero to 10. Somewhere around seven to eight out of 10 across all four is a reasonable working bar for a team that is ready to scale. 

The score itself is not the point. The comparison is. It is common for a leader to rate a condition a 10 and for the team to rate the same condition a five, and that gap is the most useful information in the exercise. It says the leader is operating on a picture of the company that the rest of the room does not share. The conversation about why one person wrote a five is worth more than any number in the set. 

It also does not hold still. People join, people leave and every change resets the dynamics, so a single snapshot has a short shelf life. Distributed teams need the check more often rather than less, because the informal contact that normally surfaces friction in a hallway is simply not there. 

Ask: 

• Have we scored ourselves, or only asked the leader’s opinion? 

• Where is the biggest gap between how the leader sees this team and how the team sees itself? 

• Which single condition, if it improved, would unlock the most performance right now? 

A score is not the insight. The gap between the scores is. 

The common thread: the cost of waiting is paid in milestones 

The throughline here is timing. None of this comes from a lack of commitment or expertise. It comes from carrying a way of working into a stage it was never designed for, and by the time the cost lands it does not look like what caused it. 

That is what makes this easy to defer. The bill for a leadership team that has not scaled never arrives labeled as a culture problem. It arrives as a decision that took six weeks, a submission date that moved, a strong leader who burned out or a partnership window that closed while the company was still deciding. 

The teams that get through this treat it as an operating discipline rather than a soft topic. They look at themselves honestly, they name the one condition holding them back most and they work on it while the options are still open.  

For an early-stage medtech company that is one of the few investments that pays back across every function at once, because purpose, trust, conflict and accountability are not sitting off to the side of regulatory strategy, quality and commercialization. They are what decides how well all of it gets run. 

If this content resonates with you, reach out to talk through how we can help your team fly higher. 

FAQ 

What are the signs that a leadership team is limiting a company’s growth? 

Common signals include decisions that migrate upward to the founder, leaders who each name a different top priority and concerns that surface after meetings rather than during them. Milestones that slip without any single function being clearly at fault are another indicator, because it usually means ownership across functions was never explicit. 

Why do founders become decision bottlenecks as a company grows? 

The habit forms early and for good reason. In the first stage, the founder genuinely does hold the most context, so routing decisions through them is efficient. Once the company adds functional leaders, that same pattern stops being efficient and starts slowing everything down, but it persists because nobody has explicitly renegotiated who decides what. 

How can a leadership team disagree productively without damaging relationships? 

The practical mechanism is a rhythm agreed to in advance. Surface tension while the decision is still open, argue the problem rather than the person, decide and then commit as a group even when individuals argued the other way. Teams that avoid disagreement do not eliminate it. They relocate it to side conversations where it cannot be resolved. 

What does mutual accountability actually look like on a leadership team? 

It means peers raise missed commitments with each other directly instead of escalating to the CEO, and the team owns collective outcomes rather than only its functional deliverables. It also depends on trust being in place first, because the same conversation lands as support in one team and as an attack in another. 

How often should a leadership team assess how it works together? 

More than once. Composition changes as people join and leave, and each change resets the dynamics, so a single assessment captures one moment only. Distributed and remote teams generally need a more deliberate cadence, because the informal contact that normally surfaces friction is not there.