The Living Nature of Collective Intelligence

The Mystery of Lost Knowledge

According to the following article; Lost Knowledge — What Are You and Your Organization Doing About It? | ERE:

If NASA wanted to send a man to the moon or Mars today, it couldn’t do it.

All the knowledge and experience is gone. NASA would literally have to start from scratch. How did a world-class organization like NASA lose the ability to recreate one of the greatest achievements in the history of mankind?

Similarly, a petrochemical executive discovered that his company thought it could fix the problem of lost knowledge just by hiring more people. Having less experienced people working in sophisticated computer-controlled manufacturing operations increased the risk of serious and costly mistakes. An investigation into an explosion at this executive’s chemical plant found that the engineer in charge had only been out of college a year, and the operators in the control room at the time of the accident all had less than a year of experience in the unit.

These aren’t isolated incidents of carelessness or poor documentation. The manuals existed. The procedures were written down. New employees were trained according to established protocols. Yet somehow, the living knowledge that had once ensured smooth operations and safe practices had evaporated when experienced workers departed.

How do organizations lose knowledge they once possessed?

To answer this question, let us examine the essential nature of “knowledge.”

The Fallacy of “Static Knowledge”

We commonly think of knowledge as something we “have”—a static commodity of facts and procedures that can be stored and transferred like library books, existing independently of the knower. Yet this assumption collapses when tested against real-world failures like NASA’s lunar program or Texas Instruments’ production breakdowns, where meticulously documented procedures remained intact while the actual ability to execute missions or operations vanished—thus proving that preserved information is not the same as living knowledge.

In other words, information is not knowledge until it has been internalized and integrated into lived experience. A new engineer may have access to all the same technical manuals that the veteran possessed, but possessing the documentation is fundamentally different from having internalized its meaning through years of application. The manual describes the procedure, but only through repeated practice does one develop the intuitive sense of when something feels wrong, when a deviation from standard protocol might be necessary, or when seemingly minor variations signal deeper problems.

David DeLong, author of “Lost Knowledge: Confronting the Threat of an Aging Workforce,” distinguishes between explicit knowledge (information that can be easily explained and stored in databases or manuals) and tacit knowledge (experience, stories, impressions and creative solutions that accumulate over years and are much harder to capture). What organizations can lose isn’t the explicit knowledge – the manuals and procedures remain intact. What vanishes is the tacit knowledge – the lived experience of what the knowledge “means”, and it actually works in practice.

Knowledge as a Living Process

Real knowledge exists not as a static thing but as a dynamic process of being and becoming. It lives in the constant flow between theoretical understanding and practical application, between abstract concepts and hands-on implementation. Knowledge is less like a library book and more like a living organism that requires constant activity to maintain its vitality.

Consider the spectrum of knowledge types within any complex endeavor:

Between these extremes flows a river of knowing – where abstract principles and concrete experience endlessly reshape each other; the process never stops:

This isn’t knowledge transfer but knowledge transformation. With each cycle:

The actual knowledge of the team or the organisation is contained within this dynamic give-and-take. As long as the organisation is alive and the team is functioning, that knowledge continues to exist and to happen. However, once the organisation or team cease to exist, the “happening” of that knowledge, and the knowledge itself, can vanish into thin air.

NASA: Knowledge in Action

The NASA space program operated as a living knowledge ecosystem – a system where expertise did not reside in any single person but in the dynamic exchange between team members. Theoretical understanding constantly cycled into practical application and back again, creating a feedback loop of continuous learning and refinement.

• Rocket scientists didn’t just know propulsion theory – they understood how it played out in the specific context of Saturn V engines, with their unique quirks and limitations.
• Mission controllers didn’t just calculate orbital mechanics – they knew how those calculations felt in real-time, under pressure, with incomplete data and split-second decisions.
• Astronauts didn’t just memorize procedures – they internalized how those procedures worked in the unpredictable reality of spaceflight, where human and mechanical variables constantly shifted.

This knowledge wasn’t static; it evolved through constant collaboration. Engineers designed systems, technicians tested them in real-world conditions, and their observations looped back to refine the original designs. Each iteration deepened the team’s collective intelligence. The result was knowledge that no single individual could possess—it lived in the relationships between roles, in the rhythm of problem-solving, in the shared memory of past failures and breakthroughs.

When the NASA space program wound down and teams disbanded, something irreplaceable was lost. The individuals retained their personal knowledge and experience, but the living ecosystem of collective intelligence simply ceased to exist. The knowledge that had existed in the flow between team members, in their collaborative problem-solving processes, in their shared temporal experience of working through challenges – this knowledge had no way to survive the team’s dissolution.

Documentation could preserve the “what” but not the “how” or “why.” Technical specifications could capture the final solutions but not the living process of how those solutions emerged from the interplay of theory and practice.

Conclusion

Knowledge is not a fixed artifact but a process – one that exists only in motion, in the active exchange between minds, in the continuous cycle of application and adaptation. It is temporal by nature, emerging from the interplay of theory and practice, preserved not in documents but in the living rhythms of collaboration.

NASA’s moon missions did not fail to endure because manuals were lost or data was deleted. They faded because the conversation that sustained that knowledge – the daily back-and-forth between engineers, technicians, and astronauts – stopped. The knowledge lived in the act of solving problems together, in the shared language of trial and error, in the unspoken adjustments made under pressure. When the teams disbanded, that dynamic collapsed, and with it, the knowledge itself dissolved.

This ephemeral quality reveals something fundamental: knowledge is not just what we possess but what we do. It thrives in the space between people, in the friction of debate, in the feedback loops of action and reflection.

In this sense, knowledge cannot be stored; it must be fed. It cannot be archived; it must be practiced. The lesson of NASA teaches us that to preserve knowledge we must keep it alive, by keeping the conversation going and by maintaining collective memory.