iterate-lessons-log

A lessons log entry documents organizational learnings after projects or incidents. You need to create one when you want to capture context, events, outcomes, and actionable recommendations to preserve organizational memory for future initiatives.

To create a structured postmortem or retrospective, use a template that records context, timeline, team, and applicability. This skill generates a structured entry with frontmatter fields like artifact, version, created, and status, plus sections for actionable recommendations.

Yes, you can use a single lessons log template across teams and initiatives. It applies organization-wide to centralize knowledge, capturing context and outcomes from various projects into one searchable entry for continuous improvement and onboarding.

The best way to capture organizational memory is to centralize knowledge in a structured lessons log entry. This records what happened, what was learned, and recommended follow-ups, creating a reusable template that aids audits and future work.

Yes, this lessons log approach works for both project retrospectives and incident postmortems. It captures context, events, and outcomes after significant learning moments, applying across teams to document actionable recommendations regardless of the initiating event.