“We talked about this last month.” Someone says it halfway through a meeting. The issue is familiar, and so is the frustration. There was a conversation, an agreement and a reasonable expectation that things would improve. For a while, perhaps they did.

Now the team is back in the same discussion, wondering why a problem everyone recognises has proved so difficult to resolve.

It is tempting to conclude that people have forgotten what was agreed, failed to take ownership or slipped back into old habits. Any of those things might deserve attention. Before settling on that explanation, it is worth looking at what the team actually learned the first time around.

A team can agree on an action without reaching a shared understanding of the problem. It can also understand a problem quite well and still be working within conditions that make the agreed response difficult to sustain.

The first explanation can become the lasting one

Consider a team that repeatedly discovers important concerns late in a project. Each time, people agree that communication needs to improve. A reminder goes out asking everyone to flag risks earlier.

That seems sensible. Yet the next project follows a similar course.

Look more closely and several explanations may emerge. One colleague believed the concern was too uncertain to raise. Another had mentioned it but thought the lack of response meant it was unimportant. Someone else understood the risk only after a decision had already been made.

The phrase “poor communication” brought these experiences under one heading, but it did little to explain them. A reminder to communicate earlier gives each person the same instruction when the reasons for their behaviour are different.

Teams can spend considerable time acting on an explanation they have never properly examined. Once an issue has been described as a commitment problem, for example, later events may be read as further evidence of poor commitment. Information that points towards conflicting priorities or uncertainty about authority can receive less attention.

Returning to the evidence helps loosen that first interpretation. What happened, in what sequence, and what did people understand at the time?

A lesson has to survive an ordinary working week

Even a well-understood lesson can lose its influence when daily demands return.

A team agrees that people should raise concerns while options remain open. The following week, a project is already behind schedule and the conversation is focused on getting the decision through. A colleague begins to question an assumption, notices the time pressure and decides to leave it for now.

The earlier agreement still exists. So does the expectation that the team will keep moving.

This is a difficult situation for a leader as well as a team member. Delaying a decision carries consequences. Exploring every concern in depth is rarely possible. What matters is whether the team has worked out how to handle that tension in practice.

When should a concern pause the work? Who can make that call? How can someone raise uncertainty without having to arrive with a complete alternative?

If these questions remain unresolved, “speak up earlier” depends on individual confidence each time. The team has expressed an intention without making it easier to act on.

A useful review makes room for different accounts

When an issue returns, starting with “Why has this happened again?” can put people straight into explaining their own part. A more useful starting point may be to reconstruct one recent example together.

Ask people to describe what they could see at each stage. Include the information they had, the choices available to them and what they expected would happen next. Someone who appears unresponsive from one position may have been waiting for an answer that nobody knew was needed.

Differences between accounts are worth exploring. They can show where the team is relying on assumptions that have never been shared.

Keep the discussion specific enough to reach a decision. “We need to trust one another more” may express something important, but it leaves the team with considerable work to do. An agreement to surface unresolved concerns before the final decision, with a named person responsible for responding, gives everyone something they can recognise and use.

There may also be a constraint the team cannot remove itself. If priorities conflict across departments, a local reminder will have limited reach. Recognising that boundary allows the issue to be raised where the necessary decision can be made.

Look for evidence that the next experience is different

Learning becomes more useful when the team decides what it expects to notice next time.

If the aim is to hear concerns earlier, look for whether they are reaching the conversation while there is still room to respond. If the aim is clearer decisions, examine whether people understand what was decided and can act without repeatedly reopening it.

Agree when to return to the change. A brief review after the next relevant piece of work can reveal whether it helped, where it broke down or whether the original explanation needs revisiting.

An action can be completed without producing the intended effect. Checking that effect gives the team an opportunity to adjust before another month passes.

Seeing the wider pattern

Repeated problems can be difficult to interpret when each person holds a different piece of the experience. Amazing Team Performance gives teams a structured view of their performance, emotional conditions and leadership environment, creating a shared starting point for exploring what may be keeping a pattern in place.

The next time a familiar issue returns, it may be useful to ask: what would need to be different in the team’s everyday experience for this agreement to hold?

Explore Amazing Team Performance