We've all been there: the Tuesday afternoon retrospective. You open the board, and there they are—the same three columns: What went well?, What didn't go well?, Action items?
By the third sprint, the team starts giving "safe" answers. "Communication was good." "The deployment was a bit slow." "Let's try to communicate more." This isn't a retrospective; it's a zombie walk. You're ticking a box, not improving the process.
In 2026, with teams spread across timezones and cultures, you need to break the pattern to get to the truth.
The "Sailboat" (Visual/Metaphorical)
Instead of just words, use a metaphor. Draw a sailboat on your Miro or Mural board.
- The Wind: What’s pushing us forward? (Our strengths)
- The Anchor: What’s slowing us down? (Our blockers)
- The Rocks: What risks are ahead of us? (The "Red Line" dependencies)
- The Sun: What are we excited about? (The wins)
This shifts the team’s brain from "compliance mode" to "problem-solving mode." It’s much easier to point to an "anchor" than it is to call out a colleague’s slow PR review process.
The "4Ls" (Deep Dive)
If you need a more structured approach, the 4Ls are my go-to for deeper reflection:
- Loved: What did you genuinely enjoy this sprint?
- Learned: What new skills or knowledge did we gain?
- Lacked: What did the team need that wasn't there?
- Longed for: What do we wish we had for the next sprint?
"Longed for" is a powerful question. It’s where your best tool automation ideas and process changes usually hide.
The "Async Retro" (For Distributed Teams)
In 2026, the "Live Hour" is expensive and hard to schedule across 10 timezones. We now use Async Retros. We open a dedicated Slack canvas or FigJam on Wednesday, and the team adds their thoughts throughout their workday. On Friday, we have a short 20-minute "Sync" to vote on the top 2 action items. This gives introverts more time to think and ensures the "loudest" person doesn't dominate the meeting.
Real Example: The "Blunt Tool" Failure
I once tried to run a "Start, Stop, Continue" after a particularly brutal release. The team was too raw. The "Stop" column was just a list of complaints about other departments. I pivoted to the "Hero's Journey" format, where we mapped the release as a story. It allowed the team to see the "Monsters" (external factors) separately from the "Mentors" (internal support), turning a blame-game into a shared narrative of survival and growth.
Takeaways
- Change your retrospective format every 2-3 sprints to avoid "pattern fatigue."
- Use metaphors like the Sailboat to lower the barrier for honest feedback.
- Use the 4Ls to capture more than just "pros and cons."
- Try Async Retros to respect deep work and different timezones.
- Focus on just 1-2 high-impact action items—don't try to fix everything at once.
Resources
- Miro: 10 Retrospective Templates
- Echometer: 54 Fun Retrospective Ideas
- TeamRetro: Best Practices for Remote Teams
Modern Project Management for Distributed Teams
PM Squared shares practical tools, templates, and lessons for PMs navigating remote work in 2026.
Browse Resources →