There's a meeting that lives inside almost every organization I've worked with. Different company, different industry, different people at the table... same meeting.
Three senior leaders. Same company. Same stated goal. One is pushing to ship before end of quarter to capture a market window. Another wants six more weeks to do it right. A third, quietly incentivized on cost and efficiency, sides with the first one. Not because they believe it, but because moving feels better than staying stuck. The meeting ends. Agreements are made. And six weeks later, they're having the same conversation.
Every time.
What do organizations usually do with this? They tighten the process. Add a project manager. Sharpen communication norms. Build a better RACI. These aren't bad ideas. But they are answers to the wrong question.
What looks like a coordination problem is almost never a coordination problem.
The thing nobody names
Incentive misalignment is hard to see because it doesn't introduce itself. Nobody walks into that meeting and says: I'm being measured on speed and you're being measured on quality, so we're going to disagree on every time-sensitive decision we make. They just... disagree. And because both sides are right, legitimately, defensibly right, the conflict gets attributed to personality. To communication style. To departmental territorialism. To this person and that person not getting along.
Not to the structural mismatch underneath.
There's a concept in project management most leaders know intuitively: of the three variables (time, quality, cost) you can optimize for two, but never all three simultaneously. Pick fast and cheap, and quality suffers. Pick quality and fast, and cost climbs. It's not a preference. It's physics.
When organizational incentives aren't aligned, you're asking your teams to score through two different goal posts with one ball.
They can't win. And the harder they try, the more visible the friction becomes, and the more it gets mistaken for a people problem.
Where delegation actually breaks
This is where I see trust erode fastest inside leadership teams.
A leader hands off work to a team that's structurally incentivized for something different than what the directive requires. The team tries. They're capable. But they can't actually succeed against two competing definitions of success. So they hedge. They prioritize the thing they're actually being measured on, which is rational, and the work comes back... off. Not wrong exactly, but off.
The leader, frustrated, reaches for the same lever: more oversight, tighter review cycles, another check-in. Which doesn't fix anything, because the problem isn't capability. It's not even effort. It's that the design underneath the delegation was broken before the work started.
The team feels it even when they can't name it.
And the naming... that's the thing most leadership teams skip.
What changes when you name it
The most powerful thing I've watched a leadership team do is look at their own incentive structure clearly, not to assign blame, not to launch an initiative, just to see it.
Put the OKRs on a wall. All of them. Team level, individual level. Look for tension, not just for coherence. A team with perfectly written OKRs can still be operating against a cultural incentive that quietly overrides everything: what actually gets celebrated, what gets promoted, what gets funded when resources get tight.
There's a three-level diagnostic I use with leadership teams. Culture and values versus business model. Team OKRs versus individual OKRs. Performance reviews versus actual daily priorities. Most organizations run these diagnostics independently. The gap between levels is where the real friction hides.
The moment a leadership team can see it, specifically and clearly, without turning it into a conversation about people, something shifts. The question stops being why can't we agree and starts being here's what we need to change.
That is not a small shift.
The question that should end every planning cycle
What would have changed the outcome of that opening meeting? Not better project management. Not a sharper agenda. One question:
Are we all being rewarded for the same thing here?
Most leadership teams never ask it. Not because they don't care about alignment. They do. But because naming misalignment feels like an accusation, like pointing at someone and saying the reason this isn't working is you. So we route around it. We add process. We build structure on top of a system that's pulling against itself.
The fix isn't a harder push. It's a different design.
And the design conversation can only start once someone in the room is willing to name what's actually misaligned.
Incentive alignment is a systems problem. The moment you treat it like a people problem, you've already lost the thread.