Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why do our retros only list what went wrong?

You call it a retrospective, but look at what actually happens in the room. Someone lists what broke. The team nods, takes notes, feels the weight settle. Then someone mentions, briefly, that the release shipped on time — and the meeting moves on before anyone can stand on that ground for a moment. This is not honesty. Honesty would give equal weight to what held. What you are running is an audit of failure with a courtesy mention of success attached. The team leaves knowing exactly what they did wrong and having no clear picture of what they did right, or why it worked, or how to do it again. A person who only hears what is broken in them starts to believe they are only breakage. This is not sentiment. It is fact about how attention shapes belief. You do not need to lower your standards. You need to stop confusing scrutiny with truth.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The team needs a quick reframe of what a retrospective is for, but the real work is changing meeting behavior in real time.
How the two dials adapt to you →
What’s really going on

Because you built the meeting to hunt problems, so that is all it finds. A retrospective that spends ninety seconds on what worked and twenty minutes on what failed is not balanced — it is a trial. Change the ratio of attention, and you change what the team believes about itself.

🔒 What you’ll build togetherUnlock by starting
A moveOpen every retrospective by asking the team to name, out loud, one thing that worked and why it worked — not just that it worked.
A moveGive successes and failures equal time on the clock, by the minute, not by feeling. If failures get twenty minutes, successes get twenty minutes.
A moveWhen someone names a failure, ask what specific choice caused it — not to blame, but because vague failures teach nothing and specific ones do.
A moveWrite down what worked with the same detail you use for what broke. If it isn't written down, it will be forgotten by the next retro.
A moveClose every retrospective by naming one thing the team will keep doing exactly as they did it. Say it plainly: keep doing this.
PractiseThe Equal Ledger · a Pod of 5 · 30 min

What changes unlock by starting

  • Retrospectives take the same time but leave the team standing on firmer ground.
  • The team can name specific practices worth repeating, not just problems worth fixing.
  • Fewer people dread the meeting, because it stops feeling like a hearing.
  • You catch what's working before you accidentally cut it while chasing what's broken.

Related problems

The same struggle, seen by other coaches
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.