Psychological Safety: Build a Team Where Everyone Dares to Speak Up and Make Mistakes

What psychological safety is, why Google's Project Aristotle ranked it first, and practical ways to build a team that speaks up, asks and admits mistakes.

Monday morning team meeting. The manager asks, "Does anyone see any problems with this plan?" The room goes silent and everyone looks at their laptop. Two weeks later the project stalls because of a problem a junior team member noticed on day one but did not dare to raise. If this sounds familiar, what your team lacks may not be ability. It may be psychological safety.

What is psychological safety?

The term comes from Amy Edmondson of Harvard, who defines it as "a shared belief held by members of a team that the team is safe for interpersonal risk taking." Put simply, people on the team feel free to ask questions, suggest unusual ideas and say "I made a mistake" without fearing they will be laughed at, blamed or seen as incompetent.

One distinction matters: psychological safety is not being so nice that there are no standards, and it is not everyone agreeing all the time. A truly safe team can argue about work directly, because they know disagreement will not break the relationship.

Why Google cares about it

Google's re:Work guide describes Project Aristotle, which studied 180 teams (115 engineering project teams and 65 sales teams) to find what makes a team effective. It found five key dynamics, and psychological safety was the most important, followed by dependability (delivering quality work on time), structure and clarity (clear goals and roles), meaning (the work matters personally) and impact (seeing how the work contributes to the organisation).

The striking conclusion: who is on the team matters less than how the team works together.

Signs your team lacks psychological safety

• Only one or two people speak in meetings; the rest stay quiet, then complain afterwards in the LINE group
• Problems are reported when it is too late to fix them, because nobody wants to bring bad news
• New joiners never ask anything, then spend a whole week working in the wrong direction
• The default answer is "Sure" or "No problem" even when the workload is too much
• People stick with the safe old way instead of trying a new approach that might be better

In a Thai context, kreng jai (reluctance to impose) and seniority make these signs harder to see, because silence is often read as "everyone agrees."

How leaders can build psychological safety right away

1. Admit your own mistakes first

The leader sets the norm. If you say, "Last week I underestimated the timeline and everyone had to rush. Sorry about that," the team learns that owning mistakes is normal.

2. Ask open, specific questions

Instead of "Any questions?", try "If this plan fails, where is it most likely to fail?" or "What might we be overlooking?" Questions like these turn pointing out problems into part of the job, not fault-finding.

3. Respond well when someone speaks up

The moment someone raises something difficult, your reaction matters most. Try "Thanks for telling me, good that we know now" instead of "Why are you only telling me now?"

4. Separate mistakes from experimenting and mistakes from carelessness

An experiment that does not work is data, not a fault. Repeatedly skipping a process still needs a direct conversation. Safety does not mean no accountability. Read more on handling difficult conversations in Giving Constructive Feedback.

5. Create team rituals

For example, a 10-minute "lesson of the week" slot at the end of a meeting, where each person shares something that did not go to plan and what they learned, with the leader going first. Or collect anonymous questions before a big meeting.

A team that dares to say "I don't know" learns faster than a team where everyone pretends to know.

Common mistakes

• Announcing "we can talk about anything here" while looking annoyed every time someone disagrees. People believe actions over words.
• Criticising someone in front of others. Even once can bring the silence back for a long time.
• Thinking it is only the leader's job. Every team member plays a part, for example by not interrupting and not mocking a new joiner's questions.

Where to start

1. This week, notice who speaks in meetings, who stays silent and when.
2. Share one of your own mistakes with the team, along with what you learned.
3. Change your end-of-meeting question from "Any questions?" to "What could stop this plan from succeeding?"
4. Have a 1-on-1 with the quietest person and ask what would make them more comfortable speaking up.
5. Review every month whether problems are being reported earlier.

If you have just become a manager, read A New Manager's First 90 Days and How to Resolve Team Conflict, or talk through your team situation with the Plants.work AI Career Assistant to plan your next conversation. To hear how experienced leaders build trust in their teams, talk to a mentor on Plants.work.