Knowledge Management for Uncertainty

An archive can tell an organization what it has preserved, but it cannot tell us which emerging pattern deserves resources before that pattern becomes an emergency. I do not consider this a failure of archives; I consider it a warning about asking one instrument to perform the whole orchestra.

This is the limit of the archive metaphor. Preserving what was is noble work. A coastal campus facing rising water, or an industry facing a regulatory change that remakes its obligations, has a different requirement. It needs to practice for several possible futures while the present still permits choice. Knowledge management becomes a field guide for uncertainty rather than a compliance checklist for cataloging deliverables.

This does not make evidence less important. Future-facing work depends on a trustworthy record of past decisions, current conditions, and prior experiments. The difference is in how that record is used. Instead of asking only whether a document is stored and searchable, the organization asks what it would need to notice, decide, connect, and revise if a familiar condition changes.

A chain of capabilities supports that work. Strategy considers several possible futures rather than one corporate mandate; governance sets boundaries within which experiments can breathe; infrastructure keeps records and people connected while classifications, systems, and teams change; and memory retains provenance without being poured into amber. Connections, learning, innovation, and feedback carry the rest of the work, recombining expertise, testing speculative prototypes, and making reflection useful before it becomes an autopsy.

Each capability has a future-facing job. Strategy needs a way to compare possibilities without pretending that one forecast will become fact. Governance needs to establish the boundaries for experimentation: who can try what, what evidence must be retained, and when a local experiment needs broader review. Infrastructure needs to make records and people connect even when classifications, systems, and teams change. Memory needs to preserve provenance while allowing current work to reinterpret what an old record means.

Connections and learning make the chain social. A distributed organization may have useful expertise in several locations but no regular practice for combining it. A training program may explain a standard procedure while missing the situation in which a worker has to adapt it. Future practice asks whether knowledge can travel into the moment of work, where a new condition becomes visible and a person needs more than a static course.

Innovation provides the place for speculative prototypes. The prototype is not proof that a future will occur. It is a way to test an assumption, discover a dependency, or make an unfamiliar possibility concrete enough for people to discuss. Feedback closes the route. A reflection that never changes a decision, practice, or next experiment is a record of concern, not a learning loop.

The coastal campus makes this visible. Rising water may affect buildings, access routes, maintenance plans, student movement, insurance, and long-range investment. A clean repository can hold flood studies, plans, maintenance records, and prior decisions. The organization still needs a strategy practice that considers alternatives, governance that permits cross-unit testing, infrastructure that connects the records, learning that reaches facilities and leadership, innovation that explores responses, and feedback that records what the tests reveal.

The same logic applies when a regulatory framework changes an industry. The first response may be to collect the new requirements. That is necessary. The harder work is to identify where the change reaches practice, who needs to interpret it, which systems need adaptation, what experiments can clarify the effect, and how the organization will learn from the first implementation rather than merely surviving it.

“Craft, courage, and community” sound dangerously close to values painted on a meeting-room wall unless an organization can point to the capability that has no future-facing work yet. Perhaps the repository is strong but the feedback loop is absent; perhaps strategy has scenarios but governance permits no test; perhaps innovation has prototypes but learning never reaches the people who deliver the work. Find that missing capability and give it a job. The archive remains necessary, just no longer burdened with predicting the water.