Celebrate Small Wins Out Loud

Ask a team what is wrong and the answers arrive quickly: the deadline, the handoff, the unclear owner. Ask what went right and you get a pause. That pause is not a lack of good work. It is a lack of practice at noticing it.

I see the same pattern in the sessions I run. The agenda is built around problems to solve, so the problems get the room’s first and best attention. The work that quietly went well since the last meeting never gets a turn, and the people who did it learn that nobody was watching.

There is a reason beyond mood. People repeat what gets noticed. If the only thing a team ever names aloud is the thing that broke, the lesson people take is to stay out of view. A small, regular habit of saying what worked changes what the room treats as worth saying, and it costs less than any recognition program I know of.

It is one question, asked at the start, with a short clock: “What is one thing that worked since we last met? It can be yours or someone else’s.” Each person answers in a sentence. Nobody is ranked, and nobody has to justify the answer.

My argument for it is simple. A session that opens by naming progress tells people their work is seen before anyone asks them to do more. That is my observation from facilitating, not a measured result, and I would rather say so than invent a statistic. There is related research behind the idea: Google’s guide on team effectiveness suggests giving specific positive feedback and publicly thanking people who help you (re:Work, accessed October 23, 2026).

Here is a hypothetical version for a team of about six. The times are a guide:

Notice what the facilitator does at the end: it names a pattern, not a person, and then moves on. The round is a doorway into the session, not a performance review.

The round only works if the answers are concrete. A vague answer is easy to give and easy to forget, and the room copies whatever the first person sets. That is why I go first and I go specific. I might say, “The agenda for today was shorter because two of you sent your updates in writing beforehand. That saved us twenty minutes.” Everyone then hears what a good answer sounds like.

A few hypothetical contrasts show the difference:

• Vague: “Good communication this week.” Specific: “Dana posted the schedule change in the channel before the meeting, so nobody showed up at the old time”
• Vague: “Great job on the launch.” Specific: “The launch checklist caught the missing approval before it went out”
• Vague: “Thanks, team.” Specific: “Sam stayed on the call after hours to walk the new hire through the system”

If someone gives a vague answer, do not correct it in front of the group. Ask one gentle follow-up, such as “What did that look like?” and the specifics usually arrive. If they do not, accept the answer and move on. The point is the habit, not the polish.

For a small group, speak it. Go around the room in a fixed order, allow a pass, and keep each answer to a sentence. In a small circle people can hear each other, and a spoken thanks lands harder than a typed one.

For a large group, write it. Ask people to type their answer into the chat or a shared document, wait about a minute, and then read three or four aloud, choosing different voices from the last session. Name the themes you see, such as “several of you mentioned handoffs.” If you want a third path, send people to pairs for 60 seconds and ask each pair to bring back one win.

A few practical notes apply to both. Say out loud that a pass is allowed, because a round that feels compulsory turns into a quiz. Choose a fixed order for the spoken version, so nobody has to wonder when their turn is coming. For the written version, open the document or chat before the session starts, so the first minute is not spent finding the right window. And keep time: a round that drifts to five minutes is no longer an opener, and the group will remember the drag more than the warmth.

Both versions fit into the opening described in how to open a virtual session, as the first act people take.

• Do not use the round to avoid a problem. If something went badly, name it later in the session, not instead of this round
• Vary who gets read aloud. If the same two voices get quoted session after session, the round tells everyone else their wins do not count
• Skip the round after a hard event, such as layoffs, when forced positivity will feel false
• Keep wins specific. “Good teamwork” gives the room nothing to build on, while “Priya covered the vendor call” does

This also fits with a retrospective, which too often becomes only a list of problems. The retrospective nobody acts on covers what to do with the problems. The what-worked round covers the part that gets left out.

Naming wins out loud is one of the small moves that make a room feel safe to speak in. Thanks for a specific contribution show people that contributing has an effect. I cover that and six other moves in how to build psychological safety in a virtual meeting.

At your next session, put the question on the first slide and give it ninety seconds. Notice who speaks first, what kind of win people name and how the room sounds afterward. Then decide whether it earns a place in your standard opening.

If it does, the second time is easier. People arrive already thinking of something to say, and a few start noticing wins during the week so they have an answer ready. That shift, from waiting to be noticed to noticing each other, is the part of the habit I care about most.

Want a second read on your opening?

Bring the first five minutes of your next session. In a free consult we plan an opening that makes people feel seen before the agenda starts.