FAQ
Should we include anonymous feedback in our lessons learned document?
Anonymous feedback can reveal honest insights, but it’s best used as supplementary input rather than the core of your report. Combine it with direct team discussions to balance transparency with accountability. Focus the main document on actionable items tied to specific roles or processes, then note broader trends or frustrations anonymously in a separate appendix if needed.
How detailed should we get when describing ‘what didn’t work’?
Be specific enough to identify patterns—e.g., ‘vendor X missed three deadlines due to miscommunication’ instead of ‘delays occurred.’ Include enough context for others to understand the root cause without diving into irrelevant details. The goal is to prevent repetition, not assign blame. Save emotional or personal critiques for team retrospectives, not the official record.
Can we use these templates for lessons learned during a failed project?
Yes, these templates work for any project outcome, including failures. Frame the document as a ‘post-mortem’ or ‘retrospective’ to emphasize learning over judgment. Highlight what was preserved (e.g., teamwork, budget discipline) alongside what didn’t, and focus recommendations on mitigating similar risks in future efforts. Avoid language that could be perceived as criticism of individuals, even in retrospect.
Comments
Join the conversation
Sign in to share your thoughts and leave a comment on this resource.
