Case Study 24-01: Sam's Exit and Return
Background
Sam Nguyen is three weeks into a running tension with Tyler, a direct report who has been missing deadlines and offering explanations that Sam finds insufficient. Their first conversation (Chapter 22) ended when Sam recognized flooding and called a time-out. Their second conversation — the one documented in this case study — was supposed to be a fresh start. It was not.
The context: Tyler had missed a second delivery milestone on the operations reporting project. Sam had documentation. Tyler had been given clear expectations in writing. This was not a matter of disputed facts — it was a matter of Sam needing to understand why the timeline kept slipping and what would be different going forward.
Sam came in prepared. He had reviewed Chapter 21's de-escalation techniques, had practiced opening without accusation, had the documentation at hand but had decided not to lead with it. He was going to stay curious. He was going to stay regulated.
This plan lasted approximately four minutes.
The Conversation: What Went Wrong
Sam: "Tyler, I wanted to circle back on the reporting project. The Tuesday milestone was missed again, and I need to understand what's happening."
Tyler: "I know. I've been buried. The Martinez account needed emergency attention, and I made a judgment call."
Sam: "I hear that. The thing is — this is the second milestone. I need to know we can rely on this timeline. What's your plan for catching up?"
Tyler: "The same plan I've had. I'm doing everything I can."
Sam: "That's not specific enough. I need a concrete plan."
Tyler: (long pause) "I feel like no matter what I do, it's not right."
This line — "no matter what I do, it's not right" — landed on Sam in a way he had not anticipated. There was something in Tyler's tone that Sam read as contemptuous: the implication that Sam's expectations were unreasonable, that Sam was the problem. Whether Tyler intended that implication is debatable. That Sam heard it is not.
Sam: "That's not fair. I've been flexible with you. The expectations haven't changed."
Tyler: "You keep saying the expectations haven't changed, but the goalposts keep moving."
Sam: "The goalposts haven't moved. The project scope is the same as it was on day one."
Tyler: "That's not true."
Two words. Very quiet. And Sam felt something shift in his chest — a tightening, a flash of heat. He knew this feeling from Chapter 22: this was the edge of flooding. He was not flooded yet. He was close.
Sam: "I have it in writing, Tyler. The scope hasn't —"
Tyler: "I'm not saying the written scope changed. I'm saying what's expected of me day to day isn't what was described."
Sam: "Then you should have raised that before the first missed deadline."
Tyler: "I tried to. In the September meeting."
Sam: "I don't remember that."
Tyler: "I know."
Another two words. They hit differently from the first pair. "I know" — as in, I know you don't remember, and I've stopped expecting you to. The implication of someone who has given up on being heard was, paradoxically, louder than anything Tyler had said at volume. Sam felt the heat rise further. He was about to say something he could not take back. He could feel the sentence forming — something about Tyler's attitude, something about what happened in September that Sam now remembered differently, something that would shift this conversation from a performance issue to a personal conflict.
He stopped.
He stopped because he recognized what was happening. He was flooded. And Chapter 22 had been very clear: a flooded person cannot have this conversation productively. Every word he said now would be from his activated nervous system, not from his prefrontal cortex. Anything he said now would make things worse.
The Exit
Sam: (pauses, takes one deliberate breath) "Tyler. I need to stop here."
Tyler: (a slight defensive stiffening) "Okay."
Sam: "Not because this conversation is over. I can hear that you've been frustrated for a while, and I need to take that seriously. But I'm not in a state right now where I can do this conversation justice, and I'd rather stop than say something I'll regret."
Tyler: "All right."
Sam: "Can we come back to this on Thursday? I'll send a calendar invite for two o'clock. Is that workable?"
Tyler: "Yeah. That works."
Sam: "I appreciate your patience with me on this. I mean that."
He stood. He left.
What Sam Did in the Interval
Sam spent twenty minutes after the exit sitting in his car in the parking garage. He did not check his phone. He practiced the physiological self-soothing that Chapter 22 described: slow breathing, deliberate muscle release in his jaw and shoulders, not rehearsing the argument. After twenty minutes, his heart rate had settled.
That evening, he did three things:
First: He wrote down what had actually happened — not his interpretation of it, but the sequence of exchanges. He was particularly careful about Tyler's "I know" moment: when he wrote it out, he could see that Tyler's "I know" was ambiguous. It could mean "I know you don't remember, and I've stopped trying to be heard" — which was contemptuous. It could also mean "I know — of course you don't remember, because you were running another meeting and I only raised it briefly" — which was factual and resigned rather than dismissive. He could not tell from memory. He had to hold the ambiguity.
Second: He wrote down his own contribution to the deterioration. This was harder. He had come in prepared and regulated. But: he had escalated when Tyler questioned his memory. He had said "I have it in writing" in a tone he now recognized as contemptuous — the implication being that documentation made Tyler's recollection irrelevant. He had not asked a genuine question since the third exchange. He had moved from curiosity to interrogation and had not noticed the moment of transition.
Third: He reviewed what he actually needed from the conversation. It was not to win an argument about September or scope creep. It was to understand why the timelines were slipping and to establish a realistic path forward. He had lost track of that purpose entirely by the sixth or seventh exchange.
On Wednesday evening, Sam sent a brief message to Tyler:
"Looking forward to picking this back up tomorrow. I've been thinking about our conversation. I want to make sure we're actually getting to what matters rather than getting stuck on the other stuff. See you at 2."
Not elaborate. Not apologetic in a way that undermined his position. Just a signal that he had been thinking, and that the conversation was not finished.
The Resumption
Thursday, 2:03 PM.
Sam: "Hey. Thanks for making time."
He sat. He did not open with the documentation. He did not open with the reporting project.
Sam: "Before we get into the project — I want to say something about Tuesday. I think that conversation went sideways pretty fast, and I think I contributed to that. When you said the scope felt different day to day, I immediately went to my documentation instead of asking what you were actually experiencing. That was defensive of me, and it wasn't useful."
Tyler looked at him. Not entirely open. Cautious. But present.
Sam: "I also want to say — I don't know if the September conversation happened the way you remember it, and I don't know if it happened the way I remember it. I'd rather not get into that. What I do know is that you came in Tuesday feeling like you weren't being heard, and I didn't do anything to help with that."
Tyler: "I appreciate that."
A pause. Sam let it sit.
Tyler: "For what it's worth — I know the deadlines matter. I'm not trying to make excuses."
Sam: "I believe you. I need to understand what's actually happening, though. Not to build a case — genuinely. Because if there's something in how the project is structured that's creating problems, I need to know that."
And this — this was the conversation they should have had on Tuesday. Tyler talked. Sam listened without composing his rebuttal. Tyler described a dependency on a data feed from another department that had been unreliable, a fact Sam had not known. He described the Martinez account emergency as something that had consumed two full days that he had not been able to recover. He described the September conversation — brief, in the middle of a larger meeting — as a moment when he had tried to flag the data feed issue and Sam had said "let's take that offline" and it had never been followed up.
Sam did not know if he remembered the September meeting that way. He chose not to contest it.
Sam: "Okay. So the data feed issue is real, and it's been affecting you since the start. That's something I can actually do something about."
Tyler: "That would help."
Sam: "What would a realistic revised timeline look like if we got the data feed stabilized?"
They spent forty minutes in that conversation. By the end of it, they had a revised timeline, an action item for Sam to address the data feed dependency with the other department, and a shared understanding of what had caused the slippage. The conflict was not fully resolved — trust had been damaged and would need to rebuild over time. But the actual operational problem had been identified and was now addressable.
Analysis: The Exit and the Return
Why the Exit Worked
Sam's exit was effective for three specific reasons.
First, he stopped before saying the thing he would regret. This is harder than it sounds — the sentence was forming. He had felt the impulse. He arrested it. The measure of the exit is not just that he stopped but that he stopped before causing the relational failure that would have required a much more costly repair.
Second, his exit language hit all three required components. The acknowledge component ("I can hear that you've been frustrated for a while") validated Tyler's experience without conceding Sam's position. The suspend component ("I'm not in a state right now where I can do this conversation justice") gave a specific, non-accusatory reason for stopping. The commit to return component (a specific day, time, and calendar invite) converted a vague promise into a concrete commitment. Tyler walked away from the exit knowing the conversation was not over — just paused.
Third, the appreciation at the end ("I appreciate your patience") was genuine. It was not a manipulation or a softener. It was a small repair attempt on the relational damage that the conversation had caused — a signal that Sam recognized Tyler had stayed regulated while Sam had not.
Why the Resumption Worked
The resumption succeeded because Sam did something difficult in the interval: he genuinely examined his own contribution to the failure rather than just managing Tyler's experience.
The specific acknowledgment he made — "I went to my documentation instead of asking what you were actually experiencing" — was precise enough to be credible. General acknowledgments ("I know I wasn't perfect") are often experienced as a form of getting credit for humility without doing the actual work. Sam's acknowledgment named a specific behavior and called it by name: defensive.
His refusal to re-litigate the September meeting was strategically and relationally sound. Whatever happened in September, getting certainty about it was not possible and was not the point. The point was the operational problem that had been named and not addressed. Sam chose the operational future over the documentary past.
The outcome — a revised timeline, an action item, a shared understanding — was only possible because the residue had been addressed first. If Sam had walked in on Thursday and opened with "okay, so the reporting project," he would have walked into a conversation still saturated with Tuesday's damage. The acknowledgment of the failed conversation was not courtesy. It was a prerequisite.
What Sam Would Do Differently
Sam's debrief, shared with his partner Nadia that evening:
"I lost curiosity too fast. I went in saying I was going to stay curious and I lost it by the fifth or sixth exchange. I need to figure out what the trigger was — whether it was the specific thing Tyler said or whether I had already started hearing him as adversarial before he gave me a reason to."
This observation matters. The most sophisticated repair work often points back to a failure that happened before the conversation deteriorated visibly — a moment of internal shift from "I'm here to understand" to "I'm here to establish what's true" that happened below the threshold of conscious choice. Sam's ability to identify that moment in retrospect is exactly the kind of post-conflict reflection that, over time, builds the self-knowledge to catch the shift earlier.
Reflection Questions
- At what point in the Tuesday conversation could Sam have made a repair attempt rather than needing a full exit? What would that attempt have looked like?
- Sam chose not to contest the September meeting in the resumption. Was this the right call? What are the risks of permanently leaving a factual disagreement unaddressed?
- Tyler's "no matter what I do, it's not right" was the line that triggered Sam's escalation. Analyze that line: how many different ways could it have been meant? How might Sam have tested his interpretation before reacting to it?
- The data feed issue — an operational problem Sam did not know about — was only discovered in the Thursday conversation. What does this suggest about the cost of Tuesday's failure to stay in curiosity?
- Sam's pre-resumption message to Tyler ("I want to make sure we're actually getting to what matters") signals intent without full disclosure. Is this the right level of pre-communication? Too much? Too little?