Lessons learned
A lessons learned template that captures what went well, what didn't, the root cause, and an owned action item after every project, sprint, or campaign.
About this template
A retrospective that only lives in a meeting disappears with the meeting. This template keeps the write-up as a searchable card, so the same weak spot doesn't quietly resurface three projects later.
Each entry is tagged to a project or source, so a board holding lessons from a dozen different sprints, campaigns, or launches stays searchable instead of turning into a pile of undated notes. From there, capture what went well, what didn't, how much it actually mattered, why, and one action item with an owner and deadline. The impact field matters more than it looks — not every miss deserves a root-cause pass, and rating impact is what keeps the team from spending a retro debating something trivial. Group entries by category (process, communication, tooling, planning) to see if the same root cause keeps showing up across different projects.
Works for a single sprint retro, a full project post-mortem, a campaign wrap-up, or an ops review alike — the fields scale down to a five-minute fill-in or up to a full team discussion, and teams already using a 4Ls format (liked/learned/lacked/longed for) can map straight onto the same fields.
What’s inside
Columns included
Task types
Custom fields
Key features
- Project / source tagging so lessons stay searchable across many teams and project types
- Structured what-went-well / what-didn't / why fields
- Impact rating to prioritize which misses actually deserve a root-cause pass
- Action item always tied to an owner and deadline
- Category tagging to catch recurring root causes
- Scales from a 5-minute sprint retro to a full project post-mortem
- Link action items directly to tasks so changes get scheduled
Who is this template for?
- Agile teams running sprint retrospectives
- Project managers closing out a project phase
- Marketing teams reviewing campaign performance
- Support teams documenting incident retros
- PMOs tracking recurring process gaps across projects
How to use this template
Use this board to turn a retro conversation into a record the next team can actually find and use.
Step 1
Tag the project or source first
Name the sprint, project, campaign, or launch this entry came from before anything else — a lesson with no source is unsearchable the moment it's not the most recent one.
Step 2
Capture what went well and what didn't
Be specific — name the actual process or decision, not a vague summary like "good teamwork" or "poor communication."
Step 3
Rate the impact, then ask why
Note how much this actually affected the outcome before digging into root cause — it's how you tell a real pattern from a one-off gripe worth skipping.
Step 4
Assign one action item with a deadline
A lesson without an owned next step is just a complaint. Give every entry one concrete change and a date.
Frequently asked questions
Related templates
After action review
An after action review template that captures what was planned, what actually happened, and why, right after an event, launch, or incident.
Risk register
A risk register template that scores likelihood and impact, assigns an owner to every risk, and keeps mitigation plans visible until they're closed.
Project charter
A project charter template that locks down scope, sponsor, budget, and success criteria before work starts, and tracks approval status for teams running several projects at once.