The Enterprise Cognition Problem

Sit in enough executive operating reviews and a pattern emerges. The same data set produces five different reads. The CFO sees a cost efficiency problem. The Chief Operating Officer sees a capacity constraint. The Chief Technology Officer sees a technical debt issue that nobody wants to fund. The Chief People Officer sees a talent and change readiness gap. And the CEO, pulling signals from all of them plus the board, is somewhere in between — leaning toward whichever argument was made most recently, or most forcefully.

Nobody is wrong, exactly. They are each reading the signals available to them through the lens of their function, their experience, and their current pressures. The problem is that an enterprise can't execute effectively when its most senior leaders are operating from fundamentally different interpretations of reality.

This is what I've come to call the enterprise cognition problem — and in my experience, it is the most underdiagnosed source of organizational underperformance.

What enterprise cognition actually means

John Boyd's OODA Loop — Observe, Orient, Decide, Act — is most often described as a decision-making framework. But Boyd's real insight was about Orientation: the step that determines how incoming information gets interpreted before any decision is made. Orientation isn't just what you see. It's the accumulated weight of your experience, your assumptions, and your mental models applied to what you see. Two people looking at the same situation can observe identical facts and orient toward completely different conclusions.

Boyd was writing about individual pilots in aerial combat. The same dynamic, at far greater organizational cost, plays out in executive teams every day.

Enterprise cognition is the collective version of this problem. It refers to how an organization — as a system — perceives its own situation, interprets signals, and forms a shared understanding that drives decisions and action. When enterprise cognition is strong, leadership teams read situations similarly, calibrate quickly when they don't, and close the gap between what they intend to do and what the organization actually does. When it breaks down, organizations move slowly, execute inconsistently, and relitigate decisions that were supposedly made months ago.

How it breaks down in practice

The breakdown rarely looks dramatic. It doesn't announce itself. What it looks like from the inside is a series of ordinary frustrations: a strategic priority that never quite gets traction, a cross-functional initiative that keeps stalling at handoffs, a leadership offsite where everyone leaves aligned and nothing changes in the following quarter.

The McKinsey 7S framework — Strategy, Structure, Systems, Style, Staff, Skills, Shared Values — is often used to diagnose organizational misalignment. It's a useful tool, but it tends to focus on what the organization has and how those elements fit together. It says less about how the organization thinks: what signals its leaders are tracking, which interpretations of those signals are treated as authoritative, and where perception gaps between functions are quietly undermining decisions that look made on paper.

Three patterns show up most often when enterprise cognition breaks down:

1. Signal fragmentation

In large organizations, data is abundant but interpretation is siloed. Each function has its own metrics, its own dashboards, and its own definitions of what good looks like. A technology organization tracking deployment frequency and change failure rates is reading a fundamentally different story about enterprise health than a finance organization tracking budget variance and headcount ratios. Neither is wrong. But when those signals are never synthesized into a shared picture, the leadership team ends up in the same room having very different conversations about the same underlying reality.

2. Priority drift

When senior leaders don't share a common interpretation of the organization's situation, they default to optimizing for their own functional priorities — which is rational behavior given what they can see and what they are accountable for. Over time, the enterprise's stated priorities and its actual resource allocation diverge. The strategic plan says one thing. The budget says something slightly different. The portfolio of active initiatives says something different still. Nobody made a decision to drift. It happened because cognition was never truly shared.

3. Decision fatigue at the top

Executives in organizations with weak enterprise cognition spend a disproportionate amount of time relitigating decisions that shouldn't need to be relitigated. Every initiative becomes a negotiation. Every cross-functional dependency becomes an escalation. The cost is measured not just in time, but in the organizational energy that gets consumed before any value-creating work actually happens.

This is not a communication problem

The instinct, when this pattern gets named, is to reach for a communication solution — more town halls, better cascade messaging, a refreshed set of company priorities plastered on a conference room wall. That instinct almost always misses the actual problem.

Communication addresses what people are told. Enterprise cognition is about what people actually believe based on everything they are observing — what gets funded, who gets promoted, which initiatives survive and which ones get quietly defunded, how leaders behave when they think nobody is watching. Organizations communicate constantly through their operating decisions, their governance rhythms, and their resource allocation. When those signals are inconsistent with the stated strategy, the operating signals win. They always do.

Building strong enterprise cognition requires something more deliberate: creating the conditions under which senior leaders develop genuinely shared mental models of the organization's situation, not just shared language about it.

What it takes to get it right

In practice, this comes down to three things that most governance frameworks underinvest in:

A shared signal architecture

Leadership teams need to be working from the same integrated picture of organizational performance — not functional scorecards presented sequentially in a leadership review, but a synthesized view that deliberately cuts across the boundaries where perception gaps tend to form. This isn't about having more data. It's about having fewer, better-curated signals that the whole team is accountable for interpreting together.

Structured interpretation, not just reporting

The operating rhythm of most leadership teams is built around reporting: what happened, what's the status, what are the risks. What it rarely creates space for is genuine interpretation: what does this mean, are we reading this the same way, what would have to be true for us to be wrong? That kind of structured sense-making — done regularly, not just at annual planning — is where shared cognition actually gets built.

Honest accounting of where alignment breaks down

Most leadership teams will tell you they are aligned on the strategy. The more revealing question is where they are not — which trade-offs remain genuinely unresolved, which functional priorities are in tension, which assumptions are held by some leaders and not others. Organizations that build the discipline to surface and work through those tensions explicitly are far more effective than those that paper over them with consensus language and hope the execution sorts itself out.

---

Enterprise effectiveness is not primarily an organizational design challenge. Structure, governance, and process all matter — but they are downstream of something more fundamental: whether the people leading the organization are actually seeing the same thing when they look at it.

The organizations that execute most reliably are not the ones with the most sophisticated frameworks. They are the ones where senior leaders have done the harder work of building a genuinely shared understanding of where the enterprise is, what it is trying to do, and what stands in the way. Everything else follows from that.