Receiving Feedback Is a Skill – Stone & Heen
Almost all feedback training is about giving it: how to phrase things, pick the right moment, balance criticism and praise. But every feedback conversation has two roles – and it is the receiver who decides whether anything is learned. A perfectly worded observation that bounces off a closed receiver is wasted.
Douglas Stone and Sheila Heen, both affiliated with the Harvard Negotiation Project at Harvard Law School, flipped the perspective in their 2014 book Thanks for the Feedback. Their thesis: receiving feedback well is a skill in its own right – one that can be understood and trained.
What does the research say?
Stone and Heen describe three kinds of reactions – triggers – that make us reject feedback before we have even examined it. The truth trigger: "that's just not accurate" – we hear one error and dismiss the whole message. The relationship trigger: "not from you" – we react to who is saying it rather than what is being said, perhaps because that person falls short in the same area. The identity trigger: the feedback threatens our sense of who we are – "me, the one who's always been so organized" – and the whole system goes into defense mode.
These reactions are normal, not signs of weakness. The point is that once you recognize your trigger, you can separate the reaction from the content: I can be annoyed at the messenger and still explore whether the message has something to offer.
The authors also distinguish three types of feedback that are often mixed up: appreciation (I see what you do), coaching (here's how you can grow) and evaluation (here's how you measure up against the requirements). Many feedback conversations break down because the two parties are after different types – the employee needed appreciation, the manager delivered evaluation, and both walk away frustrated without understanding why.
What does this mean for you as a project manager?
When you receive criticism – from a steering group, a client or your team – notice which trigger fires first. Simply naming it silently ("there's the identity trigger") creates enough distance to ask a follow-up question instead of defending yourself: "Can you give me an example of when that happened?" Examples make vague criticism usable, and the question itself shows you are taking it seriously.
Find the grain of truth before you sort anything out. Even unfair or clumsily delivered feedback usually contains something true. Train yourself to first look for the valid ten percent, then decide what to do with the rest. That is the opposite of first finding the flaw in the criticism and thereby getting to dismiss all of it.
And when you give feedback yourself: say what kind it is. "This isn't an evaluation – I want to give you a coaching idea for the next sprint" dramatically lowers the receiver's defenses, because uncertainty about what is at stake is a large part of the threat.
How to practice this
You can only practice receiving feedback when someone is actually giving it to you. In Project-simulator there are scenarios where the AI counterpart criticizes you – sometimes fairly, sometimes clumsily – so you can practice handling your triggers without a real relationship on the line. Afterwards you see, in your own words, exactly how you responded. Try it free for a week at project-simulator.com.
In Project-simulator you practice these conversations against an AI counterpart and get feedback grounded in research like this.
Try free for 7 days