A colleague raises a concern in a meeting. They think the team may be committing to a deadline it cannot meet.

The leader thanks them, explains that the date has already been agreed and moves to the next item. Nothing openly hostile happens. Nobody criticises the person for asking.

Afterwards, the colleague is unsure whether their concern was understood. The rest of the team has also seen what happened, and people will draw their own conclusions about whether to raise a similar issue next time.

Encouraging people to speak up can be a useful beginning. The response they receive helps determine whether the invitation continues to feel worthwhile.

There is more to the response than the first few words.

Someone may hear “thank you for raising that” while also noticing an impatient expression, a quick defence of the original decision or a request to discuss it privately. Any one of these can have an innocent explanation. Repeated together, they can make it difficult to judge how welcome the contribution really is.

Colleagues also notice what happens later. Does the concern influence the work? Does the person get an explanation if the decision remains unchanged? Are they included in the next discussion, or does challenging an idea seem to make their involvement less convenient?

People may then become more selective. They wait until they have complete evidence, soften a concern until its significance is difficult to hear or share it with a trusted colleague after the meeting instead.

A leader can experience this as a lack of openness without seeing the earlier exchanges that made caution seem sensible.

Psychological safety concerns the interpersonal risks involved in contributing, including asking for help, admitting uncertainty or questioning an approach. A team member does not have to feel entirely comfortable to do these things. They do need some reason to believe that their contribution will be treated fairly.

That reason develops through experience.

Understanding a concern takes a little longer than answering it

Leaders often have information that others do not. They may know why a deadline is fixed, what has already been negotiated or which alternatives have been ruled out. Hearing a concern can therefore prompt an immediate explanation.

The explanation may be accurate and still arrive before the concern has been understood.

In the deadline example, the colleague might be asking whether the team can reduce the scope. They might have noticed that a dependency has changed. Or they may be trying to make visible a level of overtime that others have not seen.

A question such as “Which part of the work makes that date look difficult?” gives the team a better chance of hearing the actual issue. It also allows the leader to respond to something more specific than an apparent objection to the plan.

There will be times when the discussion needs to move on. Acknowledging what has been heard and agreeing how it will be examined helps keep time pressure from becoming an unexplained dismissal.

For example: “I can see that the testing window has become shorter. We need to check that before we confirm the scope. Let’s review it this afternoon and come back to the team tomorrow.”

The value lies in the response being accurate and followed through. A reassuring phrase loses its usefulness if people repeatedly hear it without anything happening afterwards.

The decision can stay the same and the response can still be useful

Taking a contribution seriously does not require agreeing with it. Teams need to be able to examine concerns, weigh competing needs and make decisions that some people would not have chosen.

What helps is making the reasoning visible.

If the deadline must remain, explain what that means for the work. Perhaps a lower-priority activity will move. Perhaps the risk needs to be accepted explicitly by someone with the authority to accept it. If a concern cannot be resolved, being clear about that is more useful than allowing the person to assume it has disappeared.

There is a similar responsibility when somebody points out an error. The team needs to understand its consequences and decide what accountability requires. It also needs enough information to learn. If the conversation quickly becomes an argument about a person’s competence, details that could help prevent a recurrence may become harder to discuss.

Honest examination includes both the person’s actions and the conditions in which those actions occurred.

A missed moment can be repaired

No leader or team responds perfectly every time. Fatigue, surprise or pressure can lead someone to answer more sharply than they intended.

Returning to that moment can matter. A leader might say: “I moved on too quickly when you raised the testing issue. I was focused on the deadline and didn’t ask enough about what you were seeing.”

Then comes the useful part: making time to hear it properly and explaining what will happen next.

Repair does not erase the first response. It gives the team another experience to learn from, including evidence that it is possible to recognise an unhelpful reaction and change course.

Responsibility also sits with colleagues. A concern can be dismissed through jokes, side comments or the way the group rushes to defend a familiar approach. Leaders can help the team notice these responses without making the person who spoke up responsible for correcting them.

Leaders may find it difficult to judge how the team’s responses are experienced. Their intentions are easier to see from the inside than the effect they have on others.

Amazing Team Performance helps teams explore the emotional and leadership conditions around their work. Bringing different experiences into a structured conversation can help reveal where speaking up feels useful, uncertain or unnecessarily risky.

A useful place to begin is with one recent contribution: what happened after it, and what might the team have learned from that response?

Explore Amazing Team Performance