Blog/9 min read

What to do with what a stranger just said

A stranger just answered you. CARE helps you follow up: Catch what they said, Aim at a useful thread, Respond with interest and Extend the conversation.

A person considering different responses to a conversation

You did the hard part. You noticed someone, you moved toward them, you said the thing. They answered. Now you have about two seconds to respond, and what you do in those two seconds decides whether this becomes a conversation or dies right here.

If you've read the REACH model, this is the C in it, the Continue phase. It's a phase where a lot of stranger conversations quietly die. Not necessarily at the opener. Not at the first awkward silence. Right here, in the moment where they've said something and you have to say something back.

The problem isn't usually that you don't know what to say. You know several things you could say. The problem is that in those two seconds, most of us default to responses that look reasonable but end the conversation. Understanding why that happens, and what to do instead, is the whole point of this piece.

Four responses that can stop a conversation

Shelly Gable and colleagues published a paper in 2004 on what happens when someone shares good news. They identified four ways people respond, and only one of them actually builds the relationship. Their work was about good news specifically, but the shape of it holds for ordinary conversational answers too.

Three of the four failures below come from that research. The fourth comes from somewhere else.

The dropped response. They said something, you said "cool." One word, no engagement, nothing offered back. This is a very common failure, and it kills the conversation immediately. Not because "cool" is rude, it isn't, but because it signals no real interest in what they said. It closes a door that had just opened.

The muted response. Slightly warmer than dropped. "Oh nice, Wednesdays are good for that." You acknowledged the content, but you didn't pick up any thread, didn't ask any question, didn't offer any piece of yourself. The conversation is technically still alive, but it's not going anywhere. Both people feel they're stuck at the beginning of something that never quite starts.

The undermining response. You engaged with what they said, but you turned it into a critique or a complication. "After work? Isn't that when you should be resting?" Or: "This class gets so busy in winter, hard to keep up." You took their thread seriously, but you used it to disagree or point out a problem. They become defensive. The conversation goes negative or stalls entirely.

The self-shift. This one isn't in Gable's taxonomy, but it belongs here. You took their thread and used it as a springboard to talk about yourself. "I know what you mean, I always come on Thursdays because my schedule..." Their thread got abandoned. Occasional shifts are fine, you have to talk about yourself sometime, but if every response is a shift, the stranger feels like they're being talked over rather than talked to. Sociologist Charles Derber called this pattern "conversational narcissism" almost fifty years ago, and it still kills conversations today.

What keeps a conversation alive is the response that engages with what they specifically said, values it visibly, and moves things forward. Gable called this an "active-constructive response," and it's the one style in her taxonomy that consistently predicted better outcomes. The capitalization literature has been built on substantially since.

The question is how to reliably produce one. That's what the four moves are for.

How to keep a conversation going with CARE

Everything from noticing what they said to giving the conversation somewhere to go decomposes into four moves. Naming them makes them easier to hold on to when you're in them.

C, Catch. Notice what's in what they said. Every answer to a stranger's opener contains more than one thing. There's the content, the literal facts. There's usually a thread or two, specific words or details you could grab onto. There's often a feeling under the words. And there's usually some volunteered material, things they mentioned without being asked, which are worth noticing because they signal what's on their mind.

You don't need to consciously catalog all of this. You need to notice at least one specific thread and at least one piece of volunteered material. That's enough to work with.

A, Aim. Which thread do you respond to? Four selection criteria, roughly in order of importance:

Volunteered over asked-for. Things they mentioned without being asked are more revealing.
Specific over abstract. Concrete details are richer than generic ones.
Feeling over pure fact. Emotional threads invite more depth than logistical ones.
Their focus over yours. What did they seem to want to talk about? Follow their pull.

Combining these usually narrows the field to one obvious choice. If two threads tie, either works.

R, Respond. Engage with the specific thread you chose in a way that shows you understood and valued it. This is the acknowledgment piece: your reply has to make clear that you actually caught what they said, and that it landed.

Weak: "Cool." (didn't engage)
Weak: "Oh nice." (acknowledged but didn't engage with the specific thread)
Better: "Getting out is half the battle." (engages the thread, validates it)

Whatever form your response takes, it needs to be active-constructive: engage with the specific thread, show you understood it, value it visibly. This is what makes the response feel like a real answer rather than a token.

E, Extend. Give the conversation somewhere to go past your response. Add something small that opens a new door: a follow-up question about the same or a related thread, a small offering about yourself that invites them to ask back, a reflection that invites more.

The failure mode Extend addresses: you responded well, but your reply was terminal. It engaged with what they said, but it didn't give them anywhere to go. The conversation ends politely and quickly.

Terminal: "Getting out is half the battle."
Extended (question): "Getting out is half the battle. How did you land on this class?"
Extended (share): "Getting out is half the battle. I'm the same on Thursday mornings, that's my one mid-week thing."
Extended (reflection): "Getting out is half the battle. I keep noticing how much energy the leaving takes."

In practice, Respond and Extend usually happen in the same utterance. The response engages with what they said, the extension adds forward momentum, delivered together. But naming them separately lets you catch the specific failure mode of responding well and still leaving the other person with nowhere to go.

Examples of follow-up questions and responses

At the gym

Your opener: "First time in this class?"

Their answer: "No, I come most weeks. It's the one thing that gets me out of the house on Tuesday nights."

Catch. Content: weekly class, Tuesday nights, hard to get out of the house. Threads: "most weeks," "gets me out," "Tuesday nights." Feeling: getting out is a struggle, and this class is a small victory over that. Volunteered: everything after "no" was offered without being asked.

Aim. "Gets me out of the house" is volunteered, specific, emotional, and clearly on their mind. Right thread.

Respond. Engage the thread: "Getting out is half the battle."

Extend. Give it somewhere to go. A question: "How did you land on this class?" A share: "I'm the same on Thursday mornings, that's my one mid-week thing." Or a reflection that invites more.

Combined: "Getting out is half the battle. How did you land on this class?"

Compare to the failures: "Cool" (dropped, no Respond), "Nice, Tuesdays are good" (muted Respond, no Extend), "Yeah, but the winter classes get crowded" (undermining), "I always go on Thursdays because my work schedule is..." (self-shift), or "Getting out is half the battle." said and then nothing (good Respond, no Extend, conversation ends politely).

At the coffee shop

Your opener: "Is that book any good?"

Their answer: "Yeah, I'm actually rereading it. First time was in college and I remembered nothing, so I wanted to try again with a different brain."

Catch. Content: rereading, first read in college, "different brain" now. Threads: "rereading," "different brain," the reference to college. Feeling: curiosity about their own past self, a small self-aware observation. Volunteered: everything after "yeah."

Aim. "Different brain" is volunteered, specific, emotional, and philosophically interesting. Right thread. "Rereading" is a good runner-up.

Respond. Engage the thread: "Different brain is such a good way to put it."

Extend. Give it somewhere to go. A question: "Are you getting different things out of it this time?" A share: "I keep meaning to reread things for exactly that reason." Or an opening reflection.

Combined: "Different brain is such a good way to put it. Are you getting different things out of it this time?"

Why feeling heard helps people connect

Harry Reis and Phillip Shaver proposed in 1988 that what makes people feel connected in a conversation isn't the topic or the wit or the amount of talking. It's whether they perceive their partner as responsive. They named three components: the sense that the partner understands what you're saying, validates it, and cares about you. Decades of subsequent research have supported this. When those three components are present, people feel heard. When any are missing, they feel dropped.

The Catch-Aim-Respond-Extend moves are how you produce those three components in real time. Catching shows understanding, you noticed the specific things they said. Aiming well shows validation, you picked the thread that mattered to them. Responding actively and constructively shows caring, you engaged rather than just tolerating. Extending, adding forward momentum past your response, is what keeps the conversation alive long enough for the connection to develop.

You don't have to think about any of this consciously in the moment. The mechanics of the four moves produce the effect. It works even when the stranger doesn't know it's working.

Practise responding without following a script

The four moves are a map, not the territory. In practice, Catch and Aim often happen in the same half-second, faster than you can consciously separate them. Respond and Extend usually happen inside the same utterance. Sometimes the right thread jumps out before you've catalogued anything. Sometimes you'll respond to the wrong thread and it'll still land fine. Sometimes their answer has nothing much in it and the right move is a warm reaction and a beat of silence, with no extension needed.

The value of naming the moves isn't that you'll walk through them each time. It's that when a stranger conversation dies in the Continue phase, you now have four specific places to check: did I catch what was actually in their answer, did I aim at a thread worth responding to, did I respond in a way that engaged that thread, or did I forget to extend past my response and leave them nowhere to go? Hold the model loosely. Use the parts that help.