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.

______________________________________

‍

Knowledge mapping is the practice of making your organisation’s collective intelligence visible. It is not about building a database. It is not about writing everything down. It is about creating a navigable map of who knows what, where critical resources live, and where the dangerous gaps are.

‍

‍

We can use a map of a mall or a city as an example. The map does not replace the city, a mall, or a shopping center — it helps you navigate them easily without getting lost, and find specific shops, restaurants, or entertainment zones. A knowledge map does not replace expertise — it helps you find it.

A good knowledge map tells you three things:

•        What do we know? (The domain taxonomy — your knowledge categories)

•        Who knows it? (The expert directory — your knowledge holders)

•        Where are the gaps? (The gap register — your risk picture)

Imagine your most experienced  Proposal Manager or Lead Engineer leaves next month. Could your team still deliver with the same efficacy and timelines, especially if the KT plan is not in place? Would you even know what knowledge they left with?

Most organisations have enormous amounts of knowledge — but it is invisible. It lives in people’s heads, scattered across files, buried in email threads. Knowledge mapping makes the invisible visible. It answers three questions:

•        What do we know as an organisation?

•        Who knows it?

•        Where are the dangerous gaps?

When knowledge is mapped well, your organisation can:

•        Find the right expert in minutes, not days

•        Onboard new staff faster with clear knowledge paths

•        Reduce the impact when someone leaves — the knowledge transfer plan is already written

•        Make better decisions because the right knowledge reaches the right person at the right time

The Knowledge Mapping process does not require a special tool or an AI. All you need is a clear process, a bit of time, and people willing to be honest about what they know.

Let’s discuss the six-step mapping process as well as the cost of not mapping your knowledge and experts in the next blog.

_________________________

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.

___________________________

A few years ago, a Knowledge Management team I am aware of spent considerable effort documenting the lessons from a major programme. They interviewed people, captured the key insights, organised them clearly and stored everything in a system that was genuinely accessible.

Six months later, the organisation launched a similar programme.

Almost none of the captured lessons informed the new decisions being made.

Not because the knowledge was hidden. Not because people were indifferent. But because there was no real connection between what had been captured and the moment when decisions were actually being made. The knowledge existed in one place. The decisions happened somewhere else.

Capture is not the same as use

Knowledge Management has made genuine progress over the past two decades. Organisations capture more than they used to. They share more. They structure experience into frameworks, lessons and repositories that previous generations did not have.

But capturing knowledge and ensuring it reaches decisions are two different things.

A lessons-learned repository is not, by itself, a decision input. An expertise directory does not automatically put the right knowledge in front of the right person at the right moment. A documented best practice does not guarantee it shaped the choice that was made.

The path between what an organisation knows and what actually influences its decisions is often shorter in theory than in practice.

Why this gap is structural, not a failure

It is worth being precise about this, because Knowledge Management professionals sometimes hear this observation as a criticism. It is not.

KM was largely designed to solve a real and important problem: organisations were losing knowledge they needed to retain. The response — capture it, structure it, share it — was the right one.

But there is a second problem that sits adjacent to the first: even when knowledge is captured, it may not reach the decisions it was meant to support.

That is not a KM failure. It is a structural gap between two things that are related but not automatically connected — knowledge management and decision-making.

Closing that gap requires something more deliberate than a better repository or a more comprehensive lessons-learned process. It requires thinking about the path from knowledge to decision as something worth designing.

What that connection looks like in practice

It does not need to be complicated.

For an important decision, it is worth asking explicitly: what does the organisation already know that is relevant here? What lessons exist? What expertise is available? What have we learned from similar situations?

And then — crucially — making sure the answers actually reach the people making the decision, at the moment they are making it, in a form they can use.

This is different from storing knowledge well. It is about ensuring that knowledge travels to the right moment.

It also means preserving, after the decision, what knowledge was used and how it shaped the reasoning. Because that connection — between knowledge and decision — is exactly what tends to disappear over time, as last week's article explored.

Why this matters now

Decisions are where knowledge either proves its value or quietly fails to.

An organisation can have an excellent KM function and still make decisions that ignore what it knows. It can have well-maintained repositories and still repeat avoidable mistakes. Not because KM is not working, but because the link between knowledge and decision was never explicitly made.

Structured Decision Continuity examines that link — not as a criticism of Knowledge Management, but as an extension of what KM can offer when it is connected more deliberately to the decisions it is meant to support.

The question worth asking is not only: do we capture our knowledge?

It is: does our knowledge reach our decisions?

‍

This article is part of a monthly series on how organisations can preserve the reasoning behind important decisions, explored through the lens of Structured Decision Continuity.

___________________________________

In many discussions about AI literacy, a natural follow-up question quickly appears: What does Knowledge Management literacy mean inside organisations?

Τhe term is often mentioned, but rarely explained in practical terms.
‍
Knowledge Management literacy is not primarily about tools or platforms.
‍

It is about understanding how organisational knowledge is recognised, structured, and validated so that it can reliably support decisions.The simple framework below summarises four practical capabilities that shape how organisations work with knowledge.
‍

These capabilities may appear straightforward. In practice, they often determine whether knowledge supports sound decisions or simply turns into fragmented information.

1. Locate Knowledge

‍The first capability is the ability to locate where organisational knowledge actually lives.
‍

‍

In many organisations, knowledge is distributed across multiple systems: document repositories, collaboration platforms, shared drives, internal portals, and email archives. Without a clear understanding of this landscape, people often spend a considerable amount of time simply searching for information.

Knowledge Management literacy therefore begins with a basic awareness of the organisation’s knowledge environment: where different types of knowledge are stored and which systems serve which purpose.

Without this basic capability, organisations struggle to use knowledge consistently, whether by people or by AI systems.

2. Identify the Authoritative Source

‍Locating information is not enough. The next step is recognising which version of knowledge can be trusted.

‍

‍

In practice, organisations often operate with multiple versions of the same document, guideline, or procedure. Teams may rely on different sources without knowing which version is officially maintained.

Knowledge Management literacy therefore includes the ability to identify the authoritative source: the version of knowledge that is validated, maintained, and intended to guide decisions.

‍3. Understand Knowledge Context‍

Knowledge is never created isolation. It always emergies in a particular context: a regulatory environment, a project phase, and a specific organization challenge.

‍

‍

Understanding this context is essential for interpreting knowledge correctly. Without it, documents and guidance may easily be reused in situations where they no longer apply. Knowledge Management literacy therefore involves recognising how and why knowledge was produced, and under which conditions it should be interpreted.

4. Validate Knowledge before reuse

Finally, knowledge must be validated before it is reused, shared, or embedded in automated processes.

‍

‍

Organisations evolve, policies change, and procedures are updated. If knowledge is reused without verification, outdated information can easily spread across teams or systems.

Knowledge Management literacy therefore requires the ability to confirm that knowledge remains current and relevant before it is applied again.

Why these capabilities matter for AI

These four capabilities become particularly important as organisations explore AI-enabled systems.

AI can retrieve, process, and connect information at scale. However, the quality of its outputs depends directly on the structure and reliability of the knowledge it accesses, including the systems developed by generative AI development companies.

If knowledge sources are fragmented, unclear, or outdated, AI may simply accelerate confusion rather than support judgement.

For this reason, developing Knowledge Management literacy is not only a Knowledge Management concern. It is increasingly becoming a foundational capability for organisations seeking to use AI responsibly and effectively.

Future Knowledge Nuggets will explore these capabilities in greater detail and examine how organisations can strengthen them in practice.

‍

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.

__________________