The Missing Enterprise Capability Nobody Is Building

A company solves a difficult problem. People spend months understanding it, finding the root cause, redesigning the process, fixing the data, changing the system and documenting what happened. Eventually, the problem is solved and everyone moves on. Two years later, somewhere else in the same organization, remarkably similar conversations begin again. Different people, different market, different project name, same problem.

Nothing failed. The first team did exactly what it was supposed to do, the documentation still exists and the change was successfully implemented. Yet what happened did not make the organization better prepared for the next time. The problem was solved; the organization did not become better because of solving it.

This is an odd thing about modern companies. We have spent decades building specialized capabilities for almost everything: Strategy, Finance, Risk, Data, Governance, Transformation and, more recently, AI. Each a distinct discipline, many of them sophisticated in their own right. Yet it remains surprisingly difficult to say who makes sure that something learned in one part of the company changes what another part knows, that critical knowledge survives the person who carries it, or that signals scattered across functions are connected before they become a problem.

Documentation preserves what happened. Knowledge Management makes knowledge easier to find and reuse. Change Management helps people adopt and sustain change. All of those matter. But an organization can document a lesson perfectly and still repeat it elsewhere. It can preserve knowledge without that knowledge ever changing a future decision. Capturing what was learned and becoming better because of it are not the same thing.

Which leads to a more fundamental question: who is responsible for making sure the organization itself becomes better because of what it knows and what it experiences? There is rarely an obvious box for that on the org chart, and perhaps there shouldn’t be. Creating another function, another team or another framework may be precisely the wrong response.

The capability lives in the connections between things we have become very good at managing separately. It is what determines whether experience in one part of the organization changes what another part can understand or do; whether knowledge survives people, projects and organizational boundaries; whether scattered signals become visible before they become crises; whether solving a problem today makes solving the same problem tomorrow less likely. None of those outcomes belongs naturally to a single function. Yet together, they determine whether an organization merely accumulates experience, or actually becomes better because of it.

Companies already have most of the ingredients: the technology, the data, the expertise, the processes and the people who know. What many are still missing is the enterprise capability that allows all of those things to become more than the sum of their parts.

And perhaps the most interesting question is not who should own it.

It is why, after decades of building increasingly sophisticated organizations, we assumed it would emerge on its own.