Why our teams keep having the same conversation — and why it's not their fault.
We've all seen this meeting before.
A decision gets made, everyone nods, the energy is good. People walk out with clear next steps. And then, over the following weeks, three different versions of that decision show up across the organization. The systems those people walked back into — how priorities get set, how resources get allocated, how success gets measured — sent three different signals about what that decision actually meant.
So the team compensates. They work harder, fill the gaps with judgment calls and hallway conversations and late-night emails that shouldn't be necessary. They pull it off, because they're good at what they do. A month later, the same tension surfaces again. Different topic, same pattern.
If we've watched this cycle repeat and wondered what we're missing, it's probably not our people. It's probably our wiring.
When teams feel stuck, the instinct is to look at the people. Are they communicating well enough? Do they trust each other? Are the right people in the right roles?
Fair questions, but often the wrong ones.
In most senior teams, the people are already doing something remarkable: they're holding the system together through sheer effort and good intent. The friction they feel isn't coming from each other. It's coming from the space between the systems they operate in.
Every team has a way it makes decisions, sets strategy, defines priorities, and rewards performance. When those systems are wired together coherently, the team flows. Decisions translate into priorities. Priorities shape execution. Execution gets recognized. It's not effortless, but energy moves forward.
When strategy says "innovate" but process says "standardize," when decision-making is collaborative but rewards are individual, when priorities shift quarterly but structure stays fixed — the team absorbs the contradiction. They find workarounds. They use relationships to bridge what the system doesn't connect.
That's connective tissue doing its job. And when it frays, the people inside feel it long before anyone can point to it on an org chart.
Strategy says one thing, process enforces another. The leadership team sets an ambitious new direction. Meanwhile, the approval workflows, resource allocation models, and operating rhythms haven't changed. The people in the middle aren't resisting the strategy — they're trying to execute it inside a machine that was built for the old one. Both the strategy and the process seem reasonable on their own. It's the relationship between them that's broken.
Decisions are collaborative, rewards are individual. The team is told to think collectively — shared goals, cross-functional priorities, one team. Compensation, recognition, and career progression still track to individual contribution. So people learn to perform collaboration while optimizing individually. The system is asking them to hold two contradictory truths at once, and they're doing the rational thing within it.
The org chart says "empowered," the calendar says "controlled." Leaders are told they have autonomy. They're also in four standing meetings a week, submitting updates in three formats, and getting sign-off from two levels above for decisions that should be theirs. The people setting those requirements aren't trying to micromanage — they're managing risk in a system that doesn't have another way to create visibility. The people below carry the weight of that gap every day.
In each case, the same thing is true: good people, doing their best, inside a system that is quietly working against them.
We can't see this by looking at any single part of the system. Strategy looks fine in isolation. Processes are defensible on their own terms. Rewards follow an internal logic. Each piece is reasonable.
The problem only becomes visible when we look at how they interact. And that's nearly impossible from inside the system, because the people inside it are busy doing what good teams do — adapting, compensating, making it work. Their competence masks the dysfunction. The better the team, the longer the system runs on their effort before the strain shows.
This is why the same conversation keeps happening. The team hasn't failed to solve the problem. The problem doesn't live where they're looking.
When we see this clearly, something changes. It stops being a story about people falling short and becomes a story about a system that isn't serving the people inside it.
For any of us who've watched a talented, committed team hit the same walls — that's a different conversation entirely. There's nothing wrong with our people. They've been holding together a system whose connective tissue has frayed, through will and judgment and care. The question isn't how to get more out of them. It's how to make the system worthy of the effort they're already giving.
The wiring was right at some point. It was built for a strategy, a market, a team composition that made sense then. The situation shifted. The wiring didn't. And the people inside kept compensating, because that's what good teams do.
They deserve a system that doesn't ask them to.