How should a lessons learned repository be used to inform future goals?

• A. Archive for regulatory purposes only
• B. Replace current project plans entirely
• C. Inform future goals and reduce repetition of mistakes
• D. Disseminate to external competitors

Answer: (C)

A lessons learned repository is a living knowledge base where teams capture what happened on projects—the decisions that worked, the missteps, why they happened, and the context. Using it to inform future goals means letting those insights shape planning, so goals are more realistic, milestones are better timed, and priorities reflect actual experiences. It creates a feedback loop: after a project, you review what went right and what didn’t, identify root causes, and apply concrete corrective actions to future plans. This helps set smarter objectives, adjust risk management, and align resources accordingly, reducing the chance of repeating the same mistakes. It’s an internal tool meant to improve performance, not just an archive, not a replacement for current plans, and it shouldn’t be shared with competitors.