
Naming a trigger, as you saw in the last chapter, is something you do quietly in your head. But feedback usually arrives out loud, in a real moment, with someone watching your face and waiting for a reply. This chapter adds the part that happens in the room: how to keep your cool as a comment lands, and the handful of concrete moves that turn a hard remark into something useful. It is the last stop in Part 1, and it pulls everything you have learned about receiving into a single, repeatable response.
Picture the moment feedback actually lands. A teammate says something that stings, and you feel it in your body before you have thought a single clear thought: your face gets warm, your chest tightens, and a reply is already halfway out of your mouth. That reply, the one that arrives in the first two seconds, is almost always the reaction talking, not you. It defends, or it caves, and either way you lose the thread of what was actually said.
Staying steady is the skill of putting a small gap between the feeling and the response. The move has four simple beats:
notice the reaction in your body, the heat or the tightening, so you know it has fired;
pause, even for a single breath, before you say anything;
name the feeling to yourself, silently: “okay, that stung,” or “I’m getting defensive”;
then respond, from a slightly cooler place than where you started.
That pause is doing real work. It is the space where you get to choose your words instead of letting the reaction choose them for you.
Won’t pausing make me look like I have nothing to say?
Almost never. A short silence reads as thoughtful far more often than it reads as stuck. “Give me a second to take that in” is a perfectly good thing to say out loud, and it buys you the very gap that keeps your answer from being a reflex.
Once you are steady, receiving well comes down to a few concrete moves, none of them complicated:
ask for a specific example, so a vague comment becomes something you can picture and act on;
get curious, and ask a real question about what they meant rather than a defensive one aimed at proving them wrong;
reflect back what you heard, in your own words, so you both know you understood it;
decide later what to do about it, on your own time, once the heat is gone.
You already met the first of these, asking for a specific, back in the chapter on separating the message from the delivery; here it becomes one move in a larger sequence. And notice what is missing from the list: agreeing. Nothing here commits you to anything.
That is why one of the most useful responses you can give is also one of the shortest: “Thanks, let me think about that.” It is complete on its own. It tells the other person you heard them, it closes the moment gracefully, and it leaves the actual decision, change it or don’t, entirely with you, for later.
Because the same moves work almost everywhere, it helps to keep a small frame in your back pocket, three lines you can fill in on the spot in nearly any feedback moment:
“What I’m hearing is …” to reflect the message back in your own words;
“Can you give me a specific example of … ?” to turn the vague into the concrete;
“I’ll take that and think it over.” to acknowledge the comment and keep the decision for later.
Let us watch the whole sequence in one go. Maya runs a weekly tabletop board-game group at her local café. After a session, another regular tells her, a little sharply and in front of two others, “Honestly, your rules explanations drag on forever, and half the table zones out before we even start.”
Maya feels the heat rise at once, and her first instinct is to shoot back, “Well, someone has to explain the rules.” Instead, she catches the reaction, takes one breath, and names it to herself: okay, that stung, and it feels a bit like he is saying I am bad at this, an identity trigger firing. With that named, she can look at the message instead of the sting.
So she gets steady and reaches for the moves. “Give me a second,” she says, then: “So you’re saying the explanations run long and people check out before we start, is that right?” He nods. She asks for a specific: “Was it the whole setup, or one game in particular?” It turns out it is mainly the longer strategy games. She reflects it back, thanks him, and closes with, “Thanks, let me think about how to tighten that.” On the walk home she decides the note is fair and worth acting on. The same sharp comment that could have started an argument turned into something she can actually use, and the only reason is that she stayed steady long enough to receive it well.

Now you run the sequence yourself.
The setup. You help coordinate a community choir. After a rehearsal you helped lead, another member says, a bit bluntly and within earshot of a few others, “You kept us on that one song way too long, and we ran out of time for everything else.”
Your task. In a few lines, write the steady-and-receive response you would actually give in the moment. Include three things:
one short line that buys you a pause instead of a reflex reply;
one specific-example question that turns the comment into something concrete;
a “let me think about it” style close that acknowledges the feedback without committing you to anything on the spot.
Write it in your own words, from your own read of the moment, rather than asking an AI tool to draft it for you. Staying steady and running these moves is the exact skill you are building here.
The reply that arrives in the first two seconds is usually the reaction talking, not you.
Staying steady means notice the reaction, pause, name the feeling to yourself, then respond; it is not suppressing the feeling.
The core receiving moves are ask for a specific, get curious, reflect back, and decide later.
“Thanks, let me think about that” is a complete response that commits you to nothing.
A simple three-line frame, hear it back, ask for a specific, and take it away, works in almost any feedback moment.
That wraps up the receiving side: you can now take a hard comment without letting your defenses run the show. A short self-check quiz comes next, and then Part 2 turns to the active side, where you will learn to give feedback clearly with a model called SBI and to work through disagreements when a team pulls in different directions.