See anything of yourself here?
A snapshot of Internet forums this month – such as LinkedIn, Reddit, and X – surfaces several frustrations with retrospectives / debriefs:
- Practitioners and team members venting that retros and debriefs are performative rituals (“therapy with sticky notes”, “lessons documented, not lessons learned”) where the real problems are whispered in private DMs because speaking up in the room is politically dangerous – and even when issues are raised, action items die in the backlog?
- Team leads, Scrum Masters, Engineering Managers, and Incident/Ops Commanders frustrated by silence on Zoom calls, tired of playing “therapist” or spending hours synthesizing messy notes into reports, and embarrassed when the exact same failure happens two sprints or two quarters later.
- Pragmatists who hate “Agile theater” and performative meetings. You want your team to respect your leadership, and nothing erodes your credibility faster than running a meeting everyone secretly considers a waste of time.
- The astute – “Problem-aware moving into Solution-aware”. Why: They explicitly call out that people stop speaking up “because why they should bother if nothing changes anyway”, and mock postmortem slides “full of action items nobody follows up on six months later”.

A solution for your consideration
Break the cynicism loop where unshipped action items kill future team honesty. Consider turning a dead ritual into a closed-loop review that forces prioritization and follow-through. Trial Candid Cycle Starter.


