Coordinated Dysfunction

There's a meeting that happens in most organizations approximately once a quarter.

Sales is in the room. Finance is in the room. Sometimes Operations. Sometimes the CEO. The agenda varies but the conversation doesn't. Revenue is up but margin is flat. Or margin improved but the pipeline is thin. Or the quarter was fine but the forecast is uncertain. Somewhere in the room, someone has a slide that shows the gap between what was expected and what happened. And somewhere in the conversation, the same unresolved tension surfaces: sales wants to close deals, finance wants to protect margin, and both of them are right.

The meeting ends. Actions are assigned. The same conversation happens again next quarter.

If you've been in that meeting — or a version of it involving any two functions that seem structurally incapable of agreeing — this piece is about why it keeps happening. Not because the people are difficult. Not because the data is unclear. Because the environments those two functions live in were never designed to point toward the same outcome.

The Mechanism Nobody Names.

Most organizations diagnose this as a communication problem, a culture problem, or a leadership problem. The functions aren't talking to each other. The leaders aren't aligned. The incentives are off.

That last one is closest. But it still misses the actual mechanism.

The problem isn't that your incentives are off. It's that your incentives are working exactly as designed — for each function individually. Sales is doing what the commission structure rewards. Finance is doing what the board measures. HR is doing what the budget cycle incentivizes. Operations is doing what the delivery SLA requires.

Every team is optimizing rationally. Every team is doing the right thing for the environment they live in. The dysfunction isn't coming from any individual failure. It's emerging from the interaction of multiple locally-correct behaviors inside a system that was never designed to make those behaviors globally coherent.

This is not misalignment. This is coordination — just not toward the same outcome.

Call it what it is: Coordinated Dysfunction.

Not chaos. Chaos would be easier to diagnose. Not laziness or bad faith. Not a failure of communication or culture or leadership, though all of those may appear as symptoms. Coordinated Dysfunction is what happens when multiple well-functioning local optimization systems operate inside a larger system that was never designed to align them.

Every team is moving efficiently. Every team is moving rationally. They're just not moving toward the same thing.

What It Actually Looks Like.

The Sales and Finance example is the most visible because the tension is measurable. But Coordinated Dysfunction shows up everywhere an organization has functions optimizing for different objectives without a shared environment that makes those objectives coherent.

Sales and Finance. Sales closes the deals that commission rewards. Some of those deals are margin-accretive. Some aren't. The commission structure doesn't distinguish — or doesn't distinguish clearly enough to change behavior. Finance sees the margin erosion and tightens controls. Sales sees the controls as obstacles to hitting targets. Both are right. Neither is the problem. The incentive architecture is the problem.

Strategy and Operations. Strategy sets direction toward new markets, new capabilities, new business models. Operations optimizes for efficiency, repeatability, and the stability of what's already working. Both are necessary. But when a new strategic initiative lands in an operational environment that was never redesigned to support it, Operations doesn't obstruct it out of spite. It optimizes around it — because that's what an efficiency environment does with interruptions. The initiative stalls. Everyone is puzzled. Nobody was wrong.

HR and Innovation. HR manages headcount against a budget that was set before the strategy changed. The budget reflects last year's priorities, encoded in a planning cycle that runs months behind the market. A new capability the organization needs doesn't exist as a budget line. A role that the strategy requires hasn't been approved because approving it would require revisiting assumptions nobody has time to revisit. Innovation waits. Quietly. Until it stops waiting and leaves.

Why Every Restructure Fails to Fix It.

The instinct when Coordinated Dysfunction becomes visible is to restructure. Move the reporting lines. Create cross-functional teams. Hire a Chief of Staff or a COO whose job is to sit in the gap. Put sales and finance under the same leader so they're forced to align.

These interventions aren't wrong. But they are downstream of the actual problem.

Because the dysfunction isn't in the org chart. It's in the incentive structures that sit underneath the org chart — the ones that determine what each function optimizes for when their career, their compensation, and their budget are on the line. Move the boxes without touching those structures and the dysfunction doesn't disappear. It migrates. It finds new expression in the new structure. The same conflict resurfaces under new names, with different people, in different meeting rooms.

This is why the quarterly meeting that never resolves keeps not resolving. Not because the people in it aren't capable. Because the environment surrounding that meeting is still selecting for the same locally-optimal behaviors that produced the tension in the first place.

You didn't fix the environment. You rearranged the boxes. The environment kept running.

The reorg bought time. Sometimes a year. Sometimes two. But the conditions that produced the dysfunction are still active — and conditions are patient. They'll reproduce the same outcome as soon as the new structure settles.

Why AI Makes This Undeniable.

For most of organizational history, Coordinated Dysfunction was survivable. Slow information, manual processes, and human-speed execution meant the costs of misalignment accumulated gradually. The quarterly meeting was frustrating but manageable. The strategic initiative that stalled could be reframed as a learning exercise. The margin erosion from the wrong deals could be absorbed into the noise of a good enough quarter.

AI changes this — not by creating Coordinated Dysfunction, but by exposing it and then accelerating it.

When you give each function an AI tool that optimizes for its local objective, the misalignment between functions becomes visible in real time. The Sales AI closes more low-margin deals faster. The Finance AI flags the margin erosion immediately. The gap that used to play out over a quarter now surfaces in a week. The dysfunction that was survivable at human speed becomes undeniable at machine speed.

But here's the part that matters more: the organization that responds by adding better AI tools to each misaligned function doesn't solve the problem. It accelerates it. You're not fixing the coordination failure — you're giving each locally-optimizing function a faster engine. Coordinated Dysfunction at scale. The quarterly meeting that never resolves now happens weekly, with better dashboards and the same unresolved tension.

This is the asymmetry that makes the next eighteen months consequential in a way that most organizations are not treating as consequential. The gap between organizations that have designed their environments and organizations that haven't has always existed. AI is making it visible. And it's making it permanent faster than any previous technology transition.

The organization running Coordinated Dysfunction through AI tools is moving efficiently in the wrong directions simultaneously. The organization that fixed the environment first is moving efficiently in the same direction from every function at once.

That gap doesn't close by adding more tools. It closes by designing the environment.

The Question Worth Asking.

Coordinated Dysfunction is not a diagnosis that requires a consultant to deliver. It's visible in the meetings that never resolve. In the initiatives that stall without a clear cause. In the AI implementations that reproduce the existing friction at higher speed. In the talent that leaves not because of one bad manager but because the environment was structurally incapable of letting them do what they were hired to do.

The question isn't whether Coordinated Dysfunction is running in your organization. For most organizations above a certain size and age, it is. The question is whether anyone has framed it as a design problem — and whether anyone has the mandate to treat it as one.

Because it is a design problem. The dysfunction isn't coming from bad people or bad strategy or bad technology. It's coming from an environment that was never designed to make the right behavior for each function identical to the right behavior for the whole system.

That's a specific, solvable problem. It requires looking honestly at what each function's environment is actually selecting for — not what you intend it to select for, but what it does select for given how people respond to incentives when their career is on the line. It requires asking whether the signals that determine what each team optimizes for are pointing toward the same outcome at the system level.

And it requires accepting that no amount of restructuring, no amount of AI tooling, and no amount of cross-functional collaboration theater will close the gap until the underlying incentive architecture is deliberately designed.

The next piece in this series is about the design error that sits upstream of every failed AI implementation — and why the question most organizations ask before deploying a new tool is the wrong question entirely.

— Raf Alencar