Signs your leadership team isn't pulling weight — and what's actually going on

You're a CEO running a 200–800 person company. You've started having the thought that you've been pushing away for a couple of months: my leadership team isn't pulling weight. You don't want it to be true. You hired most of them. Some of them are people you would still hire today. But something has gone off, and you can't quite name it. This is the diagnostic.

The hardest version of this for any CEO is figuring out whether the read is you or them. Almost every founder who's having this thought has had it before, and at least half of the previous times it turned out to be about the system, not the people. Which is why the diagnostic question is not "are they pulling weight" — that's a binary that pushes you toward a personnel answer too fast. The right question is "what specific patterns am I seeing, and what do they usually mean?"

Here are the eight patterns. Each one means something specific. Most of them are not what the CEO initially thinks they mean.

Pattern 1 · Decisions escalate up to you that shouldn't

The most common pattern, and usually the first one a CEO notices. Your VPs bring tradeoffs to you that you would expect them to call themselves. Customer commitments. Hires. Architectural choices. Pricing nuances.

What it usually means: Decision rights are unclear. Strategic context is missing. Or you have, somewhere along the way, signaled that calls made without you get audited publicly. (See What to do when your leadership team brings you problems not solutions for the full diagnostic.) Almost never means a motivation problem.

What to fix: Decision rights doc. Strategy in writing. 30-day audit of your own meeting signals.

Pattern 2 · Decisions route laterally instead of getting made

Less obvious, often missed. Your VP of Sales asks the VP of Product for sign-off on something that's clearly a sales call. Your VP of Marketing waits on the VP of Sales for input on a campaign that's marketing's job to run. Decisions aren't escalating up — they're moving sideways, looking for cover.

What it usually means: Each VP is uncertain enough about scope that they want a peer in the room when the call gets made. Often a sign that the team operates as a single decision-making body, not as a set of functional leaders. Sometimes a sign that one VP is operating outside their lane and others have learned to defer rather than push back.

What to fix: Name the function ownership clearly in the leadership meeting. "This is a Sales call. Sales owns it." And let the VP make the call without lateral sign-off. Watch what happens. The pattern usually shifts in three weeks if the underlying ownership is named explicitly.

Pattern 3 · The language gets hedged

You stop hearing "we'll ship that by the end of the month" and start hearing "we're targeting end of month." Or "we're aiming to land that one." Or "we'll do our best to get that out." Hedged verbs creep in across the leadership team.

What it usually means: Either commitment to a goal that was set without the team's real buy-in (so they're protecting their downside), or fatigue with goals that have shifted before, or a quiet read by the leadership team that they are no longer being held to commitments.

What to fix: In the next leadership meeting, name the hedge. "I'm noticing the language has gotten softer in the last few weeks. I'd rather you say no to a target than agree to one with a verb hedge. What's actually deliverable here?" Force the explicit recommit or the explicit no. Hedged verbs without consequence is the most reliable lead indicator of a leadership team that's stopped owning the outcomes.

Pattern 4 · The time-zone of decisions slips

A decision that used to take a day takes a week. A decision that used to take a week takes a month. The actual content of the decisions is the same; the cycle time is creeping.

What it usually means: The leadership team has accumulated a backlog of "we need to talk about this in the next leadership meeting" items, and the meeting is the only forum where calls get made. The flow has collapsed into a weekly batch process. This is rarely about effort. It's almost always about the operating cadence having gotten clogged with the wrong kind of work.

What to fix: Rebalance what goes in the leadership meeting versus what gets made in function. "This is a Sales-and-Marketing thing — you two get on a 30-minute call this week and bring back the decision." Make decisions outside the leadership meeting the norm. Use the leadership meeting for the small set of cross-functional or strategic items that genuinely need the whole room.

Pattern 5 · Artifacts that used to exist stop showing up

The quarterly business review used to have a single-page summary. Now it has 40 slides. The roadmap used to have a one-page version with three priorities. Now it has a sprint-by-sprint table you can't read in under twenty minutes. The QBR-prep doc used to come in a week before the QBR. Now it shows up the morning of, or doesn't show up at all.

What it usually means: The discipline of producing tight, top-down summaries — which is what a senior leader does for the CEO and the board — has eroded. Usually a sign that the team has lost track of who the artifact is for. Sometimes a sign that the underlying work is bad enough that the team is consciously or unconsciously hiding it in volume.

What to fix: Specify the artifact form. "I want a one-page version with three priorities for the year, and the tradeoffs you'd make for each." Make tight summarization an explicit deliverable, not an inferred one. The discipline of one-pagers is one of the highest-leverage cultural decisions a CEO can re-impose, and it shows up immediately.

Pattern 6 · Calendar drift

The 1:1s that used to be weekly are now bi-weekly. The leadership meeting that used to be 60 minutes is now 90, but no more decisions are getting made. The standing review that the VP runs with their function is being canceled twice a month. The off-site is being pushed.

What it usually means: Either the meetings have stopped having clear purpose (so they get optional in everyone's heads), or there's so much fire-drill work that the standing cadence has lost priority. Both are operating-model failures, not motivation failures.

What to fix: Name the cadence as non-negotiable, or change it deliberately. "The leadership meeting is 60 minutes, decisions only. We're not going to use it for status. If we need a status meeting, we'll have one separately." Cancel the meetings that have stopped serving their purpose. Hold the ones that haven't.

Pattern 7 · Peer disagreement disappears

The VP of Sales and the VP of Product used to push back on each other in meetings. Now they don't. Everyone says yes to everything in the room, and the disagreement happens in DMs to you afterward.

What it usually means: Almost always the most concerning of the eight. Public agreement plus private disagreement is the signal of a leadership team that has stopped holding each other accountable in real time and started routing everything through the CEO as referee. Sometimes it's the result of a single bad incident where peer pushback got punished. Sometimes it's that the team has learned that you'll resolve it if they bring it to you.

What to fix: Push the disagreement back into the room. "I want to hear this one in the leadership meeting, not in my DMs. Bring it up on Monday." It will be uncomfortable the first two times. By the fourth time, the operating norm has shifted. If the disagreement stays in DMs after explicit redirection, you have a more specific people problem to address.

Pattern 8 · Your own week is the smoking gun

This is the hardest one for a CEO to see, because it requires looking at your own week as data about the leadership team.

If your week looks like:

• Multiple deals you're closing personally.
• Hiring loops you're in the middle of for functional roles.
• Customer escalations that you're owning end-to-end.
• Internal arbitration calls between functions.
• The same questions from the same VPs week to week.

…then the leadership team is not pulling weight, and the proof is what is on your calendar. This is the most reliable single diagnostic. Your week is what your leadership team is delegating to you. When the delegation is healthy, your week is hard problems no one else can resolve. When the delegation is broken, your week is calls anyone else in the room could make.

What to fix: Pull the last four weeks of your calendar. For each calendar block longer than 30 minutes, write next to it: who else could have done this? Be honest. The number of "anyone on the leadership team could have done this" blocks is your real diagnostic. The fix is then to push that work to the right owner, with the system changes from Patterns 1–7 to make it stick.

What the diagnostic does NOT mean

A leadership team showing several of these patterns does not mean the team is bad. The most common case — by a lot — is a team that was hired correctly, has the capacity, and is operating inside a system that is sending the wrong signals.

The frame to hold: most of these patterns are downstream of system gaps, not character gaps. The system gaps are fixable in 60 days. The character gaps are real but rare, and you should be slow to conclude that's the issue.

A team that's showing five or six of these patterns simultaneously, after you've fixed the system in writing — decision rights doc, strategy in writing, calendar discipline, operating-cadence redesign, your own micro-signals — is a different conversation. That's when the per-VP performance conversations become real, with the rigor described in How to have a hard performance conversation with a VP.

What to do this week

Pick three of the eight patterns that resonate hardest. For each one, write down the two or three most recent concrete instances. Don't show this to anyone — it's your read, not the team's. Bring it to your next 1:1 with each VP separately, or to the leadership team meeting if the pattern is consistent across people.

The conversation that follows is structured: see What to do when your leadership team brings you problems not solutions for the team-level version, or How to have a hard performance conversation with a VP for the 1:1 version.

The single biggest mistake CEOs make at this stage is treating these patterns as a feel rather than as data. If you can write the instances down with dates, you have a real picture. If you can't, you're not yet ready for the conversation — keep watching for another two weeks.

How Ren makes this easier

The eight patterns above are exactly the signals Ren is built to surface. Pattern 4 (cycle time on decisions), Pattern 5 (missing artifacts), Pattern 7 (DM-routed disagreement) — Ren reads the operating-model signal across Slack and Teams threads and surfaces them to the CEO weekly, not biannually like an engagement survey.

The drafts and prep stay between you and Ren — Tier 1, never visible to HR or the leadership team. Only the did the conversation happen, did the pattern shift outcomes roll up as the Tier 2 layer.

A leadership team's drift is one of the highest-cost patterns in any company. Catching it at week eight instead of month eight is the difference between a 60-day system fix and a leadership transition. Take the three-minute product tour to see it surface a pattern like this in real time, or talk with us about a deployment for your leadership team.