Case Study 28-1: Sam, Elena, and Marcus — Three Confrontations, One Turning Point

Category C: Practical Walkthrough

This case study follows Sam Nguyen through the three workplace confrontations that mark the culmination of his arc in this textbook: with his subordinate Tyler, his peer Elena, and his boss Marcus Webb. We trace each conversation in detail, annotate the decisions against the chapter's frameworks, and analyze what made the sequence transformative despite none of the individual conversations being a triumph.

Background: Fourteen Months of Treading Water

Sam Nguyen is thirty-five, an operations manager at a mid-sized logistics company, and has been passed over for promotion twice in four years. He manages a team of six. His boss, Marcus Webb, is avoidant and politically skilled. His peer Elena is competitive, respected, and has informal influence with the VP of Operations that Sam lacks. His subordinate Tyler is smart, capable, and chronically avoidant about deadlines.

Sam's pattern across all three relationships has been the same: he perceives a problem, ruminates about it for days or weeks, waits until the problem is undeniable, has a conversation that feels productive, accepts vague reassurance as resolution, and watches the problem continue. He has been doing this for four years.

His partner Nadia, who as a therapist is professionally required to model patience, has told him: "At some point, the thing that's getting in your way is you."

Sam knows she's right. This knowledge has been available to him for approximately three years and has not, so far, produced action.

The sequence of events described in this case study happens in the six weeks following his first genuinely productive conversation with Tyler (Chapter 26). Something shifted in that room — not Tyler's behavior, exactly, but Sam's sense of what was possible when he didn't exit at the first sign of resolution.

Confrontation 1: Tyler (Downward Axis)

(Detailed in Chapter 26; summarized here for context)

Sam's performance conversation with Tyler was the first of the three. The key moves:

• Sam opened by naming the meta-level goal: not "let's settle this" but "let's figure out what would actually work."
• He conducted a cause inquiry before stating expectations, which surfaced Tyler's real obstacles (priority confusion, fear of early disclosure).
• He used the agreement checklist to close: specific, actionable, realistic, addressed the real issue, accountability built in.
• He sent a follow-up email within two hours.

Three weeks later, the Friday status updates were largely holding. Tyler had missed one (at noon) and submitted it at 2:30; Sam had texted and Tyler had acknowledged; the following week was on time.

What this gave Sam: A concrete example of what happened when he didn't accept "are we good?" as a closing. The proof-of-concept. He still had the Nadia-note taped to the back of his phone: When it feels like it's over, that's when you have to keep going for two more minutes.

Confrontation 2: Elena (Lateral Axis)

The Situation

Elena Vasquez is Sam's peer on the operations floor. She is approximately equally powerful on the formal org chart. She has been at the company eleven years (Sam: four). She has lunch with the VP of Operations every other Thursday. She is good at her job and she knows it.

The problem: In three consecutive cross-functional planning presentations to the broader leadership team, Elena had presented analysis that Sam's team had built — including, in the most recent case, a competitive landscape analysis that Sam had spent an entire weekend compiling. Elena's presentations credited "the operations team" in a general footnote. Sam's name did not appear.

Sam had noticed this the first time and told himself it was normal synthesis. He had noticed it the second time and begun to seethe. By the third time, he was carrying a low-level resentment that was starting to affect how he felt about coming to work.

He had three instincts, in order of likelihood before the Tyler conversation had shifted something: 1. Say nothing, feel resentful, let it harden into a stone in the wall. 2. Bring it to Marcus. 3. Say something to Elena.

The Decision to Go Direct

The chapter's peer confrontation protocol says: don't go to the boss first. Sam knew this intellectually. He also knew that going to Marcus would achieve one thing immediately: it would make him look like he couldn't manage a peer relationship without management intervention. Marcus would probably handle it with characteristic avoidance — a general conversation about attribution practices that wouldn't change anything and would make Elena aware Sam had gone to the boss.

He asked Elena if she had twenty minutes. She said yes; they found a conference room.

The Opening

Sam had prepared the opening. He didn't start with "I want to talk about the presentations" — he started with the shared goal.

"I want to talk about how we're handling analysis in the cross-functional presentations. I think we both want to show leadership what the operations function is capable of, and I'm wondering if there's a better way to handle attribution that reflects the full team."

Annotation: This opening does several things. "We both want to show leadership what the operations function is capable of" is accurate and flattering to Elena's work — she genuinely does want this. It frames the conversation as shared professional interest rather than grievance. "Attribution that reflects the full team" is the specific issue without the accusation.

Elena looked at him carefully. "What are you thinking?"

The Behavioral Statement

"In the last three presentations, analysis that came from my team — and in one case, from me specifically — appeared without attribution to my team. I don't think you were trying to claim it; I think it's a presentation style thing. But it matters to me, and I think it matters for how our team is perceived by leadership."

Annotation: Sam is doing something important here: he's separating the behavior ("analysis appeared without attribution") from the interpretation ("I don't think you were trying to claim it"). The distinction prevents Elena from spending the conversation defending her intent and keeps the focus on the behavior. He's also named why it matters to him — "how our team is perceived by leadership" — which is a shared interest.

Elena was quiet for a moment. "I didn't think about it that way. I was treating the analysis as team output, not individual output."

"I hear that," Sam said. "I'd like us to think about it differently. When I've built something that's being presented to the leadership team, I'd find it meaningful to have that reflected — either my name, or the operations analysis team specifically."

The Agreement

They landed on something concrete: cross-functional presentations drawing on specific analysis would include a source attribution slide ("Data/Analysis: [Team Name] — [Contact Name]"). It was a small thing. It was also the thing Sam needed.

"That seems fair," Elena said. "I honestly hadn't thought about it as a credit issue. I'll build it into my deck template."

After the conversation, Elena sent Sam a message: "I think this is actually a better practice for everyone. I'm going to suggest it to the cross-functional group."

Annotation: Elena's response suggests two things: (1) the grievance was real, but her behavior wasn't malicious — it was default; changing defaults is addressable through a direct conversation. (2) The collaborative framing worked: Elena had not been put in the position of being wrong, only of adopting a better practice. She was able to own the improvement rather than defending against the accusation.

What happened after: The following cross-functional presentation included a source attribution slide. Sam's team was listed. Sam sent a brief follow-up email after their conversation confirming what they'd agreed. Elena responded positively.

Sam did not go to Marcus. The conversation took twenty minutes.

Confrontation 3: Marcus (Upward Axis)

The Situation

Sam worked forty hours on the Q3 operations analysis — the competitive landscape, the vendor risk assessment, the operational efficiency recommendations. He sent it to Marcus on a Friday afternoon. The following Tuesday, Marcus presented it to the executive team. Marcus's email to the team afterward thanked Sam for his "contributions to the underlying data."

Contributions to the underlying data.

Sam read the email three times. He felt something that was not quite anger and not quite betrayal but lived near both.

He had counted the steps to Marcus's office: twelve. He had been counting them, mentally, for four years.

The Preparation

Sam did what he'd learned to do. He asked himself four questions from the chapter's pre-confrontation checklist:

1. Is this a pattern or an isolated incident? It was a pattern — Marcus routinely presented upward without including Sam, and had done so three times in the previous year.
2. Is this affecting my work in a concrete ongoing way? Yes: his development, his visibility with leadership, and the promotion consideration that ran through this man.
3. Can I articulate what I need differently? Yes: to be in the room when analysis he'd built was being presented.
4. Am I prepared for the worst-case response? He thought about this. The worst case was Marcus dismissing the concern, or — worse — being offended and distancing himself. Sam had been afraid of this for four years. He was less afraid of it now than he was four weeks ago, for reasons he couldn't fully articulate.

He prepared the solution-presenting frame.

The Walk Down the Hall

Sam knocked on Marcus's open door.

"Do you have a few minutes? I want to talk about the executive presentation."

Marcus looked up. "Sure. Come in."

Sam sat down. "I was really glad it went well." He meant this. "I've been thinking about how we handle executive presentations that draw on analysis I've built. I think there's an opportunity for me to add real value in the room — I can field technical questions in real time, and it would be valuable development for me. Is that something we could discuss?"

Annotation: The solution-presenting frame in action. Sam is not saying: "You presented my work as yours." He is not saying: "I felt undermined." He is saying: "Here's a way this could work better, and here's the benefit to you and the organization." Marcus does not have to acknowledge wrongdoing to respond positively to this.

The frame is honest. Sam genuinely believes he could add value in the room. He genuinely wants the development. The framing is strategic, not dishonest — he has chosen the frame that makes it easy for Marcus to say yes rather than the frame that makes Marcus feel accused.

Marcus looked at Sam for a moment. Not with warmth, exactly — Marcus was not a warm man — but with the particular attention he gave things that required him to recalibrate.

"Yeah," Marcus said. "That makes sense. Let me think about how to structure that."

It was not an apology. It was not an acknowledgment of what had happened. It was a door opening.

The Follow-Through

The following week, Marcus forwarded Sam an invitation to a follow-on conversation with the VP of Operations about the Q3 findings. The invitation included a note: "Sam can walk through the methodology if there are technical questions."

Three weeks later, Marcus included Sam in a second executive briefing. Sam had said: I think I could add real value in the room. Marcus had made that true.

Five Weeks Later: The Consideration

Marcus called Sam into his office on a Thursday afternoon. "There's a regional director search opening up. I'd like to put your name in."

Sam sat with this. He thanked Marcus. He asked what the role involved. He asked when Marcus needed a decision.

He left Marcus's office with the strange, new feeling of not being certain whether to feel vindicated or afraid. Both, maybe. The vindication was real: four years of treading water, three conversations in five weeks, a door he hadn't been sure would ever open. The fear was real too: he was being asked to step into a role that would require him to do everything he'd been doing better, in a bigger context, with more at stake.

The question he couldn't answer: was the promotion the result of the conversations, or had it been coming anyway and the conversations were incidental?

He called Nadia that evening. She asked the same question back to him.

He sat with it. "I don't know," he said finally. "But I know the conversations were real, whether or not they caused it. And I know I couldn't have had them a year ago."

Nadia said: "That's the part that matters."

Analysis: What Made the Sequence Work

The Interconnection of All Three Axes

Sam's three confrontations are not independent events — they reinforce each other in a way that makes the sequence more powerful than any individual conversation.

The Tyler conversation established the proof-of-concept: closing past "are we good?" produces something real. This gave Sam the confidence to initiate with Elena. The Elena conversation demonstrated that direct peer confrontation — without going to Marcus — could produce change and actually improve the relationship. This gave Sam the courage to walk down the hall. The Marcus conversation demonstrated that the solution-presenting frame could accomplish what direct complaint would not.

Each conversation made the next more available. This is not the typical experience of workplace confrontation, which tends to be treated as isolated crises rather than a developing competence. Sam developed across the sequence.

The Consistent Application of Preparation and Frame

In every conversation, Sam: - Prepared specifically (named the pattern, identified the interests, selected the frame) - Opened with the shared goal or the collaborative frame - Addressed behavior, not character or intent - Made a specific ask rather than a general complaint - Left with a specific agreement or a specific next step - Followed up in writing

The consistency is what made the results consistent.

What Didn't Change

Tyler is still Tyler. Elena is still Elena. Marcus is still Marcus. None of Sam's conversations produced a transformation in the other person. Tyler's avoidance pattern is managed, not eliminated. Elena's competitive instincts are unchanged; the attribution practice is changed. Marcus is still a political animal who takes the work of his direct reports to the executive floor without necessarily thinking twice about it; he now includes Sam in certain follow-on conversations.

These are not trivial changes. But they are not character transformations. The chapter's implicit argument — and the case study's — is that durable behavioral change is a more realistic and more useful goal than character transformation. You are not trying to change who Tyler, Elena, and Marcus are. You are trying to change what they do in specific contexts. That's within reach.

Discussion Questions

1. Sam's three confrontations each use a different approach (performance conversation, peer collaboration frame, solution-presenting frame). What determines which approach is appropriate in each case? Formulate a decision rule.

2. The case study describes Sam's "proof-of-concept" from the Tyler conversation as the foundation for the Elena and Marcus conversations. What is the psychological mechanism here — why would a successful confrontation in one context increase capacity in a different context?

3. Marcus's response to Sam's solution-presenting frame is "that makes sense — let me think about how to structure that." He doesn't apologize, doesn't acknowledge the attribution issue, doesn't show warmth. Sam accepts this as success. Is he right to accept it? What would he have gained from a more explicit acknowledgment, and what would he have risked?

4. Elena says — after agreeing to the attribution practice — "I think this is actually a better practice for everyone." What does this response suggest about the relationship between collaborative framing and the other party's ownership of the changed behavior?

5. Sam can't answer whether the promotion happened because of the confrontations, despite them, or something else. He concludes: "I know the conversations were real, whether or not they caused it." Is this a satisfying answer? What does it suggest about how we should think about the relationship between direct action and outcomes in complex organizational systems?

6. None of Sam's three confrontations was a triumph. All three produced something specific and real. Formulate a definition of "success" in workplace confrontation that accounts for this pattern — that is neither "everything I wanted" nor "nothing went wrong."