The team retro that fixed nothing

Look at the action items from your last four retros. How many were completed? How many are the same items repeating, in slightly different words? If the answer is "most," the retro format is the problem.

Why most retros fail

• Action items get assigned without ownership or deadlines.
• Nobody reviews the previous retro at the start of the next one.
• The same systemic issues get listed every quarter because nobody has the authority to fix them.
• The retro is held to feel democratic, not to actually change things.

What works

Start every retro by reading the last one. Track action items between retros, not just at them. Limit each retro to two changes — focused beats comprehensive. And give the team permission to escalate the systemic issues, instead of pretending they're solvable inside the retro itself.

A retro that produces the same findings every quarter isn't a retro. It's a complaint ritual.