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.
___________________________________





.png)
.png)
.png)
.png)