Organizations rarely suffer from a complete absence of information. Especially around long-lived products, systems and capabilities, the opposite is usually true. Years of work leave behind requirements, architecture descriptions, source code, test cases, assessment reports, incident records, change requests, presentations, meeting notes, operational procedures, manuals, roadmaps and countless other artifacts. Some are current, some are obsolete, some contradict one another, and some look like little more than old junk.
Yet hidden among them may still be a surprisingly large part of the organizational understanding that people assume has already disappeared. The problem is that nobody is going to read all of it.
For a long time, that limitation shaped how we thought about organizational knowledge. If knowledge was going to be useful, somebody first had to turn it into something another person could reasonably consume. Knowledge had to become a document. The document had to be found. The document had to be read. Only then could the knowledge become useful again.
AI may be changing that sequence more fundamentally than we realize.
Knowledge Prepared for Reading
Traditional knowledge management makes considerable sense when the eventual consumer is a human reader. Suppose the useful understanding of a twenty-year-old product is scattered across thousands of requirements, test cases, architecture descriptions, incident reports, change records and pieces of source code. In theory, much of the knowledge is still there. In practice, it is inaccessible because no person can economically reconstruct it whenever a question arises.
The natural response is therefore to consolidate. Someone reads the sources, identifies what matters, resolves contradictions, creates structure and publishes the result as a specification, architecture description, product reference, handbook or some other authoritative document. That document reduces the amount of material the next person has to process. Instead of reading thousands of artifacts, the reader consumes one carefully prepared representation.
The model is essentially:
Knowledge → Publication → Reading → Understanding
This is not a bad model. It solved a real problem.
But it also created another one. Every publication became another representation that had to remain synchronized with the knowledge from which it was derived.
The Cost of Publication
The work does not stop simply because somebody has written the document. Requirements continue to change. Architecture evolves. Code changes. Incidents reveal new information. Assessments produce findings. Decisions are made in meetings. New constraints appear. Old assumptions become invalid. The publication therefore begins ageing almost immediately.
Keeping it useful requires somebody to notice relevant changes, determine how they affect the document, update the appropriate sections and ensure that the resulting representation remains internally consistent.
If several publications depend on the same underlying knowledge, the problem multiplies. The same new insight may need to appear in a product reference, an architecture description, a methodology, training material and assessment guidance.
The problem is no longer simply preserving knowledge. It is maintaining all the representations through which people are expected to consume it. That cost was difficult to avoid when publication was the necessary bridge between accumulated information and human understanding.
But what happens when the bridge is no longer always necessary?
From Reading to Asking
Imagine someone encounters a strange piece of code in a twenty-year-old system. Traditionally, the hope would be that somewhere there is documentation explaining it. Perhaps an architecture description contains the rationale. Perhaps an old requirement explains the business rule. Perhaps somebody wrote a decision record. If the right document exists, is current, can be found and contains the answer, the problem is solved.
But the explanation may never have existed in one place. The relevant evidence might instead be scattered across an old requirement, a source-control change, two regression tests, an incident report and a presentation written three years later.
A human is unlikely to discover all of those relationships. An AI-enabled knowledge environment potentially can.
The person no longer needs to ask:
Which document should I read?
They can ask:
Why does this code exist?
The system can retrieve relevant evidence from several sources and synthesize an answer for that particular question.
That is a different model of knowledge consumption. The answer did not have to be published before the question existed. The representation was created because the question existed.
The Question Becomes the Interface
This changes the role of the document. For much of organizational history, documents have served as interfaces to knowledge. Someone had to anticipate what future readers might need, decide how to organize it and create a representation that could later be consumed.
The document therefore bundled many possible future questions into one predefined structure. A person looking for one answer might have to read twenty pages because the author had to write for many readers and many possible purposes.
When knowledge can be interrogated directly, the question itself can define the representation. A Product Owner may ask what business outcomes and constraints apply to a proposed change. An architect may ask which assumptions shaped a particular design decision. An assessor may ask which quality expectations apply and what evidence supports them. A developer may ask why a seemingly unnecessary rule exists. Each question creates a different view over the same underlying body of evidence.
The prompt becomes, in effect, a temporary specification for the representation required at that moment. That does not make documents obsolete. It changes their status.
Documents Become Views
There are many situations in which a stable document remains useful. A contractual context may require a frozen specification. An assessment may need a citable baseline. Governance may require a reviewed reference. A publication may deliberately capture the state of understanding at a particular point in time. In those situations, generating and preserving a stable document makes perfect sense.
But the document no longer has to be treated as the knowledge itself. It can be understood as one representation of a larger body of knowledge, produced for a particular purpose at a particular moment.
Tomorrow, another audience may need another representation. And sometimes no publication is needed at all. Someone asks a question, receives a synthesis supported by relevant evidence, makes a decision and continues working. The organizational knowledge has been consumed without first being packaged into a document.
Reachability Becomes the Problem
Once publication is no longer the mandatory interface, the knowledge-management problem changes.
The first question is no longer:
Where should we put all our knowledge?
It becomes:
Can we reach the relevant evidence when somebody needs to understand something?
That distinction has architectural consequences. Requirements do not necessarily need to be copied into a central knowledge repository. Architecture information does not need to be moved simply because other people may need it. Code does not need to stop living in source control. Operational evidence does not need to become prose before it can contribute to organizational understanding. The sources can remain where they belong.
What matters is that the knowledge environment can reach across them. Depending on the technology, that may involve indexing, linking, retrieval, ingestion or some combination of them. The implementation can vary.
The principle remains simple:
Do not move knowledge merely to centralize it. Make it reachable.
Old Information Changes Role
This also changes how we should think about accumulated historical material. When the objective is to create one clean authoritative document, old and contradictory information looks like a problem to eliminate. Before publication, someone has to decide what is current, what is obsolete and what can safely be discarded.
A knowledge environment built around interrogation has different needs. An obsolete requirement may no longer describe what the product should do today, but it may explain why a piece of code was introduced fifteen years ago. A superseded architecture decision may reveal which trade-off originally shaped a subsystem. An old incident may explain an otherwise mysterious constraint. A test case may preserve a business rule whose original requirement has disappeared. Obsolete is not the same as worthless. Historical evidence can remain useful precisely because it is historical.
The challenge is therefore not to make every source appear equally true. It is to preserve enough provenance to interpret each source correctly. When was this recorded? What did it apply to? Was it superseded? What is authoritative today? Which other sources support or contradict it?
Without those distinctions, broad access produces confusion. With them, history becomes evidence.
Connect First, Curate Where It Matters
This raises another possibility. Traditional knowledge initiatives often begin with extensive cleanup. Thousands of artifacts must be reviewed, classified and curated before they are considered suitable for inclusion in the knowledge base. That made sense when the objective was publication. Someone had to decide what deserved to appear in the finished representation.
But if AI can inspect sources at question time, asking humans to inspect everything first may recreate exactly the economic problem AI was supposed to help solve.
It may be more useful to begin broadly. Connect the old requirements. Connect the architecture documentation. Connect the test repositories, assessment reports, change histories and incident records. Make the surviving evidence reachable, subject to appropriate security and governance.
Then allow actual questions to reveal where human curation is valuable. Some sources will rarely matter. Others will repeatedly appear in important answers. Some contradictions will prove significant enough to resolve. Some missing rationale will become visible because the available evidence cannot explain what exists.
Curation does not disappear. It becomes more targeted. Instead of deciding in advance what every future reader might need, human effort can concentrate on the areas where real questions expose uncertainty, conflict or importance.
The Knowledge Environment Must Be Able to Say “I Don’t Know”
There is an obvious danger in all of this. A system capable of synthesizing across thousands of sources can produce an explanation even when the surviving evidence does not justify one. Reachability without provenance can therefore create the illusion of understanding.
A useful knowledge environment must preserve the difference between what is explicitly recorded, what is supported by several sources, what has been reconstructed from indirect evidence, what is disputed and what remains unknown.
A plausible explanation should not quietly become historical fact merely because it sounds convincing. Sometimes the correct answer to a prompt will be that the available evidence does not explain why something exists. That is not a failure. It is knowledge about the state of organizational understanding. And it tells us where human attention may still be required.
From Knowledge Prepared for Reading to Knowledge Prepared for Questioning
This may be the deeper change. Historically, organizational knowledge had to be prepared for reading. Someone had to decide what mattered, assemble it into a coherent representation and publish it in anticipation of future need.
AI makes another model increasingly practical:
- Preserve the sources.
- Preserve their provenance.
- Preserve deliberately what cannot reliably be reconstructed.
- Make the rest reachable.
- Then allow future users to ask the questions that actually matter when they matter.
The knowledge environment no longer has to anticipate everything somebody may eventually need to read. It has to preserve enough reachable evidence that somebody can ask what they need to know.
That changes the economics of Understanding Debt as well. A twenty-year-old system may appear poorly understood not because all of its understanding has disappeared, but because the surviving pieces are fragmented across thousands of artifacts that no human could economically reconstruct.
Making those fragments reachable does not magically restore everything. Some rationale will genuinely have disappeared. Some decisions will remain ambiguous. Some evidence will contradict itself. But fragmented knowledge is no longer necessarily inaccessible knowledge.
Reflection
Perhaps we have spent too much time asking where organizational knowledge should live. That question naturally leads toward repositories, migrations, canonical documents and the difficult work of keeping them synchronized.
The more interesting question may now be how organizational knowledge should be consumed.
For a long time, the path was largely:
Knowledge → Document → Read
Increasingly, another path becomes possible:
Knowledge → Question → Synthesis
Sometimes that synthesis will become a document. Sometimes it will become a decision, an explanation, an assessment or another question.
The important change is that publication no longer has to come first. Knowledge does not necessarily need to be assembled into the representation somebody might one day need.
It needs to remain sufficiently connected, contextualized and trustworthy that the representation can be created when the need appears.
The document is no longer always the interface. Sometimes the question is.
Leave a Reply