Case Study 01: Sam's Resistance Map

The Situation

Sam Nguyen, 35, is an operations manager at a mid-sized logistics company. He has a performance conversation scheduled with Tyler, one of his direct reports, for Thursday at 2 PM.

Tyler, 28, is intelligent, resourceful, and genuinely good at certain parts of his job — particularly the client-facing work where his energy and enthusiasm are assets. But for the past four months, Tyler has been consistently missing internal deadlines on process documentation — the unglamorous, necessary backend work that keeps Sam's team coordinated. Three times in the last two months, Sam has had to scramble to cover for Tyler's missing documentation. The most recent instance cascaded into a weekend phone call with Marcus Webb, Sam's boss, that Sam does not want to repeat.

Sam told Tyler two months ago, informally, that documentation was becoming a concern. He said it once, gently, without follow-up. Tyler nodded, said he understood, and then continued missing deadlines.

Now Sam needs to have the real conversation: direct, documented, with expectations clear enough to be measured. He is not firing Tyler. He is not putting him on a formal performance plan yet. He is having the conversation that, if ignored, will eventually lead to one of those two outcomes. Sam knows this is the moment that matters.

He is also anxious about it.

Tyler does not react well to feeling criticized. Sam has seen him get defensive in team meetings when feedback is directed at him — once going very quiet, once becoming animated and argumentative. Sam does not know which version of Tyler he will get on Thursday, or whether there is a version that is neither of those.

On Wednesday evening, Sam opens his laptop and starts building a resistance map.

Building the Resistance Map

Step 1: Likely Statements of Resistance

Sam forces himself to be honest. He lists what Tyler is actually likely to say — not the smooth, reasonable Tyler of his optimistic imagination, but the Tyler he has actually observed in stressful situations.

Looking at the list, Sam notices something: options 4 and 5 are the most likely. Tyler's pattern in high-threat situations is either to shut down or to agree in a way that changes nothing. The argumentative version — options 2 and 3 — is possible but less common in one-on-one conversations with Sam. It tends to happen more in group settings where Tyler's status is more visibly at stake.

Step 2: SCARF Trigger Analysis

Sam reads back his SCARF analysis and pauses at the "You never said it was critical" row. There is something genuinely uncomfortable about this. He did say something two months ago — but gently, once, without follow-up. Was that clear enough to establish genuine expectations? He considers this honestly. The answer is: probably not as clear as it needed to be.

This is a significant discovery from the resistance map. Tyler's potential accountability shift ("you never said it was critical") has a partial point. Sam was not sufficiently direct two months ago. He is going to have to acknowledge that rather than steamroll past it.

Step 3: Worst-Case Interpretation

Sam writes this section and finds it genuinely uncomfortable to complete:

Tyler might hear this as: You're building a case to fire me, and this conversation is step one of that process.

Tyler might think my motive is: I've already decided Tyler isn't working out and I'm looking for justification to move him out.

Tyler might fear that this means: My job is at risk. This will go in a formal file somewhere. The other people on the team will find out.

Sam looks at what he has written. None of it is what he intends. But he can see clearly how a person who has experienced workplace ambiguity before — and Tyler, Sam knows, had a bad exit from his previous job — would overlay those fears onto this conversation. They are not paranoid interpretations. They are reasonable worst-cases for someone who doesn't have visibility into Sam's actual thinking.

This tells Sam something specific: he needs to address the stakes question directly at the start of the conversation. Tyler needs to know what this conversation is and is not before his threat system locks in on the worst possibility.

Step 4: The Legitimate Concerns

The legitimate concern underneath "hollow agreement" stops Sam in his tracks. He had not thought about this before. If Tyler has been saying he'll fix the documentation and then not fixing it, the obvious interpretation is that he doesn't care enough. But another interpretation — one Sam had not genuinely considered — is that Tyler doesn't know how to fix it. He may not have been adequately trained on the documentation systems. He may not understand the downstream impact, which would tell him why it actually matters. He may be agreeing without having any clear picture of what change actually looks like.

Sam adds a note: in the conversation, he needs to ask not just "will you fix this?" but "do you know what it looks like to fix this?" These are different questions with different answers.

Step 5: What Tyler Needs to Feel Safe

Tyler needs to feel: That this conversation is about specific behaviors and their impacts, not about his character or his future at the company.

Tyler needs to know that: This is not a formal performance process. This is a direct conversation designed to fix something before it needs to become formal.

Tyler needs the conversation to preserve: His identity as a capable, motivated employee — someone who gets called out because he can do better, not because he is on the way out.

Pre-Emptive Empathy Statements Sam Prepares

Armed with his map, Sam drafts three pre-emptive empathy statements to open the conversation:

On the stakes: "Before we get into specifics, I want to be clear about what this conversation is. It's not a formal performance conversation. There's no file being opened. I'm having it because I think you're capable of this work and I want to fix something before it needs to get formal. I should have been clearer two months ago when I raised this, and part of why we're here is that I wasn't direct enough then."

This single statement addresses certainty threat (what is this conversation?), fairness threat (he acknowledges his own role in the ambiguity), and status threat (capable — I believe in you).

On recognition: "I also want to acknowledge the Q3 reporting work. You delivered on that, and I don't want this conversation to erase that in either of our minds. What I want to talk about is specifically the process documentation — and the pattern over the last four months."

This addresses the status threat and preempts the whataboutism. By bringing the Q3 work up himself, Sam prevents Tyler from having to defensively raise it.

On the autonomy question: "I'm not here to tell you how to manage your time. I want to understand your perspective on what's been happening, and I want to be direct about the impact. Then I want us to figure out together what needs to change."

The Response Pockets Sam Loads

For "client work comes first": Anchor: "You're right that client work is the priority — absolutely." Redirect: "The documentation question isn't about whether clients come first. It's about the specific downstream impact on the team when it's missing. Let me walk you through what happened with the Martinez file."

For "you never said it was critical": Sam decides not to use an anchor-and-redirect here. He decides to own this directly: "That's a fair point. When I raised this two months ago, I wasn't direct enough about the severity. That's on me. I'm being clearer now."

For withdrawal: If Tyler goes quiet: "I notice you've gotten quiet. That's okay — I know this is a lot. I want to make sure you feel like you can say what you're actually thinking. What's going through your mind right now?"

For hollow agreement: "I'm glad you're open to this. I want us to get specific before we close — what does 'being more careful' look like in practice? What would I see that's different by the end of next week?"

The Conversation: Thursday, 2 PM

Tyler comes in slightly guarded. Sam starts with his pre-emptive empathy statement about the stakes. He watches something shift in Tyler's face — a slight release of tension that tells him the certainty intervention landed.

Tyler does bring up the Q3 project — but Sam has already acknowledged it in his opening, so Tyler's mention of it is not defensive. It's confirmatory. "Right, I know — and I appreciate that. So what specifically is the issue?"

Sam walks through the four documentation failures in detail. Tyler's response starts as minimization ("I didn't think this one was that critical...") and Sam uses the anchor-and-redirect: "I hear you — and let me tell you what the impact was on the team, because I don't think you have visibility into that downstream." He describes the weekend call with Marcus Webb. Tyler looks genuinely surprised. He had not known about the call.

This is the turning point. Tyler had not understood the actual impact. His minimization was genuine — he did not know. Sam's map had identified "doesn't understand the downstream impact" as a legitimate concern, and now it is confirmed. This is not moral failure on Tyler's part; it is an information gap.

Tyler goes quiet after this — not the resistant withdrawal Sam had anticipated, but a processing silence. Sam waits.

"I didn't know it went up to Webb," Tyler says.

"No, I know you didn't. I should have told you sooner."

They spend the next twenty minutes getting specific: Tyler explains the documentation difficulty is partly about the system — the current tool is genuinely cumbersome and he has been spending twice as long on it as he should. Sam makes a note to look at this. They agree on three commitments: Tyler will complete the overdue documentation by Monday, Sam will schedule a meeting to reassess the documentation tool's usability with the team, and they will check in briefly every Friday for four weeks.

Tyler leaves looking more settled than he arrived. Sam closes his laptop.

The conversation was not what he had prepared for. Tyler had not been argumentative or given hollow agreement. The real issue — the one Sam had discovered in the legitimate concerns section of his map — turned out to be the center of the conversation: Tyler had not understood the impact, and the tool was a genuine obstacle.

Sam's preparation had been for every version of the conversation except the one that actually happened. But because his preparation had included asking "what is the legitimate concern underneath each form of resistance?", he arrived with the mindset to hear Tyler's real problem rather than defend against his anticipated resistance.

That is what resistance mapping is for. Not to predict the conversation exactly. To arrive with a wide enough map that the real territory doesn't leave you without direction.

Discussion Questions

1. Sam discovered during resistance mapping that Tyler's "you never said it was critical" would have a legitimate point. How should an initiator handle it when resistance mapping reveals that their own actions contributed to the problem? Does acknowledging this reduce their credibility or strengthen it?

2. Sam prepared for Tyler's withdrawal response but the conversation went differently — Tyler went quiet as a processing signal, not a defensive one. How do you distinguish between these two types of silence, and what is the risk of misreading a processing silence as a resistant one?

3. The most important discovery in Sam's resistance mapping was the "hollow agreement" row — where Sam realized Tyler might not know what change actually looks like. What does this tell us about the risk of preparation that focuses only on the other person's defensiveness rather than also examining our own communication gaps?

4. Sam chose to own the fairness concern directly rather than using anchor-and-redirect. When is full ownership of a concern more effective than the anchor-and-redirect? What makes the difference?

5. The case ends with Sam noting that his preparation was for every version of the conversation except the one that actually happened — but that the mindset of preparation still served him. What does this suggest about the relationship between preparation and flexibility in difficult conversations?