How to Collaborate With Colleagues to Build Psychological Safety Together

Someone spots a risk in the project plan but decides not to say anything.

A colleague asks a basic question and immediately feels embarrassed.

A mistake gets hidden for two weeks because nobody wants to be blamed.

A quieter team member is talked over again.

The team says “this is a safe space” but the first person to challenge the plan gets shut down.

That is where psychological safety is either built or broken. Not in a values statement. Not in a one-off workshop. Not only in what the manager says at the start of a meeting.

Psychological safety is built in the everyday response patterns between colleagues. It grows when people ask questions without being shamed, admit mistakes without being punished, challenge ideas without attacking people and support each other when conversations become awkward.

Managers matter. A lot. But psychological safety is not something a manager creates alone while everyone else waits to receive it. Colleagues build it together through repeated small behaviours.

Quick answer: how do you collaborate with colleagues to build psychological safety together?

To collaborate with colleagues to build psychological safety together, focus on how the team responds to everyday moments of risk. Make it easier to ask questions, raise concerns, admit mistakes, challenge ideas, give feedback and include quieter voices. Agree simple “we will” behaviours as a team, practise better responses in meetings and repair things quickly when someone is dismissed, blamed or talked over.

Psychological safety does not mean being nice all the time. It does not mean avoiding conflict or lowering standards. It means people can speak up early enough for the team to learn, improve and protect the work.

The most practical way to build it is to change what happens after someone takes a small interpersonal risk.

Do they get listened to?

Do they get punished?

Do people get defensive?

Does the team stay curious?

That response is what teaches people whether it is safe to speak next time.

What psychological safety means in everyday collaboration

Psychological safety is often described as a shared belief that a team is safe for interpersonal risk-taking. In plain English, it means people believe they can do things like:

• Ask a question
• Admit they are unsure
• Say they have made a mistake
• Ask for help
• Challenge an assumption
• Raise a risk
• Offer a different view
• Give or receive feedback
• Say something is not working
• Point out behaviour that is excluding someone

These are small moments but they can feel risky.

A project manager might hesitate before saying the plan is unrealistic.

A new team member might worry that asking a basic question will make them look inexperienced.

A delivery lead might spot a dependency risk but hold back because the sponsor is already under pressure.

A team member might notice a colleague being interrupted but say nothing because they do not want to make the room uncomfortable.

Psychological safety is not about removing all discomfort. Useful work often involves challenge, tension and trade-offs. It is about making sure the discomfort is attached to learning and improvement, not fear, blame or humiliation.

A psychologically safer team is more likely to hear early warnings before they become failures. It is more likely to learn from mistakes instead of hiding them. It is more likely to challenge weak assumptions before they become expensive decisions.

Why psychological safety is not just the manager’s job

Managers have a big influence on psychological safety. They set expectations, model behaviour, respond to bad news and decide what gets rewarded or punished.

If a manager reacts badly to challenge, people will learn to stay quiet.

If a manager blames people for mistakes, problems will go underground.

If a manager talks about openness but rewards only polished certainty, people will hide uncertainty.

So yes, managers matter.

But colleagues also shape the climate every day.

Think about what happens when someone raises a concern in a team meeting. The manager’s response matters but so does everyone else’s.

Do colleagues roll their eyes?

Do they interrupt?

Do they jump in to defend the plan?

Do they help explore the risk?

Do they thank the person for raising it?

Do they stay silent when someone is dismissed?

The team learns from all of these signals.

Psychological safety is not something a manager “does to” a team. It is co-created through repeated interaction.

That is good news because it means everyone has some influence. You may not control the culture but you can still change the next response, the next meeting and the next awkward moment.

Trust, inclusion, feedback and speaking up

Psychological safety is related to trust but it is not exactly the same thing.

Trust is often about whether I believe another person is reliable, capable and well-intentioned.

Psychological safety is more about the team climate. It asks: what happens here when someone takes a risk by speaking up?

A team can have friendly relationships and still be poor at speaking up. People may like each other but avoid hard conversations. They may trust someone socially but still worry about looking foolish in front of the group.

Psychological safety is also closely linked to inclusion.

If certain voices are always interrupted, ignored or treated as less credible, the team is not psychologically safe for everyone. A team can feel comfortable for the loudest or most established members while newer, quieter or under-represented colleagues experience it very differently.

Feedback matters too. Teams build safety when feedback is specific, fair and focused on the work. They damage safety when feedback is vague, personal, sarcastic or saved up until something has already gone badly wrong.

Speaking up is the visible behaviour but it is not the starting point. People speak up when repeated experience tells them it is worth the risk.

If the team wants more voice, it needs to improve the response.

The colleague-to-colleague behaviours that build psychological safety

Psychological safety is built through small behaviours that tell people, “It is safe enough to contribute honestly here.”

Ask questions without shaming

Questions are one of the simplest ways teams learn.

But questions can also be used badly. A question can open a conversation or make someone feel exposed.

Helpful colleague behaviour sounds like:

“Good question. I was wondering something similar.”

“Let’s slow down and make sure we all understand the assumption.”

“Can we explain that without acronyms so everyone is following?”

This matters because people watch how basic questions are treated. If one person is made to feel stupid, others stop asking.

Respond well to mistakes

Mistakes are moments of truth.

A psychologically safer team does not pretend mistakes are fine or consequence-free. It looks at what happened, what the impact is and what needs to change.

Helpful response:

“Thanks for flagging it early. Let’s understand the impact and work out the next step.”

Unhelpful response:

“How did you let that happen?”

The first response protects learning and accountability. The second response teaches people to hide problems for longer.

Challenge ideas rather than people

Challenge is healthy when it improves the work.

The difference is in the target.

Helpful challenge:

“I agree with the goal but I’m not convinced by that assumption.”

Damaging challenge:

“You clearly haven’t thought this through.”

The first challenges the idea. The second attacks the person.

Invite quieter voices in

Psychological safety is not just about letting people speak if they push hard enough.

It is also about noticing who has not had space.

You can say:

“We’ve heard a few views. What are others seeing?”

Or:

“I’d like to pause before we move on. Is there anything we have missed from people who have not spoken yet?”

This is especially important in hybrid meetings where quieter colleagues can disappear behind the agenda.

Share risks early

Project and delivery teams rely on early warning signs, especially when competing priorities and trade-offs are already in play.

A team builds safety when colleagues share risks before they become failures. That includes saying:

• “I may miss this date.”
• “I need help.”
• “This dependency is not as clear as I thought.”
• “The plan may still work but the risk has increased.”

When colleagues respond constructively, early risk-sharing becomes normal.

Give useful feedback

Good peer feedback is specific, timely and focused on the work.

Instead of:

“That update was confusing.”

Try:

“Can I offer an observation? I think the key message got lost because there were three different asks in the update.”

Useful feedback helps people improve without making them feel attacked.

Follow through on commitments

Psychological safety is not only about speaking. It is also about reliability.

If colleagues keep making commitments and not following through, the team becomes guarded. People stop relying on each other and start building workarounds.

Following through builds trust. Naming problems early when you cannot follow through also builds trust.

Notice exclusion or incivility

Small acts of exclusion damage safety quickly.

Examples include:

• Talking over someone
• Repeating someone’s idea only when a senior person says it
• Ignoring a remote colleague
• Mocking a basic question
• Letting sarcasm become normal
• Staying silent when someone is repeatedly dismissed

Colleagues do not need to turn every moment into a confrontation. But they do need to notice patterns and support better behaviour.

Support colleagues who raise concerns

It takes effort to raise a concern in a room where people may become defensive.

Support can be simple:

“I think that concern is worth exploring.”

“Can we stay with that point for a moment?”

“I heard a risk being raised there. What do we need to do with it?”

This shows the person they are not alone and shows the team that concerns are part of the work.

The behaviours that damage psychological safety

Some behaviours weaken safety even when nobody intends harm.

Ridicule

Laughing at a question, mocking an idea or making someone the joke teaches the team to stay guarded.

Even light ridicule can land badly if there is a power difference.

Sarcasm

Sarcasm can feel harmless to the person using it but sharp to the person receiving it.

If sarcasm becomes the normal response to mistakes, questions or concerns, people will stop offering anything that feels unfinished.

Gossip

Gossip creates uncertainty about what is being said outside the room.

If people raise concerns privately but not directly, trust falls. If colleagues hear others being criticised behind their backs, they assume the same may happen to them.

Dismissing questions

Comments like “we covered this already” or “that should be obvious” damage learning.

They may save a few seconds in the meeting but they cost much more later when people stop asking.

Punishing mistakes

Punishment does not always mean formal discipline.

It can be eye-rolling, blame, public embarrassment, withdrawal of trust or sarcastic comments.

If mistakes are punished, they will be hidden.

Talking over people

Interrupting sends a clear signal about whose contribution matters.

If the same people are talked over repeatedly, psychological safety becomes uneven.

Side conversations

Side conversations can make the formal meeting feel pointless.

They also make people wonder where the real conversation is happening and whether it is safe to be honest in the room.

Fake positivity

Fake positivity sounds supportive but avoids the truth.

Examples include:

• “I’m sure it’ll be fine.”
• “Let’s stay positive.”
• “We don’t need to focus on problems.”
• “That sounds a bit negative.”

This stops people naming risks early.

Ignoring microaggressions

Small dismissive comments, assumptions or repeated exclusions can have a large effect over time.

If nobody responds, the team learns that inclusion is optional.

Saying “safe space” without changing behaviour

Calling a meeting a safe space does not make it safe.

What matters is how people respond when someone actually says something difficult.

A practical 6-step process for building psychological safety together

You do not need to launch a major culture programme to start building psychological safety.

Begin with the moments that already happen in your team.

Step 1: Name the everyday moments where safety is won or lost

Start by identifying the team moments where people take small risks.

For example:

• Asking a basic question
• Admitting a mistake
• Saying a deadline may slip
• Challenging a senior person’s assumption
• Giving peer feedback
• Raising a concern about workload
• Pointing out exclusion or poor behaviour
• Saying “I do not understand”
• Saying “I disagree”

Then ask:

“What usually happens in our team when someone does this?”

That question is often more useful than asking whether the team “has psychological safety”.

You are looking for patterns.

Do people respond with curiosity or judgement?

Do people thank the person or move past it quickly?

Do people ask for more detail or become defensive?

Do quieter colleagues join in or withdraw?

Step 2: Agree “we will” behaviours as a team

A team agreement works best when it uses observable behaviours.

Avoid vague statements like:

• “We will be respectful.”
• “We will be open.”
• “We will collaborate better.”

Those are fine intentions but they are hard to use in the moment.

Try “we will” behaviours like:

• We will ask clarifying questions before criticising.
• We will raise risks early.
• We will challenge ideas without attacking people.
• We will thank people for surfacing bad news.
• We will not talk over colleagues.
• We will check who has not spoken before closing a decision.
• We will name missed commitments early.
• We will support colleagues who raise difficult issues.

Keep the list short. Five behaviours people actually use are better than twenty nobody remembers.

Step 3: Make it easier to ask questions and raise risks

Many people stay quiet because they do not want to look difficult, negative or uninformed.

You can reduce that risk by making questions and risks part of the normal rhythm.

In meetings, ask:

“What questions do we need to ask before this becomes a problem?”

“What could we be missing?”

“Where are we least confident?”

“What would make this plan fail?”

“Which dependency feels most fragile?”

If you are a colleague rather than the meeting chair, you can still help:

“Before we move on, can we check whether there are any questions or risks we have not surfaced?”

That simple prompt can change the room.

Step 4: Practise better responses to mistakes and challenge

The response matters more than the slogan.

When someone admits a mistake, the first response should reduce defensiveness and move the team into learning.

Try:

“Thanks for raising it early. What is the impact and what help do you need?”

When someone challenges an idea, try:

“Let’s test that. What assumption are you concerned about?”

When someone asks a basic question, try:

“I’m glad you asked. Let’s make sure we are all clear.”

This does not remove accountability. It makes accountability useful.

The team can still ask what happened, what changed and what needs to be done differently. The difference is that the conversation is about learning and repair rather than blame.

Step 5: Use meetings to include quieter voices and surface dissent

Meetings are where psychological safety becomes visible.

If the same few voices dominate every meeting, the team may be missing important information.

Practical meeting habits include:

• Ask people to write concerns first before open discussion.
• Invite input by role or perspective, not personality.
• Use a quick round where each person names one risk.
• Pause before closing a decision.
• Ask remote colleagues first sometimes.
• Check whether anyone disagrees but has not said so yet.
• Separate idea generation from decision-making.

You might say:

“We have heard from the people closest to delivery. Can we hear from those closest to the customer impact?”

Or:

“Before we agree this, I want to hear one concern or condition from each person.”

This makes dissent part of the process, not an act of bravery.

Step 6: Review and repair when the team slips

No team gets this right all the time.

Someone will interrupt. Someone will react defensively. A mistake will be handled badly. A quieter colleague will be missed. A concern will be brushed aside.

The important thing is repair.

A team can say:

“We moved past that concern too quickly. Can we go back to it?”

Or:

“I interrupted you earlier. Sorry. I’d like to hear the rest of your point.”

Or:

“We said we wanted earlier risk-sharing but I think our response just made that harder. Can we reset?”

Repair is powerful because it shows the team does not need to be perfect to be safe. It just needs to notice, adjust and keep learning.

Scripts colleagues can use

Use these as starting points and adapt them to your own voice.

Asking a basic question

“I may be missing something. Can someone walk me through the goal here?”

“Can we pause on that point? I want to make sure I understand the assumption before we move on.”

“This might be obvious to others but I think it would help to clarify it.”

Admitting a mistake early

“I’ve made an error on this piece. Here’s what I know, here’s the impact and here’s what I need help with.”

“I want to flag this now rather than wait. I think I may have misunderstood the requirement.”

“This is not where it needs to be yet. Can I talk through the gap and the options?”

Challenging an idea respectfully

“I support the goal. I’m not yet convinced by the assumption behind this option.”

“Can we test this from the customer’s point of view?”

“I might be wrong but I think there is a risk we have not fully explored.”

“Could we separate the idea from the person for a moment and look at the trade-off?”

Inviting quieter voices in

“We have heard a few views. What are others seeing?”

“I’m conscious we have not heard from everyone yet.”

“Before we close this, is there anyone who has a concern we have not surfaced?”

“Can we hear from the people closest to the day-to-day impact?”

Responding when someone raises a concern

“Thank you for raising it. Let’s stay with the concern before we defend the plan.”

“That sounds important. What would help us understand the risk better?”

“Can we separate what we know from what we are assuming?”

“I appreciate you saying that. It gives us a chance to fix it earlier.”

Giving peer feedback

“Can I share an observation about the work?”

“I think there is a stronger version of this if we make the ask clearer.”

“The content is useful. The part I think may confuse people is…”

“Would feedback be useful now or would you prefer to discuss it later?”

Calling in unhelpful behaviour

Calling in is often better than calling out when the aim is to reset the behaviour without escalating the room.

“Can we pause? I think we may be talking over the point.”

“I do not think that question has been answered yet.”

“Can we keep this focused on the issue rather than the person?”

“I’m not sure that landed as intended. Can we rephrase it?”

Offering support after an awkward moment

“I noticed that was a difficult exchange. Are you OK?”

“Would you like support raising that again?”

“I thought your point was worth exploring. I’m happy to back you up if you want to bring it back.”

“Do you want advice or would it help more if I just listened?”

Practical team rituals that help

Psychological safety becomes easier when it is built into routines.

A “we will” working agreement

Create a short team agreement using practical behaviours.

For example:

• We will raise risks early.
• We will ask before assuming.
• We will challenge ideas without attacking people.
• We will not punish questions.
• We will repair quickly when we get it wrong.

Use it in meetings. Review it in retrospectives. Keep it visible.

Meeting check-ins

A check-in does not need to be personal or time-consuming.

Try:

“What is one thing that could affect your contribution today?”

Or:

“Is there anything we need to know before we start?”

This helps people name pressure, blockers or context early.

Risk and dependency check

At the end of a project meeting, ask:

• What risk has increased?
• What dependency feels fragile?
• Who needs help?
• What should we flag now rather than later?

This makes early warning a team habit.

Challenge round

Before committing to a decision, ask each person to name one risk, question or condition.

This reduces the pressure on one person to be the challenger.

Mistake review without blame

When something goes wrong, ask:

• What happened?
• What did we expect to happen?
• Where did our process make this more likely?
• What did we learn?
• What will we change?
• Who needs support?

Avoid asking, “Who caused this?” as the first question.

Active bystander norm

Agree what colleagues can do when they notice exclusion, interruption or disrespect.

Options might include:

• Pause the conversation.
• Bring the discussion back to the person who was interrupted.
• Ask for the point to be rephrased.
• Check in privately afterwards.
• Escalate if the behaviour is serious or repeated.

Retrospective questions

Add one or two psychological safety questions to retrospectives:

• What made it easier to speak up this week?
• What made it harder?
• When did we respond well to a concern?
• Where did we become defensive?
• Whose voice did we miss?
• What will we do differently next time?

Common mistakes to avoid

Treating psychological safety as being nice

Being nice is not enough.

A team can be polite and still avoid every difficult issue.

Psychological safety means people can be candid with care. It includes respectful challenge, early risk-sharing and honest feedback.

Confusing safety with comfort

Psychological safety does not mean everyone feels comfortable all the time.

Sometimes the safest team is the one that can have an uncomfortable conversation without turning it into blame.

Removing accountability

Psychological safety does not mean low standards.

It should make accountability easier because people can raise problems earlier, ask for help sooner and discuss what needs to improve.

Forcing vulnerability

Do not pressure people to share personal stories, disclose emotions or open up before they are ready.

Forced openness can feel unsafe.

Start with working behaviours first: questions, risks, mistakes, feedback and follow-through.

Relying on a one-off workshop

A workshop may help start the conversation but it will not change the team on its own.

People decide whether the team is safe based on what happens afterwards.

Using “safe space” language without behavioural change

The phrase “safe space” can backfire if the room still punishes challenge.

It is better to agree specific behaviours and practise them.

Leaving inclusion and bystander behaviour out

Psychological safety is not evenly felt by everyone.

Junior colleagues, newer joiners, remote workers and people from under-represented groups may experience the same team very differently.

If the team ignores exclusion, interruption or microaggressions, safety will remain uneven.

Expecting junior colleagues to speak up without changing the response

Do not tell people to be brave if the room still punishes honesty.

Change the response first. Then speaking up becomes less risky.

Psychological safety together checklist

Use this with your team or before a meeting where honest contribution matters.

Everyday collaboration

• Can people ask basic questions without embarrassment?
• Do colleagues respond well when someone says “I don’t know”?
• Are mistakes raised early or hidden?
• Are risks surfaced before they become urgent?
• Do people challenge ideas without attacking the person?
• Do people thank colleagues for raising concerns?
• Do quieter voices get invited in?
• Do remote or part-time colleagues have equal space to contribute?

Meetings

• Do we ask for risks before closing decisions?
• Do we pause when one or two voices dominate?
• Do we separate facts from assumptions?
• Do we make it clear when challenge is wanted?
• Do we check who has not spoken?
• Do we agree actions and owners clearly?
• Do we review how the conversation went, not only what was decided?

Inclusion and respect

• Are people interrupted repeatedly?
• Are jokes, sarcasm or side comments making contribution harder?
• Are different working styles valued?
• Are microaggressions or dismissive comments challenged?
• Do colleagues support someone who raises a difficult issue?
• Do people know where to go if they do not feel safe speaking in the team?

Feedback and accountability

• Is feedback specific and focused on the work?
• Do we give feedback early enough to be useful?
• Do we hold each other to commitments without blame?
• Do people name blockers before deadlines slip?
• Do we repair awkward moments when they happen?

Repair

• Can we say “that did not land well”?
• Can someone apologise without making it dramatic?
• Do we return to concerns that were brushed aside?
• Do we change the behaviour after we discuss it?
• Do we review whether our team agreement is actually being used?

When to escalate or get outside help

Psychological safety is not a substitute for formal support where behaviour is serious.

You should seek help from HR, a senior sponsor, a trusted manager, a speak-up route, mediation or another formal route if the situation involves:

• Bullying
• Harassment
• Discrimination
• Retaliation
• Safeguarding concerns
• Misconduct
• Formal grievances
• Serious exclusion
• Repeated humiliation
• Abuse of power
• Behaviour that makes people feel unsafe

Colleague-to-colleague collaboration matters but it should not be used to handle issues that need proper organisational action.

If someone tells you they have experienced harmful behaviour, do not take over without asking what support they want. You can listen, validate, offer to support them and help them find the right route.

Final summary

Psychological safety is built together in the small moments of everyday work.

It is built when someone asks a question and is not made to feel foolish.

It is built when a mistake is raised early and the team responds with learning and action.

It is built when colleagues challenge ideas without attacking people.

It is built when quieter voices are invited in.

It is built when people notice exclusion, interruption or incivility and do something useful about it.

Managers have a strong influence but they are not the only people who shape the climate. Every colleague teaches the team what is safe by how they respond.

Start small. Agree a few “we will” behaviours. Practise better responses in meetings. Build early risk-sharing into the work. Review how the team handles challenge. Repair quickly when things go wrong.

Psychological safety is not created by saying “this is a safe space”. It is created when the team repeatedly proves that questions, concerns, mistakes and respectful challenge will be handled well.

If the next step is a difficult feedback conversation, the Feedback Conversation Pack can help you prepare clear wording before you go into the room.

References

1. Amy Edmondson’s research on psychological safety and learning behaviour in teams
2. CIPD evidence review on psychological safety and workplace trust
3. Google re:Work guide on team effectiveness and psychological safety
4. NHS England or NHS Employers guidance on safety culture, inclusion and speaking up
5. APM guidance on team charters and psychological safety in project teams

FAQs

Is psychological safety just another word for trust?

No. They are related but not identical. Trust is often about whether you believe another person is reliable and well-intentioned. Psychological safety is about whether the team feels safe enough to ask questions, admit mistakes, raise concerns and challenge ideas without fear of humiliation or punishment.

Does psychological safety mean avoiding conflict?

No. Psychological safety should make useful disagreement easier, not harder. It means people can challenge ideas, raise risks and discuss mistakes without the conversation becoming personal or punitive.

Can you have psychological safety and still hold people accountable?

Yes. In fact, psychological safety should support better accountability. People are more likely to raise problems early, ask for help, name blockers and learn from mistakes when they know the response will be fair and constructive.

What can colleagues do if the manager is not good at building psychological safety?

Colleagues can still influence the team climate by asking better questions, responding constructively to mistakes, inviting quieter voices in, giving useful feedback and supporting people who raise concerns. If the issue involves serious behaviour, exclusion or retaliation, use appropriate HR, speak-up or escalation routes.

How do you build psychological safety in a project team under time pressure?

Build it into delivery routines rather than treating it as extra work. Add quick risk checks, dependency reviews, challenge rounds and short retrospectives. Make it normal to say “I need help”, “this may slip” or “I think we are missing a risk”.

What should we do when someone raises a concern badly?

Try to separate the concern from the delivery. You might say, “I think there is an important issue underneath this. Can we reframe it so we can work with it?” That keeps accountability for tone while still making space for the risk or issue being raised.