25 Sep Psychological Safety at Work: What It Looks Like in a South African SME
Google spent years studying what actually separates its highest-performing teams from the rest, in a research effort known as Project Aristotle. The single strongest factor wasn’t who was on the team, how experienced they were, or how they were structured. It was psychological safety — whether people felt safe taking an interpersonal risk in front of their colleagues. Teams with it were rated as effective twice as often by executives, brought in more revenue, and were less likely to lose people. None of that research was done on a South African SME, but the mechanism doesn’t stop applying at 40 employees.
What Psychological Safety Actually Means
It is not the same as being nice, and it is not the absence of conflict or accountability. Organisational researcher Amy Edmondson, whose work underpins the Google findings, defines it as a shared belief that the team is safe for interpersonal risk-taking — admitting a mistake, asking a question that might sound obvious, disagreeing with someone more senior, without fear that it will be held against you.
Why It Looks Different in a South African SME
In a 40- or 60-person business, the founder or a handful of senior leaders are visible in almost every room. That visibility cuts both ways: it means a leader modelling openness has an outsized effect fast, but it also means one bad reaction to a raised concern — visibly punishing a mistake, shutting down a question in a meeting — travels through the whole business within days, not quarters.
Three Signals It Is Missing
Meetings where only the most senior person speaks and everyone else nods. Problems that surface to leadership only once they are already serious, because nobody felt able to flag them earlier. And team members who consistently agree in the room and raise objections afterward, privately, to a colleague rather than to whoever made the decision.
What Builds It, Practically
Google’s own research pointed to three specific, learnable behaviours: framing work as a shared learning problem rather than a simple execution task, a leader openly acknowledging their own mistakes and limitations, and responding to questions with genuine curiosity rather than defensiveness. None of these require a budget or a programme — they require a leader doing them visibly and consistently, especially the first few times someone tests whether it’s actually safe to speak up.
The Business Case, Not Just the People Case
This isn’t purely a wellbeing argument. A team that surfaces problems early is a team that fixes them while they’re still cheap to fix. A team that raises a client concern before it becomes a lost account, or flags a process gap before it becomes a compliance issue, is doing exactly what the psychological-safety research predicts — and doing it for entirely practical, commercial reasons.
FAQs
Can psychological safety coexist with high performance standards?
Yes — Edmondson’s own framework pairs psychological safety with high accountability as the combination that produces genuine performance, not psychological safety alone as a substitute for standards.
How would a founder know if their own team has it?
A useful test: think back to the last time someone told you your own idea wouldn’t work. If you can’t remember the last time that happened, that’s the signal, not the absence of disagreement itself.
Conclusion
Psychological safety is one of the few pieces of hard organisational research that translates almost unchanged from a Google-sized company to a 40-person South African SME — because it’s fundamentally about how people, in any size room, decide whether it’s safe to speak. Building it starts with one leader, in one meeting, responding to a raised concern or an admitted mistake in a way that makes the next person more likely to raise theirs. If you’d like an outside view on where your own team’s psychological safety actually sits, book a 30-minute call with YVR Consulting.
