NASA Goddard’s Knowledge Management (KM) approach rejects the idea that institutional wisdom can be stored in digital libraries or databases. Instead, they emphasize the transfer of tacit knowledge—experiential know-how that cannot be captured in manuals. By institutionalizing “Pause and Learn” sessions and narrative-driven Case Studies, NASA transforms project milestones and failures into stories that build critical thinking and capture both the “why” and “what” behind decisions. This human-centric, social approach prioritizes psychological safety, storytelling, and deliberate reflection over technical systems.

Main Ideas

• Tacit vs Explicit Knowledge: Distinguishing between what can be written down (manuals) and what is lived (experience).
• The Social Nature of Knowledge: Knowledge is not a commodity to be stored; it is a process that happens between people.
• The Case Study Method: Using narrative-driven accounts of past missions to teach decision-making and critical thinking.
• Pause and Learn (PaL): Moving beyond “Post-Mortems” to conduct reflective sessions during the lifecycle of a project.
• Culture over Technology: Systems are useless if the organizational culture does not encourage the sharing of failures and insights.

Actionable Takeaways

• Implement “Pause and Learn” (PaL): Schedule brief reflection sessions at key milestones during a project, rather than waiting for the end.
• Adopt Storytelling: When documenting a project, include a narrative component that explains the hurdles and the reasoning behind “pivots.”
• Shift KM Budgeting: Invest more in facilitating expert-to-novice conversations and peer-review sessions than in expensive database software.
• Ask “What should we have known?”: During reviews, ask what information was available but ignored, rather than just what information was missing.

Mental Models

• Polanyi’s Paradox: The idea that “we know more than we can tell”—highlighting the difficulty of capturing tacit knowledge.
• The After-Action Review (AAR): A structured review process for analyzing what happened, why it happened, and how it can be done better.
• Double-Loop Learning: Not just fixing a problem, but questioning the underlying policies and goals that allowed the problem to occur.

Surprising or Counter-Intuitive Points

• NASA Dislikes Databases: One might expect the world’s most advanced technical agency to rely on “Big Data” for KM, but they find human storytelling far more effective for high-level learning.
• Failure as an Asset: In the NASA model, a well-documented failure is often more valuable for the organization’s future than a quiet success.
• Learning is “Slow”: Goddard’s methods (Case Studies and PaLs) require taking expensive engineering time away from “work” to “talk,” which counter-intuitively speeds up the overall mission success rate.

Connections

• Medical Residency: Like rocket science, medicine uses “Morbidity and Mortality” (M&M) conferences to turn errors into collective learning.
• Software Engineering: The concept of “Blameless Post-mortems” in DevOps mirrors Goddard’s “Pause and Learn” philosophy.
• Ancient Oral Traditions: NASA’s use of storytelling brings high-tech engineering back to the most fundamental human way of passing down survival information.