Why Your Team Has Slowed Down (And It's Probably Not What You Think)
You had momentum. Decisions got made. Things shipped. People knew what to do and did it.
Then somewhere along the way, everything got slower. Meetings got longer. Projects stalled. You started hearing "we're waiting on alignment" more than you'd like. You pushed harder on process, added more check-ins and maybe reshuffled a few priorities.
And yet, still slow.
If this sounds familiar, you're not alone. It's one of the most common things CEOs come to me with. And the frustrating truth is: the thing slowing your team down is almost never the thing you think it is.
The Usual Suspects (That Usually Aren't the Problem)
When execution slows, most leaders go looking in the obvious places:
- Process. We need a better project management system. More structure. Clearer workflows.
- People. Someone isn't performing. The wrong person is in the wrong seat.
- Priorities. We're trying to do too many things at once.
These are reasonable hypotheses. And sometimes they're partially right. But in most of the organizations I work with, fixing these things produces modest improvement at best - and the slowness comes back.
That's because they're treating symptoms, not the source.
The Real Bottleneck Nobody Talks About
Not because they're bad at their jobs. Because the daily operating reality of your organization makes it genuinely unclear.
When priorities get communicated at the top but interpreted differently by the time they reach the people doing the work, you get misalignment. When it's unclear who actually has the authority to make a call, decisions stall. When "good enough" means something different to your VP of Engineering than it does to your VP of Sales, you get rework, friction and delay.
None of this shows up on an org chart. None of it gets flagged in a project management tool. It lives in the invisible day-to-day operating culture of your organization: the unwritten rules about how decisions really get made, what "done" really means and whose voice actually moves things forward.
This is a culture problem. And culture problems disguise themselves as execution problems almost every time.
How You Know It's Culture (Not Process or People)
A few signs that culture is the real culprit:
- Your high performers are slowing down too. If it were a people problem, your best people would still be moving fast. When even your A-players are stuck in the mud, the system is the issue.
- The same problems keep coming back. You fix something, and six months later it's broken again. That's a sign the underlying conditions that created the problem haven't changed.
- Decisions keep escalating to you. If your team can't move without your sign-off on things that shouldn't need your sign-off, it's not because they're incapable. It's because something in the culture has made autonomy feel risky.
- People seem busy but outcomes are thin. Lots of activity, not enough results. When effort and output are misaligned, people are working hard on the wrong things - usually because what "right" looks like isn't clear enough.
What to Do About It
The good news: this is fixable. And it doesn't require a massive reorganization or a culture overhaul initiative that takes two years.
It starts with getting honest about the gap between what you think is clear at the top and what's actually landing across the organization.
In my work with executive teams, I often find that leaders are surprised by how differently their teams understand the company's priorities, decision-making authority and definition of success. Not wildly differently - but differently enough to create drag at every level.
Closing that gap is the work. And when you do it, teams start moving again - not because you pushed harder, but because the friction is gone.
Start Here
If you're a CEO wondering whether this might be what's happening in your organization, the first step is just to look.
We built a simple tool for exactly this: the Culture Counts Alignment Check. It takes about 10 minutes and gives you a clear picture of where alignment is strong and where the invisible bottlenecks are hiding.
Run the Alignment Check →