No Longer Condemned to Repeat: Turning Lessons Learned into Lessons Remembered

  • David D. Walden
Conference paper


Many organizations have Lessons Learned processes in place, and both positive and negative lessons are dutifully captured in corporate Lessons Learned databases. Even with a well-defined process and an effectively designed database, many of these supposed Lessons Learned are not really learned at all. Subsequent projects often struggle to find lessons that are both accessible and relevant to their current endeavor. As a result, many organizations “relearn” these lessons over and over again.

This paper explores how an organization can transition from Lessons Learned to Lessons Remembered. Instead of having future projects “pull” information from a Lessons Learned database, it describes how Lessons Remembered can be “pushed” to relevant stakeholders via updates to an organization’s set of standard process assets. In this manner, the Lessons Learned become Lessons Remembered.


Intelligent Transportation System Federal Emergency Management Agency International Council Lesson Learn North Atlantic Treaty Organ 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. CAC, Center for Army Lessons Learned (CALL), US Army’s Combined Arms Center, (accessed April 2011)
  2. CJCSI, Chairman of the Joint Chiefs of Staff Instruction, 3150.25D, Joint Lessons Learned Program (October 10, 2008), (accessed April 2011)
  3. DHS, Federal Emergency Management Agency (FEMA) Learned Information System (LLIS), US Department of Homeland Security, (accessed April 2011)
  4. DOT, Intelligent Transportation Systems (ITS) Learned Information Database, US Department of Transportation, (accessed April 2011)
  5. Egeland, B.: A Lessons Learned Template. Project Management Tips (November 2009), (accessed April 2011)
  6. GAO, NASA: Better Mechanisms Needed for Sharing Lessons Learned, GAO-02-195, United States General Accounting Office (2002) Google Scholar
  7. INCOSE, INCOSE-TP-2003-002-03-03.2.1, Systems Engineering Handbook: A Guide for Systems Life Cycle Processes and Activities, Version 3.2.1. The International Council on Systems Engineering (INCOSE) (January 2011) Google Scholar
  8. Kirsch, D.: Learning Lessons Learned About Lessons Learned? Dr. Dan’s Daily Dose (May 16, 2008), (accessed April 2011)
  9. Knoco Ltd., Knowledge Management Processes, Lessons Learned, Knoco Ltd. Reference Section (April 2010), (accessed April 2011)
  10. MAIC, Mine Action Lessons Learned Database, Mine Action Information Center, (accessed April 2011)
  11. Meakin, B., Wilkinson, B.: The ‘Learn from Experience’ (LfE) journey in Systems Engineering. In: Proceedings of the 12th Annual International Symposium of the International Council on Systems Engineering. The International Council on Systems Engineering, INCOSE (2002)Google Scholar
  12. NASA, NASA Headquarters (HQ) Lessons Learned Information System (LLIS), US National Aeronautics and Space Administration, (accessed April 2011)
  13. NATO, Joint Analysis and Lessons Learned Centre (JALLC), North Atlantic Treaty Organization, (accessed April 2011)
  14. Santayana, G.: Life of Reason. Reason in Common Sense, vol. 1. Scribner’s (1905)Google Scholar
  15. SEI, CMU/SEI-2010-TR-033, CMMI® for Development (CMMI-Dev), Version 1.3. Software Engineering Institute (SEI), Carnegie Mellon University (November 2010)Google Scholar
  16. Seningen, S.: Learn the Value of Lessons-Learned. The Project Perfect White Paper Collection (2005), (accessed April 2011)
  17. Walden, D.: YADSES: Yet Another Darn Systems Engineering Standard. In: Proceedings of the Seventeenth Annual International Symposium of the International Council on Systems Engineering. The International Council on Systems Engineering, INCOSE (2007)Google Scholar

Copyright information

© Springer Berlin Heidelberg 2012

Authors and Affiliations

  • David D. Walden
    • 1
  1. 1.CSEPSysnovation, LLCShakopeeUSA

Personalised recommendations