A lessons-learned session that surfaces the same findings project after project, the same scope issues, the same communication gaps, isn't capturing lessons. It's documenting, repeatedly, that nothing actually changed as a result of the last session. The session itself isn't the problem, what happens after it is.
A lessons-learned session that actually works isn't measured by how many findings it produces. It's measured by whether the same finding shows up again next time.
The same findings project after project mean nothing actually changed, not that lessons were captured
A recurring finding is a sign the session isn't producing real change, not a sign the team keeps discovering something new. Treat a repeat finding as the actual signal worth investigating.
Separate genuinely new findings from ones that have already been raised before
Lumping new and repeat findings together hides the pattern that matters most. Check each finding against past sessions, and call out repeats explicitly rather than treating every session as a blank slate.
In Stelaah, past project notes and action items stay on the record, making it possible to actually check whether a finding has come up before instead of relying on memory. See how projects works.
Ask directly why a known issue wasn't actually fixed after it was raised last time
A repeat finding deserves a different question than a new one, not "what happened" but "why didn't the fix from last time actually hold." That question gets at the real gap in follow-through.
Assign a real, specific owner to each action item, not the team in general
An action item owned by "the team" is effectively owned by nobody, and it's the action items with no real owner that tend to become next session's repeat finding. Assign a specific person to each one.
Check whether old action items were completed before adding new ones to the list
Starting each session with a fresh list, without checking whether the last session's items actually got done, guarantees the list only grows. Check completion first, every time, before adding anything new.
A simple checklist
If you do nothing else, do these five things:
- Check each finding against past sessions for repeats.
- Ask why a known issue wasn't actually fixed last time.
- Assign a specific individual owner to every action item.
- Check old action items before adding new ones.
- Treat a repeat finding as the real signal to investigate.
Do that, and a lessons-learned session actually breaks the pattern, instead of documenting the same finding project after project.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
