Psychological safety
Psychological safety training for teams
- Tailored after a scoping call
- In person or remote
- Teams and leaders
- Practical behaviours
In many teams, the smartest people in the room say nothing. They notice the flaw in the plan, the risk in the project or the customer problem nobody has mentioned, and they keep it to themselves. Not because they do not care, but because speaking up feels risky. They might look foolish, upset a senior colleague or be seen as negative. Multiply that silence across a team and an organisation, and mistakes go unreported, ideas go unshared and problems surface only when they are expensive.
Psychological safety is the shared belief that it is safe to take interpersonal risks in a team: to ask a question, admit a mistake, offer an idea or challenge a decision without fear of embarrassment or punishment. Collective Campus has been building team capability in Australia since 2015, and psychological safety sits underneath almost everything that work depends on. The training here is practical. It helps teams and leaders understand what psychological safety is and is not, see where they stand today and practise the specific behaviours that build it, while keeping standards high. It connects closely to workplace culture and high-performance teams.
Quick answer
Psychological safety training helps teams and leaders build an environment where people feel able to speak up, ask questions, admit mistakes and challenge ideas without fear. Good training explains the research, distinguishes safety from niceness or low standards, helps the team assess where it stands and gives leaders and members specific behaviours to practise, such as framing work as learning, inviting input and responding productively to bad news. Collective Campus tailors every program after a scoping call, with no fixed format, length or group size, and does not publish prices.
What psychological safety is
The term was popularised by Harvard Business School professor Amy Edmondson, whose research on teams found that the best-performing hospital teams reported more errors, not fewer. They were not making more mistakes. They were more willing to talk about them, which meant they could learn and improve. Edmondson's later work, and resources from The Fearless Organization, describe psychological safety as a climate in which people feel comfortable expressing and being themselves at work.
The idea gained wider attention when Google's Project Aristotle studied what made its teams effective. As described in Google's re:Work guide to team effectiveness, psychological safety stood out as the most important of the dynamics researchers identified, ahead of dependability, structure and clarity, meaning and impact.
Psychological safety is a property of a team, not of an individual. The same person can feel safe in one team and unsafe in another. It is built or eroded through everyday interactions: how a leader responds to a question, what happens when someone admits an error, whether dissent is welcomed or punished.
What psychological safety is not
Psychological safety is widely misunderstood, and the misunderstandings often make teams worse rather than better.
- It is not niceness. Teams that avoid hard conversations to keep the peace often have low psychological safety. People are polite in the room and frustrated outside it. Real safety makes it possible to disagree openly.
- It is not low standards. The most productive teams combine high psychological safety with high standards and accountability. Safety without standards produces comfort. Standards without safety produces anxiety. Both together produce learning and performance.
- It is not protection from consequences. People are still accountable for their work. What changes is that they can raise problems early, before they become failures.
- It is not the same as trust. Trust is between two people. Psychological safety is a shared belief across a team.
- It is not a perk. It is not about free lunches or wellness days. It is about how work is discussed and decided.
- It is not something a leader can declare. Telling people "it is safe to speak up" does little. People judge safety by what happens when someone actually does.
The comfort, anxiety, apathy and learning zones
A simple way to understand the relationship between safety and standards uses four zones.
- Apathy zone: low safety and low standards. People disengage and do the minimum.
- Comfort zone: high safety and low standards. People enjoy working together but are not stretched.
- Anxiety zone: low safety and high standards. People work hard but hide problems and avoid risks.
- Learning zone: high safety and high standards. People take on hard goals, raise problems early and learn quickly.
Most teams that ask for psychological safety training are in the anxiety zone. The goal is not to lower standards to make people comfortable. It is to raise safety so that high standards become achievable.
Why psychological safety matters in Australia now
Beyond performance, there is a legal dimension in Australia. Under the model work health and safety laws, a person conducting a business or undertaking must manage risks from psychosocial hazards, which include poor support, lack of role clarity, poor organisational change management, poor organisational justice, bullying, harassment and conflict or poor workplace relationships.
Psychological safety and psychosocial safety are related but not identical. Psychosocial safety is about preventing psychological harm from work. Psychological safety is about whether people feel able to speak up and take interpersonal risks. A team with high psychological safety is more likely to raise psychosocial risks early, which helps organisations meet their duties. Training that builds psychological safety can therefore support, though not replace, an organisation's psychosocial risk management.
What the training covers
Every program is tailored after a scoping call. Most draw on these building blocks.
The evidence. Teams explore the research behind psychological safety, including Edmondson's work and Google's Project Aristotle, and why it drives learning and performance.
Safety and standards. Teams learn the difference between safety and niceness, and why the learning zone requires both high safety and high standards.
Diagnosing the team. Teams assess where they stand using structured questions, often anonymously, and discuss the results honestly. This usually reveals differences between how leaders and team members experience the team.
The leader's role. Leaders learn three core moves from Edmondson's framework: setting the stage by framing work as learning and clarifying why voice matters; inviting participation through humble, genuine questions; and responding productively by thanking people for raising issues, treating failure as information and acting on what is heard.
Speaking up skills. Team members practise raising concerns, disagreeing and admitting mistakes in ways that are clear and constructive.
Responding to bad news. Everyone practises responding to mistakes, dissent and bad news in ways that encourage more of it rather than less.
Team agreements. Teams agree specific practices, such as how meetings will run, how decisions will be challenged and how mistakes will be reviewed, and commit to reviewing them.
Rituals and routines. Teams design repeatable practices that build safety into everyday work, such as blameless reviews, pre-mortems and regular retrospectives.
Behaviours that build psychological safety
Psychological safety is built through small, repeated behaviours. Training focuses on making these concrete.
For leaders:
- Admitting their own mistakes and uncertainty openly.
- Asking genuine questions and listening to the answers.
- Inviting quieter people to contribute, without putting them on the spot.
- Thanking people for raising problems, especially bad news.
- Separating the person from the mistake when things go wrong.
- Explaining decisions and the reasoning behind them.
- Following through on what they hear, and showing what changed.
- Holding high standards while making it safe to fall short and learn.
For team members:
- Raising concerns early and specifically.
- Asking questions rather than assuming.
- Building on others' ideas before critiquing them.
- Disagreeing with ideas, not people.
- Owning their mistakes and sharing what they learned.
- Supporting colleagues who speak up.
Behaviours that erode psychological safety
Teams also learn to recognise the behaviours that quietly destroy safety, often without anyone intending it.
- Interrupting or dismissing contributions.
- Responding to bad news with frustration or blame.
- Asking for input after the decision has been made.
- Rewarding only good news in reporting.
- Public criticism or sarcasm.
- Leaders who always speak first and longest.
- Punishing people for mistakes made while trying something new.
- Ignoring concerns that were raised, so people conclude speaking up is pointless.
Psychological safety for leadership teams
Leadership teams often have the lowest psychological safety of all, because the stakes feel higher and executives compete for resources and influence. When senior leaders cannot disagree openly with each other, decisions get made outside the meeting, strategy stays vague and the organisation receives mixed signals. Working with the leadership team first often has the greatest effect, because their behaviour sets the tone for everyone below them. This connects to broader leadership development for teams.
Psychological safety in hybrid and remote teams
Remote and hybrid work creates particular challenges. It is harder to read reactions on a screen, easier for quieter people to disappear and easier for small misunderstandings to grow. Training for distributed teams covers practical techniques: structured turn-taking in online meetings, using chat and written input to widen participation, explicit check-ins, clear norms for cameras and responsiveness, and deliberate effort to include people who are not in the room.
Psychological safety and decision-making
Psychological safety improves decisions because it brings more information into the room. When people feel able to challenge assumptions, raise risks and offer alternatives, teams avoid groupthink and catch errors earlier. Practices such as pre-mortems, where the team imagines a project has failed and explains why, and nominated devil's advocates help structure that challenge. This links closely to critical thinking, since safe teams are better at testing ideas, including ideas produced by AI.
Psychological safety and innovation
Innovation depends on people offering half-formed ideas, running experiments that might fail and admitting when something is not working. Without psychological safety, people offer only safe ideas and hide failed experiments. Teams that want to innovate need safety first. That is why psychological safety is often included in innovation, design thinking and AI adoption programs, not just in culture or wellbeing work.
Psychological safety during change
Restructures, new technology, mergers and AI adoption all reduce psychological safety, because people feel uncertain about their roles and futures. At exactly the time organisations most need honest feedback about what is working, people are least likely to give it. Training during change helps leaders create space for concerns, explain what they know and do not know, and invite input on how change is implemented.
Where psychological safety training goes wrong
- Treating it as a wellbeing topic only. Safety becomes about comfort rather than performance and learning.
- Training team members but not leaders. People learn to speak up, then speak up to a leader who reacts badly.
- Lowering standards. Teams confuse safety with avoiding accountability.
- Running it as a one-off. Safety is built through repeated experiences, not a single session.
- Ignoring the evidence from the team. Generic content that does not address what is actually happening.
- Forcing vulnerability. Pressuring people to share personal stories can reduce safety rather than build it.
- No follow-through. If concerns raised in the session are ignored, people learn that speaking up does not matter.
Formats (shaped after a scoping call)
Every program is tailored after a scoping call, so there is no fixed length, headcount or package. What changes from one organisation to the next is the mix of the elements below, chosen to fit the outcome the team needs and the real constraints on its time.
- Focused workshop. A single facilitated session built around one live problem the team brings into the room. Best when the goal is a shared language, a quick diagnosis and a small number of agreed next steps.
- Workshop series. A sequence of shorter sessions spaced out so people apply each idea at work between sessions and bring back what happened. Best when the goal is behaviour change rather than awareness.
- Applied program. Training combined with a real piece of work: a service, process or team challenge the group moves forward while learning. Best when leaders want a visible result, not just a completion record.
- Leadership session plus team rollout. Leaders go first so they can model the behaviour and remove blockers, and then teams follow with sessions that reflect what leaders agreed.
- Coaching and follow-up. Check-ins, clinics or office hours after the formal sessions so teams get help when they hit the hard part of applying the method.
- In person, remote or hybrid. Delivered on site in Sydney, Melbourne, Brisbane and other Australian cities, or live online for distributed teams. Remote sessions are designed for remote work rather than a slide deck streamed over video.
The scoping call covers who is in the room, what is already in place, what success looks like in practical terms and what would get in the way. The design follows from those answers.
What teams leave with
- A precise, shared understanding of what psychological safety is and is not.
- An honest read on where the team sits today, on safety and on standards.
- Leadership behaviours for setting the stage, inviting participation and responding productively.
- Speaking up skills for raising concerns, disagreeing and admitting mistakes.
- A team agreement on how the team will discuss problems, decisions and mistakes.
- Rituals such as blameless reviews and pre-mortems built into the team's work.
- A plan to keep standards high while building safety.
- A review rhythm so the team can track progress over time.
How to tell whether it worked
Agree a few practical measures before the program starts, so success is judged on evidence rather than on how the session felt. Useful measures for this topic include:
- Team safety survey. Short, repeated questions on whether people feel able to speak up, ask for help and admit mistakes.
- Speaking up in meetings. Whether more people contribute and challenge ideas, observed in retrospectives.
- Early warning. Whether problems and risks are raised earlier, before they escalate.
- Error reporting. Whether mistakes and near misses are reported and reviewed more openly.
- Decision quality. Whether decisions are challenged and tested before they are made.
- Retention and wellbeing indicators. Unplanned turnover, leave and wellbeing data, interpreted carefully.
- Leader follow-through. Whether leaders act on concerns raised, as seen by their teams.
- Agreement reviews held. Whether the team reviews its agreements at the agreed rhythm.
Why capability building beats one-off training
Most training fails for a simple reason: people learn something in a room, return to a full inbox and an unchanged system, and within a few weeks behaviour drifts back to where it started. The research on learning transfer has said this for decades. What predicts whether learning sticks is less about the quality of the session and more about what happens around it: whether leaders expect and reinforce the new behaviour, whether people get to apply it immediately on real work, and whether the system they work in makes the new way easier rather than harder.
Collective Campus designs for transfer from the start. That means working on live problems rather than case studies from other companies, involving leaders so they can reinforce the change, building in practice and follow-up between sessions, and agreeing practical measures upfront. It also means being honest when training is not the answer. Sometimes the real blocker is a policy, an incentive or a system, and the most useful thing a scoping call can do is name it.
The difference shows up in what teams say afterwards. A one-off session produces "that was interesting." A capability building program produces "this is how we work now," along with the evidence of a changed process, a fixed journey or a decision made differently.
Comparing provider types
Psychological safety training comes from several kinds of provider. The comparison below describes provider types, not individual firms.
- Capability building provider such as Collective Campus. Typically strong at: Practical team and leader workshops linking safety to standards, decisions and real work. Watch out for: Requires leaders to take part and follow through. Best fit when: You want safety and performance to rise together in specific teams.
- Wellbeing or mental health provider. Typically strong at: Awareness of mental health and psychosocial risk. Watch out for: May focus on wellbeing rather than team performance and voice. Best fit when: Your priority is mental health awareness and support.
- Licensed assessment provider. Typically strong at: Structured team diagnostics using a specific survey tool. Watch out for: Diagnosis can outweigh practice of new behaviours. Best fit when: You want a formal measurement of team psychological safety.
- Improvisation or experiential trainer. Typically strong at: Playful practice of listening and building on ideas. Watch out for: Can be disconnected from real team issues and decisions. Best fit when: You want an engaging, energising session.
- Executive coach. Typically strong at: Individual leader behaviour. Watch out for: Limited reach to team norms and practices. Best fit when: One leader's behaviour is the main issue.
Decision checklist: choosing a provider
Use these questions when comparing providers. A strong provider will answer most of them clearly before any proposal is written.
- Does the training distinguish psychological safety from niceness and low standards?
- Will leaders take part, not just team members?
- How will the team assess where it stands today?
- Will people practise specific behaviours, not just discuss concepts?
- How will the session itself be made safe for honest conversation?
- Does the design connect to our psychosocial risk obligations?
- Will the team leave with written agreements and rituals?
- How will progress be reviewed and measured?
- Can it be delivered for hybrid or remote teams?
- Does the provider avoid forcing personal disclosure?
- Can the provider show relevant, real experience?
- Is the program tailored after a scoping call rather than sold off the shelf?
How Collective Campus scopes and runs a program
Collective Campus has been running capability building programs for teams in large organisations since 2015. The approach is the same whatever the topic.
- Scoping call. A conversation with the sponsor, and often with a few people from the team, about the outcome, the context and the constraints. Nothing is proposed before this call, because a generic proposal would be guessing.
- Discovery. Where it helps, short interviews or a brief survey with participants so the content reflects their real work and the language they use.
- Design. Content, exercises and examples are built around the team's own situations. Generic case studies are kept to a minimum; the team's live work is the main material.
- Delivery. Highly practical, facilitated sessions where most of the time is spent doing rather than listening. Participants leave with things they made, not just notes.
- Application. Agreed actions, owners and a simple way to check progress, so the work continues after the facilitators leave.
- Review. A debrief with the sponsor on what changed, what got stuck and what the team needs next.
Pricing, format and timing are all discussed after the scoping call, once both sides understand what the work actually involves.
Preparing for a program
A little preparation makes a large difference to the result.
- Name a sponsor. Someone senior enough to remove blockers and to ask about progress afterwards.
- Pick real work. Bring a live problem, journey, project or decision the team actually needs to move. Abstract exercises produce abstract results.
- Tell participants why. People engage more when they know why they are there and what will be different afterwards.
- Protect the time. Sessions interrupted by email and calls produce half the value. Agree that the time is protected.
- Plan the week after. Book the first follow-up action before the program starts, so momentum is not lost.
- Gather what already exists. Data, feedback, previous reviews and earlier attempts all help tailor the content.
Key terms
- Psychological safety: A shared belief in a team that it is safe to take interpersonal risks.
- Interpersonal risk: The risk of looking ignorant, incompetent, intrusive or negative in front of others.
- Learning zone: The state where a team has both high psychological safety and high standards.
- Anxiety zone: The state where standards are high but safety is low, so people hide problems.
- Project Aristotle: Google research into what makes teams effective, which highlighted psychological safety.
- Psychosocial hazard: A work-related factor that may cause psychological harm, which Australian employers must manage.
- Blameless review: A review of a mistake or incident that focuses on learning and systems rather than blame.
- Pre-mortem: A technique where a team imagines a project has failed and identifies why, before it starts.
- Voice: Employees speaking up with ideas, questions or concerns.
- Silence: Withholding ideas, questions or concerns because speaking feels risky.
- Framing: How a leader describes work, for example as uncertain and requiring learning.
- Productive response: Reacting to bad news or mistakes in a way that encourages more openness.
- Team agreement: A written set of commitments about how a team works together.
Practical tools teams use
Training introduces a set of simple tools that teams can use in everyday work.
Check-ins. A brief round at the start of a meeting where each person shares how they are arriving or what is on their mind. It signals that every voice matters and surfaces issues early.
Silent brainstorming. People write ideas individually before discussion, which stops the loudest or most senior voices shaping the conversation and brings out quieter perspectives.
Leader speaks last. In decisions and discussions, the most senior person holds back their view until others have spoken.
Pre-mortems. Before a project starts, the team imagines it has failed and lists the reasons. This makes it legitimate to raise risks that might otherwise feel negative.
Blameless reviews. After a mistake or incident, the team reviews what happened, why and what to change, focusing on systems and learning rather than individual blame.
Red teaming. A nominated person or group challenges a plan or idea deliberately, making dissent part of the process rather than a personal risk.
Retrospectives. A regular review of what worked, what did not and what to change, including how the team is working together.
Feedback frameworks. Simple structures for giving specific, behaviour-based feedback that is clear without being personal.
Escalation routes. Clear, agreed ways to raise concerns that cannot be raised directly, so serious issues are never trapped.
Psychological safety by context
Frontline and operational teams. Safety is critical where errors can harm people or customers. The focus is on reporting near misses, stopping work when something looks wrong and learning from incidents without blame.
Professional services. Hierarchies and billable pressure can make juniors reluctant to question seniors. The focus is on making it safe to raise concerns about work quality, risk and wellbeing.
Health and community services. Teams work under pressure with vulnerable clients. The focus is on speaking up about safety concerns, supporting colleagues and learning from incidents.
Project and delivery teams. Deadlines create pressure to report good news. The focus is on honest status reporting, raising risks early and admitting when plans are not working.
Government teams. Accountability and scrutiny can make people cautious. The focus is on frank advice, challenging assumptions and learning from what does not work.
Measuring progress without making it a test
Measuring psychological safety helps teams see progress, but it must be done carefully. If people suspect survey results will be used against them, they will not answer honestly, which defeats the purpose. Good practice includes keeping surveys anonymous, sharing results with the team first, discussing them openly without hunting for who said what, and focusing on what the team will do differently rather than on the score itself. Over time, the trend matters more than any single result.
Questions for your team to discuss
- When did someone last raise a concern in this team, and what happened next?
- What kinds of things do people talk about outside meetings but not inside them?
- How do we respond when someone makes a mistake?
- Who tends to speak most in our meetings, and who tends to speak least?
- Are our standards clear, and do people feel able to ask for help meeting them?
- What would help people raise problems earlier?
Psychological safety and AI adoption
AI adoption is a test of psychological safety. Teams need people to say when an AI tool gives a wrong answer, admit they do not understand how to use it, share experiments that did not work and raise concerns about privacy, quality or job security. In teams with low safety, people either avoid AI quietly or use it without telling anyone, and neither helps the organisation learn. Building safety helps teams talk openly about what AI is good for, where it fails and how work should change. It also helps people challenge confident-sounding AI output rather than accepting it.
Psychological safety and inclusion
People do not all experience the same level of safety in a team. Those who are new, junior, from under-represented groups, working remotely or with a different first language often feel less able to speak up. A team can feel safe to its most confident members while others stay silent. Training helps teams notice these differences, invite contributions in more than one way, such as in writing as well as aloud, and pay attention to whose ideas are heard and credited. Inclusion and psychological safety reinforce each other: when more people feel safe to contribute, the team benefits from a wider range of perspectives.
What leaders can start doing tomorrow
Leaders often ask for practical first steps. A few small changes, done consistently, make a noticeable difference.
- Open the next team meeting by naming a mistake you made recently and what you learned.
- Ask "what are we missing?" before closing any decision, and wait for an answer.
- Thank the next person who brings bad news, before responding to the news itself.
- Speak last in the next discussion where your view might shape others.
- Follow up on one concern a team member raised recently and tell them what happened.
- Replace "any questions?" with "what questions do you have?", which assumes there will be some.
None of these require a program to start. Training helps leaders do them consistently, understand why they work and build them into the team's routines.
Signs that psychological safety is improving
Progress is often visible before any survey changes. Teams and leaders can watch for signs such as these:
- More people contribute in meetings, including quieter and newer members.
- Problems and risks are raised earlier, while they are still cheap to fix.
- People ask for help sooner and admit when they do not know something, without embarrassment.
- Disagreements happen openly in meetings rather than afterwards in corridors.
- Mistakes are discussed as learning, and the same mistakes recur less often.
- Bad news reaches leaders faster and less filtered.
- People suggest ideas that are unfinished or unconventional.
- Retrospectives and reviews produce real changes rather than polite summaries.
When these signs appear, they are worth noticing and naming. Recognising progress reinforces it and encourages people to keep taking the small interpersonal risks that build safety.
Starting with the right scope
Some organisations want to build psychological safety across the whole workforce. Others have one team where silence or conflict is causing problems. The right starting point depends on the situation. Often the most effective approach is to start with a leadership team or a small number of teams, learn what works in the organisation's context and then extend the approach. The scoping call helps decide where to start and who needs to be involved. Where a team is dealing with serious conflict, bullying or harassment, psychological safety training is not the first step. Those situations need proper investigation and support under the organisation's policies and legal obligations, and training can follow once the immediate issues have been addressed. The scoping call is the place to raise these concerns, so the right support is put in place before any workshop is designed. Handled in that order, the training builds on a stable foundation and is far more likely to help the team move forward together. It also protects the people involved.
Talk to Collective Campus
If people in the team hold back ideas, hide mistakes or avoid hard conversations, start with a short scoping call. The conversation covers what is happening, who should be involved and what a useful outcome would look like. Book a scoping call.
Frequently asked questions
- What is psychological safety at work?
- It is a shared belief within a team that it is safe to take interpersonal risks, such as asking questions, admitting mistakes, offering ideas or challenging decisions, without fear of embarrassment or punishment.
- Who developed the concept of psychological safety?
- The concept is most closely associated with Harvard Business School professor Amy Edmondson, whose research on teams showed its link to learning and performance. Google's Project Aristotle later brought it to wider attention.
- Is psychological safety the same as being nice?
- No. Niceness often means avoiding conflict. Psychological safety makes it possible to disagree, challenge and give honest feedback, and the best teams combine it with high standards.
- Is psychological safety a legal requirement in Australia?
- Australian work health and safety laws require employers to manage psychosocial hazards, such as poor support, conflict and poor change management. Psychological safety is related but not identical, and building it can support those obligations.
- How long is psychological safety training?
- There is no fixed length. Collective Campus tailors every program after a scoping call, depending on the team, its current situation and its goals.
- How much does psychological safety training cost?
- Collective Campus does not publish prices. Pricing is discussed after a scoping call, once the scope and format are clear.
- Should leaders attend psychological safety training?
- Yes. Leaders have the biggest influence on psychological safety through how they respond to questions, mistakes and dissent. Many programs start with the leadership team.
- How do you measure psychological safety?
- Short, repeated team surveys are common, alongside observed behaviours such as who speaks in meetings, how early problems are raised and how openly mistakes are reviewed.
- Can psychological safety be built in remote teams?
- Yes, though it takes deliberate effort. Techniques include structured turn-taking, written input, explicit check-ins and clear norms for online meetings.
- How quickly does psychological safety improve?
- It depends on the team and on leaders' consistency. Small changes can be noticed quickly, but lasting safety is built through repeated experiences of speaking up and being heard well.
Tell us about your team
A short scoping call is the next step. You can also send a note about what the team is working on.