Your brain isn't built to help you take feedback well. Its job is to keep you safe, scanning for threats several times a second, and criticism registers a lot like being confronted by a predator. That's not a metaphor, it's how the amygdala works: the moment it flags a threat, it shuts down the prefrontal cortex, the part of the brain responsible for logic, nuance and problem-solving. Once someone's in that state, no amount of careful wording brings them back. The moment for that has already passed.
That's exactly why Teamwork is one of the five petals in PETALS. Supporting each other, asking for help, being honest about how something's really going, none of that happens if people are quietly bracing for impact every time a conversation starts. And it's why Serenity sits right next to it. Stress and psychological safety are tangled together, not separate things. A team that feels safe is a team that can actually hear each other.
So before I think about how to word feedback better, I've learned to ask a different question first: does this team feel safe enough to receive it at all?
The research backs this up
A single sentence can be the difference. Leadership IQ's research found that adding one judgemental sentence to a piece of feedback pushed defensiveness from around 4% up to 62%, roughly a 17x jump. That's how thin the line is between feedback someone can actually hear and feedback that shuts them down on the spot.
CIPD's evidence review on trust and psychological safety backs this up from the other direction. In psychologically safe environments, people are less defensive and more focused on team goals. They feel able to offer ideas, share views or admit mistakes without fear of being punished or ridiculed for it. The environment is doing a lot of the work before a single word of feedback gets said.
And the cost of getting this wrong shows up in places you wouldn't expect. CIPD's Health and Wellbeing at Work report found UK employees took 9.4 sick days on average last year, up from 7.8 in 2023, with weak wellbeing and feedback cultures named as a driver. This isn't just an awkward-conversation problem, it shows up in absence figures.
Building that safety first
If safety is the thing that actually determines whether feedback lands, it has to be built on purpose, not assumed. A few things I've found help:
Name the tension when you feel it. If a conversation's getting defensive, say so out loud: "I can feel this getting tense, let's slow down." Naming it shifts things away from threat mode and back towards the part of the brain that can actually think.
Treat feedback as ongoing, not a verdict. It's data for getting better, built into how the team works week to week, not a one-off correction that only turns up when something's gone wrong.
Don't ambush people. Safety is often won or lost in the first ten seconds. A heads-up like "Got 10 minutes this afternoon to talk through the client call?" beats a surprise ping.
Open with the goal, not the problem. "My aim here is to help you nail the next one" sets a completely different tone to leading straight with what went wrong.
Talk impact, not assumed motive. People judge themselves by their intent, but everyone else judges them by impact. "The client stopped asking questions" lands better, and triggers less defensiveness, than "you weren't listening."
None of this is about softening feedback until it says nothing. It's about not letting someone's brain treat the conversation as an attack before the actual message even gets a chance.
It's also why the PETALS snapshot asks how people are feeling before it asks what they've delivered. A team that's honest in a two-minute check-in is a team that can hear feedback without shutting down too. Same problem, same fix: build the safety first, and the rest gets a lot easier.
This is the kind of thing our newsletter subscribers hear about first. If you'd rather get product updates and insights like this straight in your inbox instead of waiting for the blog, subscribe below.