Organisational Memory

One of the things I have noticed over the years is how often seemingly simple questions turn out not to have simple answers. Ask whether a particular service can be delivered in a specific country and, more often than not, the answer starts with “it depends”. Not because people are being evasive, but because every part of the answer sits with somebody else. Legal understands one aspect, Product another and Operations a third. Finance introduces considerations that nobody else has mentioned, while someone in Customer Success remembers a client who encountered something similar several years ago. After a handful of conversations, the answer eventually becomes clear, but it is difficult not to wonder why it took five people to establish something the organisation already knew.

Questions Nobody Can Answer Alone

For a long time, I assumed this was simply the nature of working in a large business. Organisations become specialised because specialisation makes them stronger. Legal should understand legislation more deeply than Sales, Product should know more about capability than Finance, and Operations should see practical limitations that Marketing may never need to consider. Expecting one person to understand every aspect of the business would be unrealistic, so bringing together several perspectives seemed like a reasonable way of reaching the right answer.

The explanation made sense, but it never quite accounted for what I was seeing. The conversations were not simply combining different functional viewpoints. They were reconstructing decisions, customer experiences and lessons that had accumulated over many years. A regulatory requirement explained why a service was structured in a particular way. An implementation from several years earlier explained why one country worked differently from another. A product decision that had seemed relatively minor at the time now shaped what could be offered commercially. The answer existed, but it existed as fragments of organisational history rather than as a complete and current view.

How Organisations Remember

Every organisation accumulates this kind of history, whether anybody intends to preserve it or not. A customer requests a capability that has never existed before. A delivery team develops a better way of solving a recurring problem. A product matures, regulations change and a business enters another market. A local team finds a workaround that proves so effective it gradually becomes normal practice. None of these developments feels especially significant in isolation, but each leaves something behind. Over time, they create a business that knows far more than it did when it started, even when nobody can easily describe everything it has learned.

Acquisitions make this easier to recognise because they bring different organisational histories together in a visible way. A company may acquire a specialised platform in one country, a different service capability in another and a technology business whose product was originally designed for a particular market. Each acquisition brings customers, systems, expertise, contractual commitments and ways of working that made sense in its previous setting. Once these are brought into a larger organisation, the challenge is not only to integrate legal entities, technology and reporting structures. It is also to understand what has actually been acquired, where it can be used, what still limits it and which parts of the wider business know enough to sell and deliver it responsibly.

I encountered this in a European organisation that had grown through a combination of acquisitions and organic expansion. From the outside, it presented a broad and coherent portfolio. Internally, that portfolio reflected many years of development across different markets. Some services had been built within the business, while others had arrived through acquisition. Certain capabilities were well established in one country but barely known in another. A platform might be technically available across Europe while customer references, licensing arrangements or delivery expertise remained concentrated in a handful of markets. Individual legal entities reflected commercial and regulatory decisions that had been entirely reasonable when they were made, even if they were no longer obvious to somebody joining the organisation later.

Making It Visible

The practical questions were straightforward enough. Which services were deployed in which countries? Which ones could genuinely be sold? Where did customer demand already exist? Which platforms supported each offering? Where was there a referenceable customer, and where was the organisation still relying on ambition rather than delivery experience? The difficulty was not that the answers were unavailable. They sat with different people, in different functions, and were often maintained for different purposes.

I started bringing the information together in a simple matrix. Countries ran along one axis, while services, systems, customer demand, sales readiness, delivery experience and referenceability sat across the other. It was not sophisticated, but it immediately created a view of the business that had previously existed only through a sequence of conversations. Sales could see where an opportunity was realistic, where it required further investigation and where a customer request was running ahead of the organisation’s current capability. Operations could recognise buying signals, anticipate what delivery might involve and identify where apparently similar opportunities carried very different levels of risk.

The matrix became more useful as more people contributed to it. Questions that had previously triggered a chain of emails could be answered with greater confidence, while inconsistencies became visible enough to investigate. A market described as commercially ready might turn out to lack a suitable legal entity. A service believed to be unavailable might already have been delivered successfully for an existing customer. Demand that appeared local could reveal a wider pattern across several countries. The act of bringing the information together did not merely document the organisation. It helped people see relationships that had been difficult to recognise while the information remained separated.

What began as a spreadsheet eventually evolved into a repository housed in a Microsoft Power App. The technology made it easier to access, filter and maintain, but the value did not come from the application itself. It came from creating a shared view of what the organisation could do, what it wanted to do and what still stood between the two. For that view to remain useful, it had to be treated as a living resource. A new customer, product release, regulatory change or implementation could alter the picture, which meant the information required continual attention rather than a one-off exercise in documentation.

This is where many repositories begin to lose their value. The initial effort is often excellent. Information is gathered, categories are created and responsibility is assigned. The organisation then continues to evolve while the repository becomes a record of what was true at the moment it was created. Within months, users begin to encounter gaps. A few inaccurate entries are enough to weaken confidence, and once people stop trusting the information, they return to asking whoever they believe might know the answer. The organisation has built a source of truth, but has not created the habits required to keep it truthful.

The same pattern can be seen in the way organisations understand their people. Human Resources will usually maintain a reliable record of who is employed, their job title, their manager, their function and their place in the organisation chart. When somebody is recruited, a copy of their CV is stored somewhere in the recruitment system. That document may contain a reasonably rich account of the experience they had accumulated before joining, but it begins to age almost immediately.

A person recruited into a particular role rarely remains limited to the experience described in the CV they submitted. They work with new customers, enter unfamiliar markets, implement systems, manage crises and contribute to projects outside their formal responsibilities. They may learn a language, relocate to another country, help integrate an acquisition or develop expertise in an area that did not even exist when they joined. Their job title might change once or twice, but the organisation’s formal understanding of what they can do often remains tied to the role for which they were originally hired.

Years later, a project requires a particular combination of skills and experience. The organisation begins to define a role, approve a budget and search externally for someone who appears to match the requirement. A recruitment firm may be engaged and candidates assessed over several months, even though somebody inside the business has already done much of the work. The capability is not absent. It is simply difficult to discover because the person has continued to develop while the organisation’s record of them has stood still.

Organisations don't just lose information. They lose sight of capability they already possess.

What We Forget

Most people who have spent time in a large company have encountered a version of this by accident. A colleague mentions that they once led an implementation in the same country the project team is struggling to enter. Someone in Finance turns out to have worked with the technology now being evaluated by Operations. A person known for one functional role has deep industry experience from an earlier career that nobody thought to ask about. These discoveries often feel fortunate, although they reveal how much organisational capability depends on chance conversations and personal networks.

The issue is not confined to individual skills. Organisations regularly search externally for knowledge they have already created internally. Consultants are asked to investigate problems that another team solved several years earlier. A new project repeats work undertaken for a different customer because the previous experience was never connected to the current challenge. Businesses acquire capability while overlooking similar expertise elsewhere in the group. None of this necessarily reflects poor judgement. It reflects the difficulty of maintaining a current understanding of an organisation that is changing every day.

This also explains why some people appear unusually effective at navigating complex businesses. They are not always the people with the deepest technical knowledge or the most senior title. They have often developed a strong sense of where experience resides. They know which market encountered the issue before, which colleague remembers why a decision was made and which teams need to be brought into a conversation before a commitment is made. Their value lies partly in what they know, but just as much in their ability to connect knowledge that would otherwise remain separated.

That ability becomes particularly important when experienced people leave. While they remain in the organisation, the gaps in formal knowledge are easy to overlook because somebody still knows who to call. A question can be routed through personal relationships, and the missing context can be reconstructed informally. Once those people depart, the organisation discovers how much of its understanding was held in memory rather than in any system. The documents may remain, but the connections between them disappear.

It would be easy to treat this as a case for more documentation, although documentation on its own does not solve the problem. A business can accumulate thousands of presentations, reports, process maps and project files without becoming easier to understand. Information becomes useful when somebody can establish whether it is still current, how it relates to other information and whether it can be applied to the situation in front of them. A large archive may preserve the past while doing very little to support the next decision.

Keeping It Alive

The work is therefore closer to curation than storage. Curation starts by discovering what exists, but it does not stop there. Information has to be connected so that relationships become visible, maintained as circumstances change and pruned when it no longer reflects reality. Some experience should be retained because it continues to shape how the organisation operates. Some should be simplified and made easier to apply. Some should be retired because the market, technology or operating model has moved on. Preserving everything would be as unhelpful as preserving nothing.

Old cities offer a useful comparison. They are not valuable because every building or street has been left untouched. Their character comes from an accumulation of choices made over many generations, combined with continual decisions about what should be protected, adapted, replaced or removed. A road may follow a route established centuries ago because it still works. A former industrial building may find an entirely new purpose. Other structures disappear because preserving them would prevent the city from meeting current needs. The history remains visible, but it is not treated as something that must be frozen.

Organisations need a similar discipline. Their accumulated experience has value, but that does not mean every process, product or historical decision deserves to survive. The first task is to understand what is there and why it exists. Only then is it possible to distinguish useful capability from inherited complexity, or hard-earned knowledge from a practice whose original purpose has disappeared.

This changes the way organisational simplification should be approached. Simplification is often treated as a process of removing variation, consolidating systems or standardising ways of working. Those efforts may be necessary, but they can also destroy valuable capability when the reasons behind differences are not understood. Two markets may operate differently because one developed an effective response to a local regulatory constraint. Two teams may use different processes because one serves a customer segment with genuinely different needs. Standardisation can remove waste, but it can also remove knowledge when the organisation cannot distinguish between the two.

The same applies to integration after an acquisition. Financial, legal and technological integration tend to have clear owners because the work can be planned, governed and measured. The responsibility for integrating organisational understanding is less obvious. Product may catalogue features, Sales may absorb new messaging and Operations may map delivery processes, yet nobody holds a complete view of how the acquired capability fits into the wider business. The value that justified the acquisition can remain concentrated in the original team until rationalisation, turnover or competing priorities gradually weaken it.

A simple matrix cannot solve every aspect of this, nor can a Power App, a skills database or an artificial intelligence search tool. Each can make useful information easier to discover, but none removes the need for judgement. Somebody still has to decide which questions matter, which distinctions are commercially or operationally significant and how often the picture needs to be refreshed. The design of the repository matters less than whether the organisation treats understanding itself as something worth maintaining.

That maintenance does not need to begin as a large transformation programme. The matrix I created began with questions that people were already asking and struggled to answer. It gathered information that existed, connected it in a way that supported real decisions and improved as gaps became visible. Its value came from practical use. Salespeople referred to it when assessing opportunities, Operations used it to understand demand and limitations, and the organisation gradually developed a clearer view of itself.

The same approach could be applied to people. Instead of treating a CV as a static record from the moment of recruitment, organisations could maintain a living view of experience acquired after somebody joins. Projects, markets, systems, customers and problems solved would tell a richer story than title progression alone. This would not require every employee to write a new CV each year. It would require the organisation to recognise that capability changes continually and that internal mobility, succession planning and project staffing all depend on being able to see that change.

It could also be applied to customer experience. Major implementations produce lessons about technology, governance, behaviour and change that extend beyond the immediate account. Capturing those lessons is useful, but connecting them to future opportunities is what turns them into organisational value. A lesson learned in one market should not have to be rediscovered in another simply because the teams involved do not share the same reporting line or repository.

The underlying principle is consistent across all of these examples. Organisations create knowledge through work, but value only emerges when that knowledge can be found, understood and applied elsewhere. A customer implementation becomes more valuable when its lessons improve the next one. An employee’s development becomes more valuable when their experience can be matched to a new challenge. An acquisition becomes more valuable when its capabilities can be recognised and used across the wider business. The original experience creates potential, while curation allows that potential to travel.

This is why the apparently simple question at the beginning matters. When it takes five people to determine whether a service can be sold in a particular country, the immediate temptation is to see inefficiency, poor communication or inadequate documentation. Any of those may be present, but the difficulty may also point to something valuable. The organisation has accumulated more capability, experience and context than its formal structures can easily reveal.

The next step is not to preserve everything or to build another repository for its own sake. It is to decide which recurring questions reveal gaps in the organisation’s understanding of itself, then bring together enough information to answer them reliably. As that view develops, it can be maintained, challenged and refined through use. What begins as a practical response to a commercial or operational problem can become a way of uncovering strengths that had previously remained hidden.

Organisations devote enormous effort to creating new capability through recruitment, product development, technology, market expansion and acquisitions. Those investments are visible, measurable and closely managed. The capability created through years of customer work, individual development and accumulated experience is less visible, even though the organisation has already paid for it many times over.

The opportunity is not simply to record the past. It is to convert accumulated experience into something the organisation can continue to use. That requires curiosity about what already exists, discipline in keeping it current and judgement about what still deserves a place in the future. Once an organisation begins to curate its knowledge in that way, it becomes better able to recognise its own buying signals, deploy its people intelligently, protect valuable experience and simplify without discarding the reasons it became capable in the first place.

We spend a great deal of time discussing how organisations create value. We spend far less examining how much value they already contain but can no longer easily see. The difference between the two may lie in something as simple as gathering the right information, connecting it to the decisions people are trying to make and continuing to update the picture as the organisation evolves.

Contact

Reach out for tailored support across services procurement, external workforce strategies, workflow optimisation and SaaS evaluation.

© 2026. All rights reserved.