Circulate Knowledge, Don't Just Document It

Circulate Knowledge, Don't Just Document It

In many organizations, the knowledge-management journey begins with a decision that looks entirely sensible: let us build a documentation system, stand up a content platform, and assign a team to collect procedures and write down policies. Budgets are spent, repositories fill up, and the program is declared complete. Then months pass, sometimes years, and everyone discovers that nothing essential has changed. The documents exist but no one reads them. The content is available but performance is unmoved. The expertise still lives in the heads of a few veteran employees, and when they leave, it leaves with them.

The problem is not the tools, nor commitment, nor budget. The problem is a misunderstanding of the nature of knowledge itself. Documentation is not knowledge management; it is a single snapshot of one moment in a long journey in which knowledge is continuously transformed. Real knowledge management is not the archiving of what we know today, but the management of a flow that turns the expertise latent in individuals into a renewable collective capability. Drawing on the SECI spiral developed by Nonaka and Takeuchi, this piece offers a practical framework for understanding and managing that transformation, rather than settling for documenting a single stop along the way.

The Documentation Illusion

When the question of knowledge management lands on the leadership table, thinking gravitates instantly toward tools: Which system do we buy? Which platform do we adopt? Where do we store it? A team is tasked with gathering what is already written, organizing it, and uploading it, and then the project is handed over as if knowledge had been managed. But what actually happened is the production of content, not the management of knowledge. The difference between the two is not one of degree; it is one of substance.

Documentation is a tool, and like any tool its effectiveness is measured by the context in which it is deployed, not by the volume of what it produces. When documentation shifts from means to end, knowledge loses its essence and becomes organized institutional waste arrayed neatly on tidy digital shelves. And organized waste is more dangerous than open chaos, because it creates the illusion of achievement: the indicators are green, the documents are stacked, the reports point to completion, while the real problem, that knowledge remains unable to flow, stays unresolved.

This is the most common knowledge illusion in business: confusing the ownership of a full repository with the ownership of a living capability. A repository stores static snapshots of knowledge at the instant of capture; a capability lets knowledge transform, travel, and renew. Organizations that measure success by document count are measuring their fullness, not their learning, and they sustain an expensive illusion that diverts attention from the real gap.

Explicit Knowledge: What Organizations See

When organizations talk about knowledge, they usually mean only one kind of it: explicit knowledge, the kind that can be expressed in words, numbers, and diagrams. A written policy, a documented procedure, a user manual, an analytical report; these are all forms of explicit knowledge that can be captured, recorded, and circulated on paper or screen.

Explicit knowledge has three properties that make it almost irresistibly attractive at the institutional level. The first is that it can be documented and fixed into a file. The second is that it can be transferred without personal interaction; the document is sent and read in the absence of its author. The third is that it can be measured in appearance, since it is easy to count the documents, pages, and articles produced and present them as evidence of progress.

But here lies the great paradox: this knowledge, which seems the easiest to measure and manage, is in reality the smallest and least valuable part of an organization's true knowledge. Common estimates in the knowledge-management literature suggest that what can actually be documented does not exceed roughly five percent of the knowledge genuinely circulating inside organizations. In other words, when an organization confines itself to managing the explicit, it manages the thin visible layer and leaves the real mass in shadow.

Tacit Knowledge: The Invisible Treasure

Tacit knowledge does not live in documents; it lives in people. When an engineer who has spent twenty years in the field decides that a strange sound from a machine signals an imminent failure before any reading shows it, that is tacit knowledge. When a seasoned procurement officer senses that a supplier is overpromising during a negotiation and that she should hedge, that is tacit knowledge. It is acquired judgment that precedes conscious analysis.

As the philosopher Michael Polanyi famously put it, tacit knowledge means that 'we know more than we can tell.' It is the sum of accumulated experiences, of patterns internalized through repetition, and of intuition polished by years of practice. It is the layer of expertise that lets a professional act with confidence in a situation he has never read about, because he has lived enough to recognize its contours.

Three traits make tacit knowledge profoundly important to the organization:

And so the deeper paradox reveals itself: organizations invest heavily in managing the visible, measurable five percent, and neglect the invisible ninety-five percent because it is not easily seen or counted. They tighten their grip on the shell and let the core seep out with every employee who departs and every piece of expertise that finds no one to capture it.

The Moment of Transformation: From Tacit to Explicit

If tacit knowledge is the real treasure, the pivotal question becomes: How do we draw it out of individual minds and into the inheritance of the organization? At its heart this is not a technical question answered by a platform or a system, but a human one about how to turn what is internalized and silent into what is shareable and durable.

Real transformation does not happen in a vacuum; it is generated in three distinct human moments. The first is the moment of deep dialogue, when an expert sits with colleagues in the context of a real problem, and the questions begin to draw out his intuitive responses and force him to put into words what he had been doing without thinking. The second is the moment of teaching, when the expert is obliged to explain what he knows to a novice, and discovers for himself the hidden structure behind his intuition as he tries to make it understandable. The third is the moment of structured reflection, when the organization pauses after a success or a failure to ask: What actually happened? Why? And what do we now know that we did not know before the experience?

These moments do not arise of their own accord, and they are not left to chance. They require a safe environment in which the expert feels that sharing his knowledge is not a threat to his standing nor a surrender of his distinction, but an extension of his impact and a widening of his influence. They also require a method that guides this transformation and makes it productive and organized, rather than leaving it hostage to fleeting moments that may or may not occur.

The SECI Model: The Spiral That Runs Knowledge

In 1995, professors Ikujiro Nonaka and Hirotaka Takeuchi, in their book The Knowledge-Creating Company, presented a model that changed the way the world thinks about knowledge management. They demonstrated that an organization's true value lies not in what it knows at a given moment, but in its capacity to create new knowledge continuously. The essence of their model, known as SECI, is that knowledge moves in a perpetual spiral between the tacit and the explicit through four successive phases, each lifting knowledge to a higher level.

Phase One — Socialization

Here tacit knowledge passes from one individual to another without going through documentation. It happens when a novice works side by side with an expert, observing him, imitating him, and experimenting alongside him, absorbing from his behavior what no document conveys. It is learning by immersion, where experience is acquired before it is ever framed in words.

Phase Two — Externalization

Here tacit knowledge turns into explicit; from experience into language. This is where real documentation happens, but it is documentation prompted by interaction and dialogue, not solitary documentation in front of a screen. The difference is fundamental: in externalization the document is born of a living conversation that extracts intuition, not of an obligation hurriedly filled in.

Phase Three — Combination

Here explicit knowledge from multiple sources is combined to produce a deeper understanding or innovative solutions. When an organization gathers the expertise of different teams, analyzes it, and reorganizes and connects it, explicit knowledge grows and evolves, and scattered information turns into composite knowledge worth more than the sum of its parts.

Phase Four — Internalization

Here explicit knowledge returns to the field. The employee who reads the manual and applies it in his work gradually turns it into new experience; that is, into new tacit knowledge that settles into his intuition. With that, the cycle completes and begins again at a higher level, where applied knowledge becomes the seed of a new round of socialization.

“An organization's true value lies not in what it knows at a given moment, but in its capacity to create new knowledge continuously.”

Where the Spiral Stalls in Most Organizations

Once the SECI cycle is understood, the diagnosis in most organizations becomes plainly clear: most of them stop at the second phase. They gather expertise, document it, upload it into the system, and then declare completion. But in doing so they have severed the spiral at its midpoint: they converted some tacit knowledge into explicit, but never completed the combination, and never returned the knowledge to the field to be transformed once more into living experience.

Three symptoms expose an organization suffering from this rupture:

The diagnostic conclusion is decisive: the break in the knowledge spiral is the root cause of the weak impact of most knowledge-management initiatives, not a shortage of tools, nor a scarcity of budget, nor a lack of commitment. Organizations have enough of all of these; what they lack is the management of the flow through to the end of the cycle.

The RAISO Approach to Circulating Knowledge

RAISO designs its knowledge initiatives from a single core principle: knowledge is not what we hold, but the flow we manage. In practice, this principle means that RAISO does not design knowledge-management projects that sit apart from and parallel to the work; instead it embeds the circulation of knowledge inside the operational processes themselves, where knowledge is actually generated and consumed.

RAISO's approach rests on three interlocking pillars:

This approach does not merely produce a richer repository; it produces a genuine learning culture in which the knowledge spiral keeps turning without stopping. The difference is that the final output is not a growing archive but a growing capability, and that is a shift in the very definition of success before it is a shift in tools.

Collective Participation: The Real Fuel for the Spiral

The SECI model does not run without fuel, and its real fuel is not technology nor systems, but people and the level of their participation. Collective participation means turning employees from passive consumers of content into active producers of knowledge, and this shift does not happen by issuing a memo, but by building the conditions that make participation a natural and rewarding behavior.

This requires building three elements together:

An organization that provides these three elements together discovers that knowledge begins to flow of its own accord. The spiral turns because people want to turn it, not because they are compelled to. And this is the surest sign of a mature system: when participation becomes a collective habit rather than a temporary campaign.

Designing Initiatives by SECI Phase

When an organization understands exactly where it stands in the SECI cycle, the design of knowledge initiatives turns from a general effort into precise engineering work. Each phase of the spiral needs a different kind of initiative that serves its function specifically, and a gap in one phase should not be treated with a tool designed for another.

When initiatives are distributed across the four phases with this awareness, the spiral completes rather than breaks. More importantly, the organization stops squandering its effort on documentation that finds no user, and begins steering every initiative toward the precise point where knowledge needs to move.

The Integrated System: People, Process, and Technology

Effective knowledge circulation needs three elements working together in harmony: people are the source, process is the context, and technology is the means. The correct equation is clear in its order: people first, then process second, then technology third, not the reverse. When this order is inverted and technology gets ahead of an understanding of people and work, the result is inevitable.

Systems and platforms facilitate communication, documentation, and access, but they neither produce knowledge nor guarantee its flow. Technology that comes before an understanding of people and process produces empty repositories that nothing moves but obligation, and that are soon abandoned. A tool does not create a behavior; it amplifies an existing one. If there is no culture of circulation, the platform alone will not create it.

But when an organization links these three elements within the SECI framework — people sharing, process providing context, and technology facilitating the flow — a qualitative shift occurs: the circulation of knowledge ceases to be a project that is managed and ends, and becomes a way of working that is lived day by day. At that point knowledge management is no longer a separate function, but a property embedded in how the work itself gets done.

From Repository to Capability: Redefining Success

The final question — which is in truth the first question that should be asked before buying any tool — is this: How does an organization measure its success in knowledge management? If the metrics are the number of documents created and the number of pages in the system, then the organization is measuring the fullness of its repository, not the vitality of its knowledge. And the wrong metric inevitably leads to the wrong behavior: more documentation that goes unread.

The real metrics look entirely different, and they point to impact rather than volume:

The truest test of any knowledge system is what happens when one of its pillars leaves. If the capability collapses with the departure of an individual, then knowledge was not managed but merely hosted in a person. An organization that succeeds at knowledge management defines itself not by what it has documented, but by what it has learned, what it has adapted to, and what it is able to accomplish today because of what it mastered yesterday. This is the fundamental difference between owning a repository and owning a capability — and it is capability, not the repository, on which genuine and sustainable excellence is built.

Conclusion: Start the Spiral

Knowledge management is not in what we write, but in the knowledge flow we manage. The SECI model offers us this understanding clearly: knowledge is not a static state stored on a shelf, but a dynamic phenomenon that lives in the continuous transformation between tacit and explicit, between the individual and the group, and between experience and application. Every completed cycle lifts the organization a degree above where it was.

And when an organization focuses on running this spiral rather than on building a repository, it does not produce content that accumulates; it builds a sustainable institutional capability to learn and evolve. In the context of the Kingdom's ambition for organizations that are more efficient and more competitive, turning the expertise of individuals into a collective capability that does not leave with those who leave becomes a condition of excellence, not an administrative luxury.

A question for reflection: Does your organization settle for documenting knowledge, or does it manage its full life cycle from experience to application and back to a deeper experience? The answer to this question alone determines whether you are managing content, or building knowledge.