A retrospective template you can actually use
Run improvement with Keep / Problem / Try. Save it in Memol to revisit past retros and last time's Try in seconds.
Retrospective
Retrospective Info
- Period:
- Participants:
- Facilitator:
Keep
Things the team should continue doing
- What went well
- Successful initiatives
- Positive team behaviors
Problem
Issues and obstacles to resolve
- Problems and their impact
- Inefficient processes
- Communication challenges
Try
Concrete improvement actions
- Action item 1 (Owner: ___ / Due: ___)
- Action item 2 (Owner: ___ / Due: ___)
- Action item 3 (Owner: ___ / Due: ___)
Review of Previous Try
- Previous action 1 โ Result:
- Previous action 2 โ Result:
Filled-in example
Here's what it looks like filled in. Copy it and adapt it for yourself.
Retro: June Sprint 1
Retrospective Info
- โขDate: 2026/06/05
- โขScope: Sprint 1
- โขAttendees: 3 engineers
Keep
- โขShipped AI Format on schedule
- โขDaily sync worked well
Problem
- โขToo much idle time waiting on reviews
- โขSearch work kept slipping
Try
- โขRotate review duty
- โขMake search top priority next sprint
Review of Previous Try
- โขThursday design review โ stuck; keep it
3 tips for writing it well
Blame the system, not people
Not "who's at fault" but "what makes this likely." Safety is a precondition for improvement.
Limit Try to 1โ2 items
Trying everything changes nothing. Pick what you can actually do by next time.
Always review the previous Try
The best way to avoid set-and-forget. In Memol last time's retro is one search away.
Why Memol
Just ask AI for your notes
Ask "where was that again?" and Memol searches every note and answers. No digging through folders.
Shared with your team instantly
Teammates see it the moment you write it โ no more "hey, what happened with that?" back-and-forth.
Never start from scratch
Open this template and fill it in. Type "/" to drop in tables and headings in a second.