A retrospective is only useful if something changes
We had a good discussion. So why are we making the same mistakes?
By: Swathi Vallabhaneni - Black Dog Consultants
Most retrospectives start with good intentions.
We gather the team.
We ask what went well.
We ask what didn’t.
Someone writes notes. Someone nods. Someone says, ‘Good discussion.’
Then everyone goes back to work and does exactly what they did last time.
Which raises an awkward little question.
What was the point?
When I look closely, the problem often points back to one uncomfortable place: me.
Maybe I didn’t take enough ownership.
Maybe the action was too vague to repeat.
Maybe I had already moved on to the next urgent thing, dragging my lessons behind me like a forgotten suitcase.
A retrospective is not extra admin. It is how work gets smarter.
Without it, you can stay busy for years and still keep tripping over the same chair.
Reflection is not the finish line. Behaviour is.
A retrospective should not be treated like a box we tick after the work is done.
It is not meant to be a recap.
It is meant to create a better next round.
That means the same type of situation shows up again, and this time the way we respond is different. Not because we felt inspired in the meeting. Because we actually practised a new approach when it mattered.
If you reflect and then repeat the same mistakes, your retrospective is missing the most important step.
Using what you learned.
Why reflection gets stuck
Most retrospective conversations are too general.
Or we list too many ideas.
Or we assume motivation alone will carry the change.
Or we don’t make anyone responsible for trying it out.
The insight lands. Everyone agrees. Then nothing changes on the floor.
To avoid that, we need to treat retrospective notes as inputs for our next decisions, not souvenirs from a useful meeting.
Make your retrospective change-ready
Here are a few conditions that help reflection become action.
- Make the learning specific
‘Improve communication’ sounds good, but it is not actionable.
A better version is: ‘In the first 10 minutes of the stand-up, we confirm priorities and owners for the day.’
Specific is useful. Vague is where good intentions go to nap.
- Choose one behaviour to test
When you try to improve everything, you improve nothing.
Pick the smallest change that could create the biggest impact. Then test it immediately.
- Assign ownership and follow-through
If everyone owns it, no one owns it.
Decide who will try the change, and who will check whether it worked.
- Define success
Don’t stop at ‘it felt better.’
Look for observable outcomes. Less rework? Faster turnaround? Fewer misunderstandings? Fewer escalations?
Decide what success looks like before everyone leaves the room.
- Review it again, briefly
A retrospective without follow-up is just a thoughtful conversation that ends where the meeting ends.
Bring the agreement back into the next piece of work and ask:
Did we do what we said we’d do?
Dare to think differently. Then do differently.
A retrospective should end in a shift, not a sigh.
Because time spent reflecting should pay you back later. In fewer repeated mistakes. Cleaner handovers. Braver conversations. Work that does not keep stepping on the same rake.
So, the next time your team wraps a retrospective, ask one simple question before anyone escapes the room:
What will we change the next time this happens?
