A retro is a leadership decision before it is a feedback session.
Most leads I have watched treat the retro as a place to vent. They write the longest entry. They name the things that frustrated them. They post the screenshot of the missed deadline. The team reads this, and the team spends the first three days of the next sprint trying to fix what the lead was upset about, regardless of whether that thing matters.
The opposite move, the one I have settled into after a few years of doing it badly, is to write less than the team. Sometimes one line. Sometimes none. In a recent sprint retro I wrote a single sentence about myself under “What went well.” “We are slowly getting better at planning and respecting time.” Under “What could have been better” I wrote one more. “Discipline across updates such that we don’t have to backtrack.” Two lines total. The rest of the team filled paragraphs.
The diversity of what the team noticed told me how the team was shaped. One designer wrote about smaller tasks. One developer wrote about going back to commit logs to check dates. One engineer wrote about peer reviews and upskilling. Each person was pointing at a different part of the next sprint’s needed change. The lead’s job was to read the pattern and to act on it, not to compete for attention inside it.
The standup notes from the same week said something quieter. “Don’t want to work at 9pm at night, not cool.” “Better decision making and stick to one decision. Gave me nightmares while choosing between CRMs.” These are the lines a lead is supposed to find. The retro is the surface that surfaces them.
The honest limitation is that this only works when the team trusts the lead has their own forum to raise frustrations. If the retro is the lead’s only outlet, writing less is suppression, not leadership.
The shift is to stop using the retro to lead the conversation and start using it to read the team. The shorter the lead’s entry, the more room the team has to lead itself.