Our house was divided long before the final. My son follows the French talent, my daughter has a soft spot for the Scandinavian teams, my wife supports Spain because half our friends and colleagues are Spanish.

I wanted Spain to win, and not for any of those reasons.

‍

‍

I have spent twenty years working on how organisations hold on to what they know. So I was not watching a final that night. I was watching two theories of success play each other, and I badly wanted one of them to hold.

Argentina's theory is the one most of us secretly believe in: find someone extraordinary and let them decide the night. Spain's theory is slower and far less romantic. Teach the same ideas to everyone for years, at youth level and senior level, until nobody has to be told what to do.

Argentina came at them hard: physical, direct, trying to break the rhythm and force a mistake. It is a good strategy against a team that improvises.

Spain didn't improvise. What struck me was how little visible communication there was. Nobody shouting instructions, nobody reorganising anything. Everyone already knew where everyone else would be. My wife asked, around the hour mark, why nobody was doing anything spectacular. That was the point. Nobody needed to.

Remove one Spanish player and the shape held. Remove Argentina's best and the theory collapses. That difference is not luck. It is twelve years of the same knowledge being passed to the next group, and the next.

I have watched organisations lose that same match. Not on a pitch, but in a meeting room, eighteen months after someone resigned. You know the person: Tom. The one who knows why the framework was designed that way, who remembers what was agreed with the regulator in 2019 etc etc. They are not listed anywhere as critical infrastructure. They just are.

Three things worth doing before that Tuesday:

Write down why, not just what. Most decision records confirm something was approved. Almost none explain what made it sensible at the time.

Name your single points of knowledge. If this person were unavailable for three months, what stops? Most teams have never made that list.

Debrief the near-misses. They hold the most useful knowledge and the least defensiveness.

Knowledge Management is not about producing heroes. It is about building organisations that can afford to lose them.

Every organisation loses its best people eventually.

_____________________________________________________

You probably remember someone like him: Tom, the senior policy expert who spent two decades at the institution. Tom remembered which decisions had been revisited three times before reaching their final form. Tom carried in his head the assumptions behind frameworks that now looked obvious but had been genuinely contested when they were designed.

Tom is "The Organisational Memory" :)

When he retired, the organisation held a warm farewell.Three months later, his former team faced a decision that depended on understanding why a key position had been taken eight years earlier. They found the approval. The minutes. The final document.They could not find the reasoning.It had retired with him.

‍The gap existing frameworks do not close
In a previous article, I introduced Structured Decision Continuity through the story of Sophia: every senior expert whose absence only becomes visible when the system that replaced her produces an answer that looks correct and is not.

The diagnosis is this: organisations do not fail because they lack knowledge. They fail because the continuity between their knowledge and their decisions is not governed.

SDC names that gap. At the centre of SDC sits the Control Layer, a practical model that examines whether the path from knowledge to decision is strong enough to survive over time.
‍

The Four Conditions
The Control Layer has four conditions. Each addresses a failure that senior professionals recognise but few organisations name explicitly

‍Validation
Was the knowledge behind this decision reliable and valid in context?

Validation ensures that information, analysis and expertise were sufficiently checked; not just accurate in isolation, but appropriate for the specific decision being made.

The failure mode is familiar: a recommendation sound in theory but built on data that no longer reflected organisational reality. Before closing any significant decision, one question is worth asking: what are we taking for granted that we have not actually tested.

‍Context
Will someone encountering this decision in three years understand the conditions that shaped it.

Context is the set of circumstances and constraints that existed at the moment a decision was made. It is why the decision made sense then; even if it looks different now.

Context is the component most commonly lost. It lives informally in the people who were present. When those people retire or move on, the context goes with them unless it has been deliberately preserved.‍

Alignment
Was this decision coherent with strategy and governance and is that coherence still visible?

The failure mode here is subtle. A decision can be fully aligned at the moment it is made and look disconnected two years later, not because it was wrong, but because the strategy moved and no one recorded what the decision was originally aligned to.‍

Traceability
Can someone follow the path from knowledge to decision and from decision to consequence?

This is the expert's failure. The decision was defended procedurally. But the reasoning left with the person who held it. Traceability ensures that reasoning does not have to leave when the expert does.‍

Four Questions Worth Asking

For any decision that will carry long-term consequences, four questions are enough:
- Was the knowledge behind this decision sufficiently checked?
- Is the context preserved?
- Is the alignment with governance and strategy visible?
- Can the path from knowledge to decision be followed later?

If the honest answer to any of these is uncertain, something is worth capturing before the people who hold the answer have moved on.‍

A Closing Thought

The expert who retired took something with him that no record system was designed to preserve. Not his knowledge; much of that existed in documents. What left with him was the reasoning that connected that knowledge to the decisions that had shaped the institution.

The SDC Control Layer does not prevent people from leaving. It ensures that when they do, the reasoning behind their most important decisions does not leave with them.

Structured Decision Continuity is a developing professional concept examining how organisations preserve the reasoning behind important decisions over time. This is the fourth article in a series contributed exclusively to the Knowledge Management Institute.

The views expressed in this article are my own and do not represent the position of my employer or any institution I am associated with.

_______________________

Every year, organizations invest millions of dollars in evaluations, research, monitoring systems, lessons learned exercises, and knowledge management platforms. Yet many continue to face implementation challenges that were clearly identified years earlier.

The problem is not a lack of knowledge.

The problem is the inability to consistently transform knowledge into action.

Over the past two decades, NGOs, governments, and development agencies have generated unprecedented volumes of information through evaluations, research, monitoring systems, operational reviews, and partnerships. Knowledge management systems have improved the way this information is collected, organized, and shared.

Yet access to knowledge alone does not guarantee better decisions or stronger results.

Beyond Knowledge Management

Knowledge management focuses on collecting, organizing, and sharing information. Organizational intelligence goes a step further. It is the ability to transform evidence, experience, and learning into decisions, adaptations, and actions that improve performance and results over time.

Many organizations measure success through knowledge production: evaluations completed, reports published, lessons learned documented, or knowledge products shared. However, knowledge accumulation is not the same as learning. An organization may know something because it has documented it. Learning occurs only when that knowledge influences future decisions and behaviors.

The issue is rarely a lack of evidence. Most institutions already possess more evaluations, research findings, and lessons learned than they effectively use. The real challenge is transforming available evidence into action.

What Evaluation Can Teach Us

Evaluation provides a useful illustration of this challenge.

Across sectors and organizations, evaluations frequently identify similar issues: weak stakeholder engagement, unrealistic assumptions, insufficient risk management, limited local ownership, weak coordination, or sustainability concerns.

Consider a project where an evaluation identifies weak adoption of agricultural practices because market access constraints were overlooked during project design. Three years later, another project encounters the same challenge despite similar lessons having been documented previously.

The lesson existed. The organization simply failed to apply it.

This raises an important question:

If organizations continue to identify the same lessons year after year, are they truly learning?

In many cases, evaluations reveal less about project performance than about an organization’s ability to absorb and apply knowledge over time. Organizational intelligence extends the value of evaluation by ensuring that evidence informs future decisions before similar problems occur.

From Knowledge to Organizational Intelligence

Organizational intelligence is not a new department or software platform. It is a way of using knowledge more effectively.

In practice, it involves systematically reviewing previous evaluations during project design, integrating external evidence into decision-making, identifying recurring patterns across projects, tracking whether recommendations are implemented, and monitoring how evidence influences strategic choices.

Organizations that make this shift move:

·      From lessons identified to lessons applied.

·      From information access to evidence-informed decisions.

·      From reporting results to improving results.

·      From knowledge production to knowledge utilization.

They are also better positioned to preserve institutional memory. Staff turnover, organizational restructuring, and fragmented systems often disconnect lessons from future decision-making, causing organizations to relearn what they already know.

Looking Beyond Internal Knowledge

Organizational intelligence also requires looking beyond internal knowledge.

Valuable lessons often exist in partner organizations, academic research, government data, professional networks, and previous interventions. Organizations that combine internal experience with external evidence are generally better equipped to challenge assumptions, identify risks, and strengthen decision-making.

The Role of AI

Artificial intelligence may accelerate this transformation.

While much attention focuses on AI’s ability to generate content, its greatest value may be helping organizations connect and synthesize knowledge that already exists but remains scattered across evaluations, reports, databases, research papers, and individual experiences.

AI can support literature reviews, evaluation synthesis, evidence discovery, and pattern recognition across large volumes of information. However, technology alone cannot create organizational intelligence. The greatest barriers to learning are often organizational behavior, incentives, leadership commitment, and culture rather than information availability.

From Information to Impact

Knowledge management remains essential, but the ultimate objective is not knowledge management itself.

The ultimate objective is evidence-informed impact.

Organizational intelligence serves as the bridge between information and impact, helping transform evidence into decisions, decisions into action, and action into improved outcomes.

Organizations must move beyond asking:

“What knowledge did we produce?”

and begin asking:

“What decisions, adaptations, and improvements were influenced by the knowledge we produced?”

In the end, organizational impact may depend less on how much knowledge institutions generate and more on whether they are willing and able to change because of what they know.

______________________________________

We are all well aware that KM is no longer about static SharePoint libraries anymore. In the AI era, governance isn’t optional — it’s survival. AI can generate, summarize, and even auto‑tag knowledge, but without clear governance, you risk misuse, non-compliance, and chaos.

Step 1: Define Governance Roles (with AI in mind)

• Human content owners: AI can draft, but human intervention and ownership are non-negotiable. Ownership means deciding what’s valid, what’s junk, and what’s sensitive.
• AI assistants: Use AI for auto‑classification, metadata tagging, and even first‑pass reviews. But AI is a tool, and humans have to be the final authority.
• Approvers: Humans still need to sign off, especially for compliance or regulatory content. AI can flag risks, but it can’t take the legal hit.

Step 2: Map the Workflow (AI‑augmented)

• Drafting: Humans or AI can create. AI helps speed up first drafts, but drafts are clearly labeled as “AI‑assisted.”
• Review & Approval: AI can highlight inconsistencies, outdated references, or compliance risks. Humans decide what passes, what upgrades, and what gets replaced or archived..
• Publishing: Automated workflows push content live, but governance rules decide visibility (global vs regional).
• Archiving: AI can auto‑detect stale content, but governance policies decide whether it’s archived or updated.

Step 3: Regional Flexibility Meets AI

AI makes centralization easier, but regulations make it harder.

We are all well aware that KM is no longer about static SharePoint libraries anymore. In the AI era, governance isn’t optional — it’s survival. AI can generate, summarize, and even auto‑tag knowledge, but without clear governance, you risk misuse, non-compliance, and chaos.

Step 4: Keep It Human‑Centric

AI can automate, but governance must stay human‑centric.

• Don’t let AI approvals replace human accountability.
• Use AI to reduce friction (auto‑tagging, reminders, archiving suggestions).
• Keep ownership visible — every piece of content should show both the human steward and whether AI was involved.

In the AI era, governance isn’t about leaving it to AI — it’s about keeping trust alive. AI can flood your KM system with content, but governance ensures it’s accurate, compliant, and usable. Think of AI as the accelerator, and governance as the brakes and steering wheel. Without both, you’re just speeding toward chaos.

__________________________________________________

There is a pattern that Knowledge Management professionals will recognise immediately, even if they rarely say it out loud.

An organisation completes a significant programme or navigates a difficult period. The lessons are captured. People reflect honestly on what went well, what did not, and what they would do differently. The output is documented and filed.
‍

Two years later, the organisation faces a remarkably similar situation. A comparable decision needs to be made. And the lessons from that earlier experience are nowhere in the room.

Not because they were lost. Not because the documentation was poor. But because no mechanism existed to bring them forward at the right moment.

The lesson was captured. The decision never knew it existed.

A familiar problem with an unfamiliar name

This is one of the most persistent frustrations in Knowledge Management. It has been described in many ways: the knowing-doing gap, the lessons-learned paradox, the problem of knowledge that exists but does not travel.

What it has rarely been given is a precise structural explanation.

Lessons learned and decision-making exist in separate organisational spaces. Lessons are captured at the end of an experience. Decisions are made at the beginning of a new one. Between those two moments, there is typically no structured mechanism that asks: what has this organisation already learned that is relevant to this decision?

That gap is where significant organisational value quietly disappears.

Why existing practices do not always close it

Lessons learned processes serve an important purpose. They create structured reflection. They make tacit knowledge visible. They produce documentation that, at its best, preserves genuine organisational intelligence.

But they were designed primarily as a capture mechanism, not as a decision-support mechanism. The assumption embedded in most approaches is that if the lesson exists somewhere accessible, it will find its way to the decisions that need it.

In practice, that assumption rarely holds.

Decision-makers under time pressure do not search repositories. Teams forming around a new initiative do not systematically review what similar teams learned before them. The knowledge exists. The connection to the decision point was never made.

A practical reorientation

What is missing is not better capture. It is a deliberate connection between the moment a lesson is captured and the moment a relevant decision is being made.

This requires two things most organisations do not systematically provide.

First, lessons should be captured in a way that makes them decision-relevant — not just as a record of what happened, but as a forward-looking note for whoever faces a similar situation next. A lesson that says "stakeholder engagement was difficult" is less useful than one that says "stakeholder alignment must be established before the governance submission, not after — this assumption cost six weeks."

Second, lessons should be actively brought to decision points rather than waiting to be found — connected to governance and decision-making processes where relevant knowledge should be surfaced, not as an optional step, but as a built-in part of how important decisions are prepared

What Structured Decision Continuity adds

Structured Decision Continuity is a developing professional concept examining how organisations preserve the reasoning, context and traceability behind important decisions over time.

In the context of lessons learned, it asks one specific and practical question: was this lesson captured in a way that will actually reach the next relevant decision?

This reframes lessons learned from a retrospective activity into a forward-looking one. The lesson is not complete when it is documented. It is complete when it is connected — when there is a visible path between what was learned and the decision where that learning should be used.

A closing reflection

The question worth asking about any significant lesson captured in your organisation is not only: is it stored somewhere?

It is: will it be in the room when the next relevant decision is made?

Structured Decision Continuity is a developing professional concept examining how organisations preserve the reasoning behind important decisions over time. This article is contributed exclusively to the Knowledge Management Institute.

Disclaimer: The views expressed in this article are my own and do not represent the position of my employer or any institution I am associated with.

___________________________