Thanks for the Feedback Stone Heen

1. 1Name what you actually need before the conversation: appreciation (am I seen?), coaching (help me improve), or evaluation (where do I stand?). Ask for that specific type by name, as you did with Rick: 'I need more direction.'
2. 2When you receive feedback, first identify which of the three types the giver intended, then check whether it matches what you wanted — mismatch is the source of most 'cross-transaction' confusion.
3. 3Shift from 'That's wrong' to 'Tell me more.' Instead of screening for what's invalid (as Holly does with Irwin's 'boundaries' feedback), ask questions to understand the giver's data and reasoning before you judge it.
4. 4Separate the giver's intentions from their impact on you when discussing feedback: state 'Here's what I was trying to do' and 'Here's the impact you're describing' as two distinct arrows, then investigate the gap.
5. 5Target the 40 percent you control — your interpretation and story — not the wiring or circumstances. When upset, ask 'Is this a kitten or a tiger?' to catch emotion inflating the feedback's size.
6. 6Deliberately seek feedback from the people you clash with most. Ask them directly: 'What am I doing that's making this worse?' Their view of your impact under stress is the mirror you can't produce yourself.
7. 7Get coaching and appreciation continuously, project by project — 'honk now' rather than saving it for a year-end review, because that's when you can still change course.

You move from head of Miami marketing to head of product campaigns for the Pacific Rim and feel lost — you don't even know what the Pacific Rim is. Rather than wait for a trophy, you name your need: you tell Rick you need more direction, and you set up weekly meetings where you go over your work and questions, drawing on his regional insight — that's coaching driving skill acquisition. But you still don't know where you stand, so you raise the separate need for evaluation directly: Rick tells you your work is strong and that he's grooming you as his successor, resolving your anxiety about being a stopgap. The lesson is that coaching accelerated your learning of the markets, products, and culture, while evaluation told you where you stood — two different needs requiring two different asks. When your friend then blurts feedback about picking up checks, the wires cross: you wanted appreciation for your news, he delivered evaluation, and neither lands.

• If you want to help someone improve, then coach — never disguise coaching as evaluation ('You're no good' when you mean 'Here's how to get better').
• If you can't tell where you stand and it affects a decision (a promotion, a relationship's future), then ask explicitly for evaluation — don't let coaching's silence answer it for you.
• If you're shocked by feedback because 'that's not who I am,' then you're confusing your good intentions with your actual impact — separate the two and investigate.
• If you feel a jolt of anxiety and the feedback suddenly seems threatening, then pause and size it 'at actual size' before responding; your emotion is likely distorting the meaning.
• If you want to fast-track growth, then go to the person you have the hardest time with and ask what you're doing to exacerbate the situation.

• Screening feedback for what's wrong instead of what's useful — the tell is Holly saying 'I'll keep that in mind' while already deciding she won't, treating right feedback as wrong because it's uncomfortable.
• Delivering the wrong type: the giver intends coaching but the receiver hears evaluation, or a receiver wants appreciation but gets advice. The tell is the receiver leaving the meeting confused about what just happened, like April wondering 'what the heck.'
• Assuming good intentions guarantee good impact ('I'm trying to help, so they must feel helped'). The tell is being 'shocked and bewildered' when told you're bossy, then discarding it as wrong.
• Withholding appreciation while giving coaching or evaluation — the caretaker snapped at for one moment gets no acknowledgment for years of showering, feeding, and carrying. The tell is the receiver's resentment: 'Where's the appreciation?'
• Batching feedback for later instead of giving it in the moment. The tell is the year-end-review mindset applied to a driver who needs to move now — the moment to change has already passed.

• ▸Trigger event: what feedback exchange prompted this (one line)
• ▸Type I wanted: appreciation / coaching / evaluation (circle one)
• ▸Type I actually got: appreciation / coaching / evaluation (circle one)
• ▸Cross-transaction check: did wires get crossed, and how
• ▸Kitten-or-tiger: is my emotional reaction sizing this accurately? (yes/inflated)
• ▸Intentions vs. impact: what the giver likely intended vs. the impact described
• ▸My 40% move: how I'll reinterpret or what I'll ask to understand more
• ▸Hardest-person ask: who I clash with and the question I'll bring them

1. 1Confirm the feedback type before acting on it: separate appreciation, coaching, and evaluation, because only coaching and evaluation actually drive performance change while appreciation determines whether you can hear either. Name the purpose out loud with the giver: 'Is this meant to tell me where I stand, or to help me improve?'
2. 2Resist the volume problem. When a report contains dozens of comments and three vague 'areas of improvement,' don't try to fix everything—label-y ratings like 'below the mean on engagement' don't tell you what to change. Set aside the report and go source specific behavioral input.
3. 3Interview a small, varied set of people directly. Pick 3-5 you work with in different roles—include your boss and even someone you find irritating—and ask the single question: 'What's one thing I'm doing that gets in the way of my own effectiveness?' Ask follow-ups to make each vague label concrete.
4. 4Listen for themes across the interviews rather than treating each comment as equal. When three of five people independently name the same behavior, that convergence identifies the highest-leverage change—especially if it wasn't even on your radar.
5. 5Aim for one thing at a time. Tell givers explicitly: 'I'm serious about improving, and the best way for me to do that is to focus on one thing at a time. Let's figure out where to start.' If changes are on different fronts, you can carry a few in parallel.
6. 6Check your unconscious signals against your stated intent. When effort and result diverge (you're working on X but the feedback repeats X), assume you're sending signals that undermine you, and get specific behavioral detail on what people actually observe.
7. 7Track the change against an observable behavioral standard, not against your intent, so the improvement is measurable and confirmable by the same people who flagged the gap.

Rodrigo's 360 report had dozens of comments and three highlighted areas of improvement, but most of it was vague and label-y—at the mean on 'empathy,' below the mean on 'engagement'—and the sheer volume left him with no place to begin. So he abandoned the report and ran his own process: he chose three people he worked closely with in different roles, added his boss and a coworker he found particularly irritating, and asked each the same question—'What's one thing I'm doing that you think gets in the way of my own effectiveness?'—with clarifying follow-ups. The longest conversation took ten minutes. He then looked for themes rather than counting comments: three of the five went straight to his tendency as a team leader to hang back and let others dominate the conversation. Until that moment, that shortcoming wasn't even on his radar—though in retrospect he realized it had been buried in his earlier feedback. The convergence, not the volume, told him where the real leverage was.

• If a comment is a rating or comparison against a standard ('below the mean,' 'meets expectations'), then treat it as evaluation—useful for knowing where you stand, useless as an instruction for what to change; convert it into behavioral coaching before acting.
• If the feedback report is high-volume and vague, then stop reading it and go ask a small varied group for 'one thing' each—specificity beats comprehensiveness.
• If three or more independent sources name the same behavior, then that theme is your priority even if it surprises you; single mentions can wait.
• If you're already working hard on a trait and the feedback repeats it unchanged (as with Annabelle and respect), then stop assuming bad faith or politics and investigate the unconscious signals you send under pressure.
• If a giver hands you a long list, then explicitly renegotiate to one focus at a time and name that you're setting priorities, not dodging the rest.

• Trying to act on everything at once: the reader drowns in a report of dozens of comments and three areas of improvement and stalls. The tell—you feel 'at a loss for where to begin' and take no concrete action.
• Treating vague labels as improvement instructions: 'below the mean on engagement' names a rating, not a behavior. The tell—you can't say what you'd do differently tomorrow morning.
• Hearing coaching as evaluation, which produces defensiveness instead of learning ('You're telling me how to improve, but really you're saying I'm not cut out for this'). The tell—you feel judged and go looking for hidden verdicts instead of the fix.
• Assuming your intent equals your impact: Annabelle worked on respect, said please and thank you, yet under pressure rolled her eyes and answered sharply—so the 360 repeated the same criticism three years running. The tell—your effort is high, the feedback is unchanged, and you suspect politics or projection.
• Blaming the sources when the theme is inconvenient: dismissing convergent feedback as anonymous shots or people playing politics. The tell—multiple independent people say the same thing and your first move is to question their motives.

• ▸Feedback type: mark whether this is appreciation, coaching, or evaluation—act only on coaching/evaluation
• ▸Sources interviewed: list 3-5 people in different roles (include boss + one you find irritating)
• ▸The one question asked: 'What's one thing I'm doing that gets in the way of my own effectiveness?' plus follow-ups
• ▸Raw responses: one line per source, in their words, converted from labels to observable behavior
• ▸Theme: the behavior named by three or more sources
• ▸My stated intent vs. their observed impact: note any gap (what I'm trying to do / what they actually see)
• ▸The single focus: one behavior to change first (name it, don't list five)
• ▸Observable success marker: what the same sources would see me do differently that proves the change
• ▸Review date + who confirms: when and with whom I'll recheck the behavior

1. 1Diagnose which of three feedback types is on the table before responding — appreciation (I see you, you matter), coaching (help you grow, or fix an imbalance in the relationship), or evaluation (where you stand against a standard). Misreading one for another wrecks the relationship.
2. 2When you sense the coaching is actually about the giver's feelings or a perceived imbalance ('When's the last time you picked up the check?'), name that out loud rather than debating the literal content. The 'problem' being fixed is how the giver feels.
3. 3Audit for appreciation deficits in both directions. Ask directly whether the other party feels seen, and check whether you're withholding acknowledgment because you're under pressure to get things done.
4. 4Deliver appreciation in a form the receiver actually takes in — words, acts of service, quality time, recognition, or being brought the tough problems first. Confirm it lands rather than assuming your channel matches theirs.
5. 5When you receive relationship-level coaching, resist the reflex to assert 'they're the real problem.' Ask 'how,' not 'whether' — 'What do you see me doing that disables the staff?' rather than defending your track record.
6. 6Separate 'what's wrong' from 'what might be right' on paper. When you catch yourself defending, write the grievance in the 'what's wrong' column, then force attention back to what's valid in the other person's view.
7. 7Bring your whole self — flaws, uncertainty, not-having-it-figured-out — into the exchange. The quality of the relationship, not the accuracy of the assessment, determines whether feedback improves trust.

Fiona ran a health center for ten years and, facing a leadership gap, first assumed she needed new hires or more training. A friend asked, 'What are you doing that is disabling your staff from learning?' Fiona was offended and pointed to all her mentoring, but the question needled her. Instead of debating whether she disabled her staff, she went to a capable junior staffer and asked how — 'What do you see me doing that disables the staff?' The answer: her fingerprints were on everything, so no one could decide anything without her say-so, and staff never learned to trust their own judgment. She stepped back and gave staff more responsibility. Three things followed: staff grew, her relationships with them strengthened, and by showing she wasn't perfect, everyone loosened up and learned from mistakes more easily.

• If your purpose is coaching, then never phrase it as evaluation — don't say 'You're no good' when you mean 'Here's how to get better.'
• If the person keeps 'listening for something else' and your coaching won't land, then check for a missing appreciation floor first — they need to know you see their effort before they can hear advice.
• If the feedback is prompted by friction between you and the giver, then treat 'change and the problem is solved' claims as data about the relationship, not verdicts on who's to blame.
• If you're tempted to dismiss feedback because of who delivered it or how badly it arrived, then separate the message from the messenger — you can still learn even when it's delivered poorly or by someone you distrust.
• If appreciation would be issued through gritted teeth or for trivial acts, then withhold it — inflated or fake appreciation devalues the currency and lowers trust further.

• Delivering evaluation when you meant coaching — the tell: the receiver hears 'I'm no good at my job' instead of 'I have trouble closing certain kinds of deals,' and the conversation floods into their whole self-image.
• Mutual Appreciation Deficit Disorder — the tell: both parties privately believe 'you don't appreciate all I do,' and it's become two-way and unspoken while you both focus on the latest snafu.
• Expressing appreciation in a channel the receiver doesn't hear — the tell: you feel you've been generous but they still feel unloved or unseen, like love spoken in the wrong language.
• Removing evaluation entirely to avoid its sting — the tell: people start mining coaching and appreciation for hidden verdicts ('why was I singled out in the first email but not the second — should I be concerned?').
• Defending yourself against relationship feedback by asserting the other person is the real problem — the tell: 'we wouldn't need to be so controlling if they'd get off their backside,' and you never ask 'how' you contribute.

• ▸Feedback received (verbatim): write the actual words said
• ▸Type: is this appreciation, coaching, or evaluation?
• ▸Hidden layer: is this coaching about my skills, or about the giver's feelings / an imbalance?
• ▸What's wrong (my objections): dump every defense and grievance here
• ▸What might be right / valid: force at least three things the other view gets right
• ▸Appreciation check: does this person feel seen by me, and do I feel seen by them?
• ▸My channel vs. theirs: how do I express appreciation, and does it match how they receive it?
• ▸'How' question to ask: rewrite my defensiveness as a curious question about my own contribution
• ▸Whole-self move: what flaw or uncertainty can I admit to strengthen the relationship?

1. 1Name the three types before responding to any feedback: appreciation (I see you, you matter), coaching (here's how to grow), evaluation (where you stand). Decide which one you actually need right now.
2. 2Before a feedback conversation, state out loud what you're asking for. Instead of 'give me feedback,' say 'I want to know that the work I'm putting in is noticed' (appreciation) or 'I want specific tips to do this faster' (coaching).
3. 3When you feel invisible or overworked, ask directly for appreciation that is specific — not 'good work' but naming the exact thing you did and its effect on the giver.
4. 4Establish your 'evaluative floor' first: confirm where you stand and that the relationship is secure. Until you know you're 'good enough so far,' you cannot absorb coaching or appreciation.
5. 5When you catch yourself 'wrong spotting' (2+2=5 wrong, different-planet wrong, right-but-not-now), pause and shift the internal question from 'What's wrong with this feedback?' to 'Tell me more — what does the giver see that I don't?'
6. 6Separate how you're hearing the feedback from what was actually said. Ask: am I reacting like Annie (grateful, energized) or Elsie (hurt, defensive)? If Elsie, name that you heard 'you're not good enough' and check whether that was intended.
7. 7Check whether the friction is about your role or your self. Take two steps back: 'How much of this is my performance/personality, and how much is the role I occupy?'

April has worked for the partner Donald for eight years, anticipating his needs, working tirelessly, and often feeling stressed and invisible because Donald never says thanks. Prompted by HR, she asks Donald for feedback — but what she actually needs is appreciation, a pat on the back that says 'I see all that you do for me.' Donald, pleased she took initiative, gives her thoughtful coaching instead: organize your workspace, be more assertive about saying no. His coaching is useful and well-delivered, but April leaves feeling more invisible than ever and wonders if she should quit. The damage came not from wrong feedback but from a cross-transaction: she wanted one kind and got another. Her well-being eroded because the absence of appreciation left a gaping hole that no amount of good coaching could fill — she was listening for something else, so the coaching never got through.

• If you feel unnoticed rather than unskilled, then ask for appreciation, not advice — the paycheck is not the point.
• If you don't yet know you're 'good enough so far,' then get evaluation (an evaluative floor) before you can take in any coaching or appreciation.
• If you're reacting like Elsie — hurt, defensive, refusing to try — then the issue is how you're hearing it, not the giver's skill or words; treat the reaction as data, not verdict.
• If appreciation is going to count, then make it specific and about this person's actual effort — grand strokes like 'Good work!' or 'You were fabulous!' don't register.
• If a relationship feels persistently strained, then separate the person from their role before attributing the conflict to character.

• Confusing your own reactions with objective wrongness — the tell is how quickly you can name what's 'wrong' with the feedback; wrong spotting is almost always available and it defeats learning.
• Delivering or accepting appreciation in vague 'grand strokes' — the tell is a 'Thanks for everything!' that leaves the receiver still wondering whether anyone actually noticed what they did.
• Reading absence of appreciation as neutral — the tell is a person who is fed, paid, or still married but quietly deciding to quit or withdraw because the gaping hole was never named.
• Giving coaching when someone needs an evaluative floor — the tell is the receiver 'putting their ear to the ground,' over-interpreting every stray signal to figure out where they stand.
• Treating yourself as the sympathetic hero of every story — the tell is that in your version you're always Dorothy or the Princess, never the Wicked Witch, which blinds you to the giver's legitimate point.

• ▸What I'm actually feeling: name it (invisible / adrift / uncertain of standing)
• ▸What I need: appreciation / coaching / evaluation — pick one
• ▸What I'll ask for in plain words: the exact sentence I'll say
• ▸My evaluative floor: what confirms I'm good enough so far
• ▸Specific appreciation I want acknowledged: the exact action + its effect
• ▸Which kind of feedback I'm probably getting: their apparent intent
• ▸Am I hearing it as Annie or Elsie: and what I heard 'you're not good enough' from
• ▸Wrong-spotting check: the flaw I found — set it aside, then 'tell me more' question
• ▸Role vs. self: how much of this is my role, not my worth

1. 1Before reacting, ask yourself which of the three kinds of feedback you're getting: appreciation (I see you, you matter), coaching (help you grow), or evaluation (where you stand). Name the mismatch — the giver may be offering one while you crave another.
2. 2Separate the message from the messenger. Notice when you're rejecting content because of who's delivering it or how they said it, then evaluate the substance on its own terms.
3. 3Seek to understand before you judge or defend. Ask the giver what they saw and what they mean before deciding whether it's right or wrong.
4. 4Hunt for the implicit rule behind the interaction. When feedback makes no sense, ask 'what unstated rule about how things should be done explains why they read me this way?'
5. 5Take three steps back to find systemic causes. Step one: individual intersections (the fit between your wiring and theirs). Step two: roles (how structural role tensions shape how you see each other). Step three: the big picture — physical environment, timing, policies, processes, coping strategies, and lag effects.
6. 6Look for your blind spots by gathering outside data. Record yourself, ask a specific 'what's one thing I do that gets in my own way?' question, or note others' faces and tone — since your leaky tone and social signals live where you can't see them.
7. 7Check the 'sympathetic hero' bias: assume you're at the center of the story casting yourself as the good guy, then deliberately reconstruct how the other person experiences you.

A second-grade teacher tells Kenzie's mom, 'Your daughter is a strong personality. She says things that upset other children.' Kenzie, eavesdropping, bursts in: 'Those kids are so annoying! They're the ones who start it! I can't help it if they're crybabies!' — casting herself as victim, not problem. Using three steps back reframes the feedback: step one (individual) sees Kenzie is inborn dramatic, where everything is 'amazingly fabulous' or 'horribly catastrophic.' Step two (role) reveals she was the new kid last year, felt urgency to find a niche, and 'won' by entertaining — so classmates rewarded bigger, more exaggerated stories, cementing her as class entertainer. Step three (system) shows her behavior influences classmates' behavior which loops back to encourage more of hers, and that sensitive kids experience her oversized reactions as devastating in a way she can't feel. Now the feedback isn't 'Kenzie is a bully' but 'here's a system Kenzie is caught in and can help change.' The disentangling turns an accusation into something workable.

• If you feel hurt, defensive, or resentful like Elsie at the batting cage, then pause and check whether you're hearing coaching as evaluation ('you're not good enough') before you stomp off.
• If you keep saying 'I'm not getting feedback,' then diagnose which kind you actually want — often you have appreciation but crave coaching, or have coaching but need to know where you stand.
• If someone is described as 'difficult' or 'compulsive' or a 'bully,' then ask 'how much is role, and how much is personality?' before attributing it to character.
• If feedback simply doesn't make sense, then look for the contrasting implicit rule ('direct = engaged' vs 'direct = rude') that explains the interpretation.
• If you can only find one compelling cause, then take another step back — don't quit the search early, because root causes are often not proximate to the injury in time or place (lag effects).

• Hearing all feedback as evaluation. Tell: your first reaction to a tip is 'you think I'm not good enough,' like Elsie, so you reject even helpful coaching.
• Judging the messenger instead of the message. Tell: you dismiss valid content because the person was aggressive, an outsider, or 'just picking a fight.'
• Casting yourself as the sympathetic hero. Tell: in every retelling you're Dorothy, never the Wicked Witch — the other person is always the one who started it, like Kenzie blaming the 'crybabies.'
• Attributing to character what is caused by role or system. Tell: 'HR people are uptight and rule-bound' or 'Research can't get their act together' — you name a personality flaw where structural role tension or a coping strategy (false deadlines) is actually driving behavior.
• Being blind to your own leaky tone and social signals. Tell: like Zoe, you're stunned by a recording showing your first words are always negative — you sincerely believe you invite ideas while unconsciously killing them.

• ▸Feedback received (verbatim): write exactly what was said, not your interpretation.
• ▸Kind of feedback I'm hearing vs what was intended: appreciation / coaching / evaluation — name any mismatch.
• ▸Message vs messenger: state the substance separately from who said it and how.
• ▸My hero story: how am I casting myself, and how might the other person tell this story?
• ▸Implicit rule at play: what unstated 'how we do things' rule explains their reading of me?
• ▸Step 1 — individual intersection: how does my wiring fit or clash with theirs?
• ▸Step 2 — roles: how are our roles (not personalities) contributing to this feedback?
• ▸Step 3 — big picture: which environment, timing, policy, process, or coping strategy is shaping this — including lag effects?
• ▸My blind spot to test: what data (recording, a specific question, watching faces/tone) could reveal what I can't see?

1. 1Separate the feedback from your identity: when a comment lands as a verdict on Who I Am, name it out loud to yourself as data about one behavior, not a ruling on your worth. This is the move from vulnerable fixed identity to robust growth identity.
2. 2Run the 40 percent check. About 50 percent of your reaction is wired in and 10 percent is circumstance, but 40 percent is the meaning you make. Ask: what story am I telling about what this feedback means, and is that story kitten-sized or tiger-sized?
3. 3Dismantle the distortion. When emotion inflates a harmless comment into a threat, ask whether the boss's 'gentle advice as harmless as a kitten' is actually threatening at 'actual size,' then resize it before deciding what to do.
4. 4Shift the screening question from 'What's wrong with this feedback?' to 'Tell me more.' You can always find something wrong, so hunting for the flaw is a guaranteed off-ramp from learning.
5. 5Distinguish acceptance from immunity. Wanting to be accepted as you are is legitimate, but check whether 'that's just who I am' is really an escape hatch from responsibility for consequences.
6. 6Go to the people you have the hardest time with and ask what you're doing that exacerbates the situation. Under stress and conflict you lose skills and impact others in ways you can't see, so those hardest relationships are your honest mirrors.
7. 7Re-tell the story with growth built in: interpret upsetting feedback and even failure as material for learning, the way interpretation can turn post-traumatic stress into post-traumatic growth.

David tells Cheng, 'There's no one more talented than you, but in this industry, image is as important as substance... you've got to kick high.' To David this is a small behavioral tweak with a big payoff. To Cheng it feels like a rejection of who he is, so he refuses: if he advances it will be on merit, and he won't sacrifice the humility and authenticity at the core of his identity to become a 'phony, self-promoting windbag.' A growth identity lets Cheng hold both: he can keep his identity sturdy while still hearing the coaching as one adjustable behavior rather than a referendum on his character. He can ask 'tell me more' about what 'image' costs and buys in this industry, then implement any useful part in a way consistent with his own values. David, meanwhile, wonders whether Cheng's 'this is who I am' mantra is just a way to insulate himself from criticism, which is the acceptance-as-immunity trap for the receiver to watch.

• If a comment about one behavior feels like a rejection of Who I Am, then you have an identity trigger, not just feedback content; resize it to behavior before responding.
• If you catch yourself asking 'What's wrong with this feedback?', then switch the question to 'Tell me more,' because you can almost always find something wrong.
• If your emotional reaction is disproportionate to the words, then assume emotion is distorting the meaning and check the feedback at actual size before you decide anything.
• If you're tempted to say 'that's just who I am,' then ask whether you're seeking acceptance or seeking immunity from consequences that affect others.
• If someone difficult keeps giving you the same hard feedback, then treat them as your honest mirror and ask directly what you're doing to exacerbate it, rather than dismissing them for lacking credibility.

• Screening for the flaw: like Holly, who says she'll 'keep that in mind' but won't, you find the one thing wrong with valid feedback and discard the whole thing. Tell: you're building a case against the giver instead of asking a question.
• Being Krista in reverse: treating all negative signals as honks of support and staying oblivious. Tell: you hear criticism and immediately think 'Really? But do you know how amazing I am?'
• Collapsing behavior into identity, so one adjustment reads as total rejection. Tell: your response is 'that's not who I am' to a comment that was about a specific action.
• Using acceptance as an escape hatch. Tell: 'Just me being me!' shows up right after a consequence that hurt someone else.
• Rejecting feedback on credibility grounds. Tell: you explain what the giver is like and how they'd have to know you to understand, instead of testing whether their fresh outside perspective is right.

• ▸The feedback in their words: write the actual sentence, not your interpretation.
• ▸Story I'm telling: what I think this says about me.
• ▸Kitten or tiger: is my reaction sized to the words or inflated by emotion?
• ▸Behavior vs. identity: what specific behavior is named, separate from Who I Am?
• ▸Acceptance or immunity: am I seeking to be accepted, or dodging a consequence?
• ▸Tell-me-more question: one question that opens the feedback instead of screening it.
• ▸Hardest-person mirror: who that I struggle with would confirm or deepen this?
• ▸Growth reframe: how could acting on this become learning rather than a verdict?

1. 1Name the trigger type before responding: is your reaction about the content (truth), the person delivering it (relationship), or what it says about who you are (identity)? The label tells you which regulation move to make.
2. 2When you feel the surge of skepticism or defensiveness, slow the conversation down rather than rebutting. Ask for the specific data or example behind the label ('walk me through the methodology,' 'let's look at a concrete example') instead of dismissing the whole.
3. 3Separate the two topics when a relationship trigger fires. Notice if you've switchtracked—if you're answering the giver's feedback with your own grievance, stop and hold both topics visibly so no one's feedback goes unreceived.
4. 4Convert your first reaction from 'is this right or wrong' to 'what are they seeing that I'm not.' Adopt a mindset of understanding, not agreeing or defending—that's how Paul stayed curious even while feeling the same frustration Johann acted on.
5. 5Account for your blind spots deliberately: remember you can't hear your own tone (your STS shuts off when you speak) and you judge yourself by intent while others judge you by impact. Assume the gap is real before disputing their read.
6. 6Check whether you're disqualifying the giver on how/when/where or on credibility. If you catch yourself thinking 'why should I listen to them,' test whether an outsider's naïve question might be exactly the insight you're missing.
7. 7Verify the feedback applies to you personally when it's addressed to a group—ask directly ('do you think that's the perception people have of me?') so you don't quietly exempt yourself.

Monisha presents a disquieting employee climate survey and Johann immediately trips a truth trigger: 'Garbage in, garbage out... some of us have a business to run,' then walks out—disqualifying the giver and the data in one move. Paul feels the identical frustration and skepticism, but manages his trigger differently. Instead of attacking the methodology, he inquires under the label: he asks about the numbers, then says 'let's look at a concrete example,' surfacing the ethics-workshop complaint. When Monisha distinguishes a 'messaging problem' from an 'attitude problem,' Paul admits 'I'm not clear what you mean' and slows down rather than defending. He then asks whether the perception is about him personally, hears that the two-hour session sent a message he didn't intend but that was 'actually the truth,' and arrives at 'I'm beginning to see how someone might feel we're being hypocritical. This is a little shocking.' Same feedback, same emotional trigger—but Paul's curiosity produced learning where Johann's defensiveness produced an exit.

• If you feel the urge to rebut the methodology or credibility, then ask for the specific data or example first—disqualify only after you understand.
• If you and the giver are 'both talking about the same thing' but heading in different directions, then you've switchtracked; name both topics and pick one to finish before starting yours.
• If the feedback is about tone or impact and your reflex is 'I'm not using some kind of tone,' then assume your STS blind spot is operating and treat their read as data, not accusation.
• If feedback is addressed to your group, then ask explicitly whether it applies to you personally before assuming it's about others.
• If your purpose is to understand rather than to agree/disagree or defend/accept, then keep inquiring; if you notice yourself defending, you've switched purposes and lost the thread.

• Attacking the source to avoid the substance—the tell is 'garbage in, garbage out' or 'why should I listen to them,' discarding the what based on the who.
• Switchtracking: answering feedback with your own grievance (Louie meeting Kim's 'you don't listen' with 'give me a little gratitude')—the tell is two people giving feedback and no one receiving it.
• Defending intent over impact—the tell is 'that's not what I meant,' as if your intention settles how it landed for others.
• Denying your tone or blind spot outright ('I'm not using some kind of tone')—the tell is surprise or offense at feedback about how you came across.
• Quietly exempting yourself from group feedback—the tell is leaving thinking the criticism was about 'them,' never having asked if it's about you.

• ▸Trigger type: truth / relationship / identity — which reaction is firing?
• ▸The label I want to reject: what dismissive verdict am I reaching for?
• ▸Data under the label: what specific example or evidence have I actually asked for?
• ▸Switchtrack check: whose topic am I answering—theirs or my own grievance?
• ▸Blind-spot flag: is this about my tone, impact, or a pattern I can't see in myself?
• ▸Does this apply to me? — one question I'll ask to confirm it's about me personally
• ▸My purpose right now: understand / agree-disagree / defend-accept (circle one)
• ▸One curious question I'll ask next instead of rebutting

1. 1Before reacting, name which of the three kinds of feedback you're receiving: appreciation (thanks, 'I see you'), coaching (help to learn/grow), or evaluation (where you stand). Utility lives in a different place for each.
2. 2Separate delivery from data. Ask: 'What is the giver trying to tell me, independent of how it landed?' The pitch that hit you (Elsie) and the pitch down the middle (Annie) can carry identical information.
3. 3Account for the 'bad is stronger than good' wiring. When one criticism swamps four hundred compliments, treat that as your amygdala's red alert firing, not as proof the criticism is more valuable. Wait for baseline recovery before judging utility.
4. 4Run toward the data you least want. When the boss mentions the committee's 'questions about your overall commitment,' say 'it's helpful to know' and mine it: it tells you how you come across, which is actionable regardless of whether it's fair.
5. 5Convert the feedback into one concrete change. Use 'Name One Thing'—ask the giver (or yourself) for the single most important thing to do differently, so utility survives being overwhelmed by charts, graphs, and competencies.
6. 6Test the perception before you fight the label. Ask to talk to the person holding the concern to learn more before deciding whether to contest it—separate learning from negotiating.

In the compensation review, your boss discloses that committee members 'raised questions about your overall commitment'—and adds that he disagrees and nearly withheld it to spare you. The delivery invites you to dismiss it as noise. Instead you locate its utility: 'Of course it's upsetting to hear, but it's helpful to know. It tells me that whether or not you or I think I'm dedicated, I'm coming across at least to some people in a way that is raising some questions.' You've reframed a stray, arguably unfair judgment into data about perception you control. Then you protect learning from bargaining: you leave the rating alone for now and ask to speak with a committee member 'to learn more about that perception before I decide whether to pursue changing the rating.' The utility wasn't in the verdict; it was in the gap between how you see yourself and how you land.

• If you feel like Elsie (hurt, resentful), then pause and ask which kind of feedback you're hearing before rejecting it—your reaction may be about the label, not the content.
• If one negative comment is drowning out abundant positives, then assume the amygdala's asymmetry is inflating it and wait for recovery before assigning weight.
• If the feedback is unfair or you disagree with it, then still ask 'what does it tell me about how I'm perceived?'—perception is usable even when the judgment is wrong.
• If you're overwhelmed by volume (charts, comments, competencies), then extract one thing to change rather than trying to metabolize all of it.
• If you want to change the outcome, then separate learning from negotiating—understand the perception first, contest the rating second.

• Judging utility by delivery: dismissing coaching because it stung (Elsie hears 'you think I'm not good enough' from the same tips Annie finds exhilarating). Tell: your objection is about tone or the giver, not the substance.
• Letting 'bad is stronger than good' set the verdict—obsessing over the mother-in-law's oblique comment amid a lovely visit. Tell: you're replaying one line and can't recall the compliments.
• Confusing the kinds of feedback so you rate the wrong thing 'useless'—wanting evaluation but getting appreciation, then feeling you 'got no feedback.' Tell: 'What do you want, a trophy?' disagreements.
• Rejecting feedback because it's unfair, and throwing out the perception-data with it. Tell: you argue the verdict is wrong instead of asking why you come across that way.
• Collapsing learning and negotiating into one move—fighting the rating before you understand it. Tell: you're arguing consequences before you've asked a single clarifying question.

• ▸Feedback (verbatim): write exactly what was said, not your paraphrase.
• ▸Kind: is this appreciation, coaching, or evaluation?
• ▸Delivery reaction (0-10): how much did the delivery/emotion spike me?
• ▸Bad-is-stronger check: am I over-weighting one negative? yes/no + why.
• ▸Even-if-unfair data: what does this tell me about how I'm perceived?
• ▸One thing: the single change I could make from this.
• ▸Learn-first action: who can I ask to understand the perception better?
• ▸Negotiate-later note: what, if anything, I want to contest—after learning.

1. 1Name which of the three kinds of feedback you are giving before you give it: appreciation (I see you), coaching (help you improve), or evaluation (where you stand). Mismatch between what's given and what's wanted is the most common source of felt threat.
2. 2Ask the receiver what they need first, so they set the terms: 'Do you want appreciation, help improving, or my read on where you stand?' Elsie hears coaching as evaluation because no one separated the two for her.
3. 3Watch for the identity trigger: when feedback contradicts someone's self-story ('I'm coordinated,' 'I'm a good son'), their story can unravel and they'll retreat or fight. Slow down and address the person, not just the content.
4. 4Take three steps back before assigning fault. Separate the individual from their role, then examine other players, processes, policies, and structures that shaped the behavior so the receiver isn't scapegoated for system failures.
5. 5Acknowledge impact and problem-solve together rather than issuing a verdict. Ask 'How does this affect you?' and invite the receiver to co-design a fix, which shares ownership instead of imposing consequences.
6. 6When someone can't or won't change, name the 'duty to mitigate' out loud and coach others on how to deal with the unchanged version—Jackie inviting teammates to 'red-card' her is safety created by permission, not punishment.

Dad takes twins Annie and Elsie to the park and offers identical batting tips in the same tone. Annie hears coaching—'help you improve'—and feels herself get better with each swing. Elsie hears evaluation—'you think I'm not good enough'—drops the bat and storms off. From the bleachers there's no difference in what Dad says; the difference is which kind of feedback each girl thinks she's receiving. If Dad had labeled it first ('This is me helping, not judging you') and asked what Elsie wanted, he could have caught the identity trigger before her self-story ('I'm uncoordinated, he always criticizes me') took over. The lesson: safety isn't only about the giver's skill or tone—it's about matching the type of feedback to what the receiver can hear.

• If the person wants to feel seen but you deliver correction, then you've triggered defensiveness—switch to appreciation first, then ask permission to coach.
• If feedback contradicts their self-story and they retreat or attack, then stop pressing content and address identity before continuing.
• If you're tempted to blame one person for a bad outcome, then take three steps back and check role, players, processes, and structures before you conclude it's them.
• If the behavior won't change, then shift from evaluation to co-designing mitigation ('red-card me') so the relationship stays intact.
• If someone says they're 'not getting feedback,' then clarify which kind—often they want appreciation, not advice.

• Blending all three feedback types into one message. The tell: the receiver hears criticism where you meant help, like Elsie hearing rejection in a batting tip.
• Treating everyone 'the same' and assuming fairness follows. The tell: identical delivery produces opposite reactions and you're 'puzzled' like Dad.
• Focusing only on the individual's behavior after a bad outcome. The tell: you interrogate the injured worker's fatigue and protocol but never ask who scheduled the double shift or cut safety training.
• Pushing coaching onto someone whose identity is already rocked. The tell: they stomp off, wail, or go aggressively quiet instead of engaging with the substance.
• Delivering a verdict and calling it feedback. The tell: the receiver experiences it as 'picking a fight' rather than an invitation to problem-solve.

• ▸Which kind: Am I giving appreciation, coaching, or evaluation? Name it.
• ▸What they want: Have I asked which kind they need right now?
• ▸Identity risk: What self-story might this feedback threaten?
• ▸Steps back: How much of this is role, process, or structure vs. the person?
• ▸Impact question: How will I ask how my feedback/decision affects them?
• ▸Co-design: What fix can we build together instead of me imposing one?
• ▸Mitigation: If nothing changes, what's the agreed workaround (their 'red-card')?
• ▸Delivery check: Am I offering to help, or issuing a verdict?