Create Comprehensive Lessons Learned Templates

This skill creates comprehensive lessons-learned documentation templates for organizational learning and continuous improvement. Every document is built from eight essential components: an executive summary, project context (background, scope, timeline, stakeholders), what went well, what didn't go well, root cause analysis, actionable recommendations, knowledge artifacts produced, and stakeholder impact. It provides two full templates: a standard project template (with tables for successes and their replication strategy, challenges and their prevention strategy, root-cause breakdowns per challenge, and prioritized recommendations with owner/timeline/success metric) and an incident-response template (incident summary, a timeline-of-events table, what worked versus what failed across detection/communication/response/recovery, and immediate/short-term/long-term action items).

Best-practice guidance covers data-driven insights (quantifying impact in time/cost/quality, before-and-after comparisons, specific dates and versions, supporting evidence), actionable recommendations (SMART criteria, clear ownership, impact/effort prioritization, links to existing processes), and a balanced perspective (both positive and negative learnings, blame-free system-focused framing, multiple stakeholder viewpoints, both technical and process aspects). Advanced template features add a risk-assessment matrix (likelihood, impact, current mitigation, recommended action) and a stakeholder-impact analysis split between internal teams (development, operations, business) and external parties (customers, vendors, partners).

Knowledge-management guidance covers tagging and classification (consistent taxonomy, searchable keywords, cross-referencing related projects, version control) and distribution (executive summaries for leadership, quick-reference guides for practitioners, integration with knowledge bases and wikis, scheduled review cycles). The collection process spans immediate capture during execution, structured retrospective sessions, individual role-specific interviews, and document/artifact review, with quality assurance through peer review, stakeholder validation, management approval, and follow-up tracking. Success is measured by adoption rate (recommendations implemented), knowledge retention (fewer repeat issues), process improvement (measurable efficiency or quality gains), and cultural impact (increased participation in learning activities).

Use this skill when documenting lessons from a completed project or resolved incident and you need a structured template that captures both successes and failures, root causes, and actionable, owned recommendations rather than an unstructured retrospective writeup.

It is not a fit for real-time incident response itself - the incident template is explicitly a post-incident lessons-learned document, not a runbook for handling an incident as it happens.

Inputs are the project or incident's timeline, outcomes, and input from stakeholders across the teams involved. Outputs are a completed lessons-learned document (standard project or incident-response format) with quantified successes and challenges, root-cause analysis, SMART recommendations with owners and timelines, a risk-assessment matrix, and a stakeholder-impact breakdown, tagged and formatted for integration into a knowledge base.

Project managers, team leads, and incident responders who need to turn individual project or incident experience into institutional knowledge - with a repeatable collection process, quality-assurance review, and distribution plan - rather than a one-off retrospective document nobody revisits.