How Knowledge Management Helped Change NASA’s Culture | APQC Webinar

NASA’s culture shifted because knowledge management was built into how decisions get made after catastrophic failures—turning “lessons learned” into practical, searchable, teachable knowledge and giving engineers authority to speak up on safety-critical issues. Roger Forsgren, NASA’s chief knowledge officer from 2015 to 2021, frames knowledge management not as a culture changer by itself, but as the tool that helped NASA operationalize the cultural changes demanded by tragedy, oversight, and an aging technical workforce.

Forsgren begins with the scale and urgency: NASA employs about 18,000 civil servants with an average age of 46, supported by roughly 60,000 contractors. With tacit expertise concentrated in experienced employees, knowledge transfer becomes a risk-management problem, not just an efficiency project. He contrasts NASA’s earlier Apollo-era workforce age (about 28) with today’s younger averages at companies like SpaceX (about 29), underscoring why knowledge capture and transfer matter now.

The webinar then ties NASA’s knowledge management push to a history of both successes and failures. High-profile achievements—like the International Space Station, the James Webb Space Telescope, and the Space Launch System—sit alongside painful lessons from Apollo 1, Hubble’s mirror error, and Mars mission failures tied to unit and technical mistakes. But two accidents, Challenger (1986) and Columbia (2003), are presented as the decisive cultural inflection points. Challenger’s launch proceeded despite engineer objections about unusually cold temperatures and the failure risk of O-rings; Columbia’s disaster followed repeated foam-strike warnings that managers did not act on.

After Columbia, NASA introduced structural changes that Forsgren calls “technical authority and descending opinion.” The model gives every team member a personal responsibility to speak up when health and safety are at stake, and requires managers to listen. If consensus fails, independent subject matter experts can make the technical call—paid and positioned to be objective—rather than deferring to hierarchy. This shift is paired with governance pressure: the Aerospace Safety Advisory Panel, appointed by Congress, insisted NASA appoint a chief knowledge officer and addressed a core gap—NASA was good at gathering knowledge but weak at disseminating it.

Forsgren describes “lean Knowledge Management” as the practical implementation. NASA focused on the technical workforce, kept the program simple (avoiding academic taxonomy), and consolidated information into a single, open website: apple.nasa.gov. Instead of scattering lessons learned across many centers and servers, the one-stop portal supports searching for case studies, courses, and training.

To move tacit knowledge—expertise that lives in people’s heads—NASA fused knowledge management with training and created knowledge events designed to resonate with engineers. Case studies from Apollo 1, Challenger, and Columbia anchor coursework, while modules address critical thinking and cognitive bias in engineering decision-making. NASA also used video interviews with practitioners, podcasts (often 15–20 minutes every two weeks) to reach younger listeners, and leadership/mentorship programs that pair high-potential engineers with senior decision-makers.

Finally, Forsgren emphasizes cultural reinforcement mechanisms: a “day of remembrance” where employees revisit Apollo 1, Challenger, and Columbia, plus physical and traveling memorial-style artifacts (like the Columbia room at Kennedy Space Center and a Columbia artifacts tour for centers that can’t visit). The result, he says, is a more transparent environment where failures are treated as learning opportunities—and where engineers increasingly feel empowered to raise safety concerns and share what they learn before it becomes another preventable tragedy.