Technology Isn’t the Blocker Anymore, But We’re Still Acting Like It Is
You do not have a technology problem. You have a "it lives in Janet's brain and she is on holiday" problem.
Technology is no longer the constraint. But most organisations haven't figured out what it is.
We were speaking with someone building in a regulated environment in the US. They were trying to build a knowledge system. But as we explored it together, the conversation kept drifting away from technology and towards something more fundamental: how do you turn information that lives in documents, systems, and people's heads into something that can actually be applied?
That is the question most organisations are not asking yet.
Where We Think the Problem Is
If you look at this purely from a technology perspective, the solution already exists.
We have the infrastructure. We have the tools. We have the ability to connect systems and surface information.
Technology is not the constraint it once was. Even the data itself is not always the real problem. In many cases, organisations already have access to large amounts of information across repositories, documents, and systems.
But having access to data does not solve the problem. It simply exposes the next one.
The Challenge
Once information is available, the question becomes how to organise it in a way that makes sense: How do you structure documents so that they are usable? How do you make information accessible in a way that reflects how people actually work?
And then the challenge goes deeper. Because even when information is well organised, that still does not mean it can be applied correctly.
The Applied Knowledge Problem
This is where things become more complex, especially in regulated environments.
It is not just about finding an answer. It is about knowing which answer applies, in which situation, and why.
Does a decision depend on regulation?
On internal policy? On legal requirements? On the specific industry?
In which country does the company operate?
The same question can produce different answers depending on context. And context introduces exceptions. This is the difference between having a library full of books and knowing which book to open, which chapter matters, and why that chapter is more relevant than another that looks similar on the surface.
Most systems focus on storing information. Very few focus on helping people apply it.
The Human Bottleneck
During the conversation, something else came up. In their organisation, people often have to wait for a manager to answer questions.
Not because the information does not exist, but because the manager remembers something from a previous situation. A decision that was made. A nuance that was never written down. That knowledge is not available on demand. So people have to wait.
This highlights that knowledge exists in layers. There is:
Formal knowledge: Policies, procedures, official guidance. This is usually documented.
Informal knowledge: Conversations, a shared understanding of how things are actually done. This is often lost.
Contextual knowledge: The reasoning behind decisions. The exceptions. The lessons from past situations. This is almost always lost.
Most knowledge systems focus on the first layer. Most value sits in the second and third.
Where the Competitive Advantage Sits
For organisations investing in AI, this distinction matters. The technology itself can be replicated. It will continue to become more accessible and more affordable.
Spending heavily on tools alone does not create a lasting advantage. The advantage comes:
From understanding your knowledge well enough to structure it properly.
From knowing how information is applied in real situations.
From preserving the reasoning behind decisions.
From making context available, not just content.
Companies that are moving forward are not simply building better search systems. They are solving how knowledge is applied.
A Different Way to Think About It
This is not just a technical challenge. It is about removing barriers that prevent people from doing their jobs well.
When knowledge is scattered, or locked in someone’s memory, or missing the context needed to apply it, people are forced to wait. They are forced to guess. Or they rely on a small number of individuals to interpret information for them. That slows everything down.
Recognising that technology is no longer the blocker allows us to focus on what actually matters: turning information into applied knowledge, making expertise accessible when it is needed, and building systems that understand not just what is written, but why it matters.
Summary
Technology is no longer the primary constraint in building knowledge systems.
The real challenge lies in structuring knowledge so that it can be applied correctly in context. When organisations focus only on tools, they risk missing the deeper work required to make those tools effective.
By shifting attention to applied knowledge, preserving context, and making expertise accessible, companies can remove barriers, improve decision-making, and create systems that genuinely support how people work.
The question is no longer: “Do we have the technology?” It is: “Do we understand our knowledge well enough to use it properly?”.
Key Points
The competitive advantage isn’t in the AI tool itself. It’s in having the applied knowledge structured correctly so any tool can use it effectively
Companies getting ahead aren’t building better search - they’re solving how knowledge gets applied in context
Technology can be replicated - the infrastructure and tools for building knowledge systems already exist and will only get more accessible
The first challenge appears to be data, but even with access to all repositories, that’s not enough. The biggest challenge is turning data into applied knowledge: understanding which information matters for which situation and why
Having documents isn’t the same as knowing which policy applies to this company, in this country, for this specific case
Context creates exceptions: the same question might need different answers based on company, industry, or geography
Critical applied knowledge often sits in someone’s head (like a manager who remembers why a past project was handled differently)
