There is a thank you in the meeting, perhaps a message recognising everyone’s contribution. Then attention moves to what comes next.
It would feel odd to insist that every success needs a lengthy review. Recognition deserves its own space, and people do not need another meeting simply because something worked.
There may, however, be something worth understanding before the details fade. If the team wanted to create a similar experience again, would people agree on what made it possible?
Imagine a project that involved an unusually smooth relationship between a client team and a delivery team.
The account lead believes the difference was a clear brief. The delivery manager points to having the right people involved early. A team member remembers being able to question an assumption before the plan was finalised. Someone else noticed that the client responded quickly when decisions were needed.
Each explanation may identify something useful. None necessarily captures the whole experience.
If the account lead’s account becomes the accepted explanation, the next project may begin with a more detailed brief while overlooking the early involvement and quick access to decisions that helped people use it.
This is how a team can repeat a visible feature of success without recreating the conditions that supported it.
Listening to different accounts helps build a fuller picture. It also makes room for contributions that are less likely to appear in a final presentation, such as the colleague who noticed a misunderstanding before it became expensive or the person who made it easier for others to ask for help.
Broad descriptions can make success difficult to learn from.
“We communicated well” sounds positive, but another team member may not know what to do with it. Did people share information earlier? Were questions answered without several rounds of checking? Was there a point where a short conversation prevented two people from pursuing different approaches?
The more specific the explanation becomes, the easier it is to consider using it again.
In the project example, “having the right people involved early” might mean that the people responsible for delivery joined a discussion before a client commitment was made. They were able to explain a constraint while there was still time to adjust the scope. The team could then commit with a clearer understanding of what the work required.
That account gives the team something it can deliberately preserve. It also helps explain why an apparently small change made a difference.
The conversation can remain appreciative. Asking how something worked is one way to give proper attention to the judgement and cooperation behind a good result.
A good result is useful evidence, but it cannot tell the team everything about the approach that produced it.
Circumstances matter. The client may have had fewer competing demands. An experienced colleague may have been available at a particularly useful stage. The work may have been more familiar than the next project will be.
Recognising these conditions helps the team understand where its learning is likely to apply.
For example, early involvement may be valuable across many projects. The exact meeting schedule used on this one may only suit work of a similar size. A team can preserve the principle while adapting the arrangement.
There is also room to acknowledge that something went well despite a decision that could have caused difficulty. An unclear instruction might have been spotted quickly by chance. Examining that moment need not diminish the achievement. It helps the team avoid treating every part of a successful project as equally worth repeating.
The aim is to understand the result well enough to make useful choices next time.
Choose a recent piece of work that people feel good about. It can be an ordinary week that ran smoothly, a difficult conversation handled well or a handover that gave the next person what they needed.
Three questions can open up the discussion:
People may find it easier to form their own account before hearing the leader’s explanation. A brief pause to think, or a written response beforehand, can help keep the conversation from settling too quickly around the first confident answer.
Finish by choosing something specific to carry into the next relevant piece of work. If the early conversation made the difference, agree who needs to be included and when. Return to it afterwards to see whether the explanation held up in the new situation.
This gives recognition a practical continuation. The team has a chance to make a valued experience more repeatable.
Teams often seek a clearer picture when something is difficult. There is also value in understanding the conditions behind good performance while they are still present.
A change in workload, membership or leadership can alter arrangements that people have come to rely on. Knowing which conditions help the team work well makes it easier to consider what needs protecting as circumstances change.
Amazing Team Performance helps teams examine their strengths alongside the areas that need attention. Its connected view of performance, emotional conditions and leadership offers a way to explore why work feels effective and where that experience may differ across the team.
A good result deserves recognition. Giving some attention to how it happened also helps the team protect the conditions behind it.