The Organizational Intelligence Gap

The Distance Between Direction and Delivery

There’s a gap that has shown up in nearly every organization I’ve worked in, regardless of sector. Let’s call it an operational delta. On one side are leaders who scan the horizon and set priorities. On the other side are the operators who are deeply embedded in programs, and day-to-day execution.

The delta becomes pronounced when leaders (charged with translating the priorities) work to turn ideas into solutions. A working group might form with the best of intentions. There’s plenty of positive energy. Unfortunately, an echo chamber forms.

Distributed by Design

Universities are structurally complex ecosystems. Work is distributed across departments, centers, and institutes. The connective tissue between them can be thin. An idea planted at the leadership level can take root in three different places simultaneously, with each branch unaware of the others.

What happens next? If projects progress without intervention, staff feel overlooked, leaders feel a little upstaged, and foundational work is duplicated. We’re all left wondering, how do we cross the delta?

When faced with a challenge like this one, I knew the visceral thought “communicate more” was way too simple. Even if there were more town halls, more emails, more announcements…issues would remain. If the fix were that simple, everyone would be doing it. I revisited the analogy of connective tissue, and how it can be cultivated.

What Closing the Delta Actually Requires

A few cultivation mechanisms I’ve been sitting with:

1. Index before you build. Before any new initiative is formally proposed, there should be a standard discovery phase: a scan of existing programs, pilots, and informal efforts related to the problem area. "What currently exists on campus in this space?” Making discovery a stepping stone changes behavior.

2. Develop input channels that don't require a meeting. Some cannot show up to a town hall. Not everyone feels safe raising their hand in a room with a leader at the front. Deploy a standing Google Group, a rotating anonymous feedback form, a brief biannual survey sent to program coordinators. Give people a way to surface what they know without the social risk. Once a repository has been created, leadership has to acknowledge what comes through, or the channel dies from cynicism.

3. A living program inventory. I’ve mentioned this tool in the alumni engagement context. Institutions that maintain a shared, searchable record of active initiatives, pilot programs, and sunset efforts are far less likely to duplicate work. It doesn't need to be elaborate. Even a shared spreadsheet with owner names and brief descriptions is infinitely better than nothing. Someone has to own it, and that someone needs protected time to keep it current.

4. Leaders who re-enter the room. The most underrated move a senior leader can make is periodic, intentional re-engagement with the operational layer. The focus? Listening. A twice-annual 60-minute conversation with frontline program staff, with no agenda other than "What are you seeing that we should know about?” It signals that proximity to the work still matters at the top.

5. Internal RFPs. Leaders articulate a strategic priority and invite units already working in that space to propose expansions. The RFP can't be performative. If leadership has already decided who will lead the work, or if the process is designed to favor a predetermined outcome, staff will see through it immediately. There must be transparency regarding evaluation criteria and timelines to get responses.

Collective Responsibility Is Not a Design

These five mechanisms share something important: each one requires someone to initiate and manage the process. In most institutions, that someone doesn't formally exist.

We tend to treat organizational intelligence as a collective responsibility. We believe this is everyone's job in theory, and therefore, it's no one's job in practice. The mechanisms I've described above don't fail because institutions lack good intentions or capable people. They fail because they require sustained, protected attention that never gets formally owned. When budget cycles tighten or leadership transitions happen, the first things to disappear are the informal connective efforts that were never on anyone's job description. "Other duties as assigned," am I right?

Institutions need designated ownership. There should be someone whose explicit mandate includes maintaining visibility across the operational layer. In some organizations this lives in a Chief of Staff role. In others it belongs to a strategy office, or a planning function. This work could also belong to a senior engagement leader who sits close enough to a Dean or Provost to translate institutional priorities downward, and close enough to program staff to translate operational intelligence upward. The title matters less than the clarity of the mandate: someone is responsible for maintaining visibility across active initiatives, and for making sure that intelligence reaches the people who need it before they build something that already exists.

We need to make implicit work explicit. The connective tissue doesn't grow on its own. It has to be someone's job to cultivate it. Until institutions treat organizational intelligence as a function rather than a virtue, the delta will keep producing the same outcomes: duplicated effort, frustrated staff, and leaders who are genuinely surprised to learn what was already underway.

A Confession

I'll be transparent about something: I don't call myself an operations expert. I’m cautious about that label. I've spent more time in strategy and relationship-building, and less and less time in day-to-day program delivery. This means I’m growing closer to the problem. 😅

I do not write this from a position of having solved the problem. I write from a position of having watched it cost institutions credibility, time, and money. I feel compelled to ask why we keep paying that price.

Make the Implicit Work Explicit

The mechanisms in this piece are starting points. Some institutions will find one or two that fit; others will need to build something more comprehensive. What I invite you to sit with is not which mechanism to try first, but another question. Does your institution have someone whose explicit job it is to maintain organizational intelligence? I’m not talking about someone who does it when they have time. I’m not talking about a committee that convenes when a crisis surfaces. Organizations require someone with protected bandwidth and enough proximity to both leadership and the operational layer to actually close the loop.

If the answer is yes, I'd like to know how that function is structured and what it's taught you. If the answer is no, I’d like to know who is doing it informally right now, at what personal cost, and what happens to that invisible labor when they leave?

Good intentions, however widely distributed, are not a substitute for design. We have to make sure the people setting direction, and the people doing the work, can actually see each other across the delta.