Case Study 1: The Wrong Conditions, Twice

Background

Sam Nguyen, 35, operations manager at a regional distribution company, had been building toward a difficult conversation with his boss, Marcus Webb, for nearly two months.

The issue was not complicated to diagnose: Webb had been loading Sam with operational responsibilities that properly belonged to a full team, had consistently failed to staff the team adequately despite promises, and had repeatedly interrupted Sam's scheduled planning time with emergency requests that weren't actually emergencies. Sam had been working twelve-hour days for six weeks. His partner Nadia had noticed. Sam himself had noticed — his sleep had deteriorated, he'd stopped going to the gym, and he'd started dreading Sunday evenings in a way he hadn't since his first year out of college.

Sam was not naturally conflict-averse, but he had a deep professional loyalty to Webb, who had mentored him earlier in his career and whom he genuinely liked. He kept telling himself that things would stabilize after the next project, after the Q3 report, after the new logistics software launched. They didn't stabilize. They got incrementally worse.

By the time Sam decided he genuinely needed to address the situation with Webb, he had accumulated eleven specific incidents he could cite, a list of broken promises he had written down in a notebook, and a level of emotional exhaustion that was beginning to affect his performance. He was ready to have the conversation. He was not, it turned out, ready to have it well.

Attempt One: Tuesday Afternoon

Sam's first attempt occurred on a Tuesday in early October. He had not planned it. He had been passing Webb's open office door — Webb was on his computer, seemingly between tasks — and something about the open door and the quiet moment triggered an impulse.

Sam knocked on the door frame. "Hey, Marcus. Do you have a minute?"

Webb looked up from his screen. "Sure, what's up?"

Sam came in, sat down across from Webb's desk, and began talking. He had rehearsed his key points a dozen times, but in the moment, sitting across from his boss's desk, in a space that was entirely Webb's territory, with Webb in the position of authority behind the desk, Sam felt the scaffolding of his preparation collapse.

He started with the Q3 shortfalls. Then he mentioned the team staffing issue. Then he found himself referencing something from August that he had promised himself he wouldn't bring up. He talked for about four minutes in a way that was not incoherent but was clearly nervous, disorganized, and building toward — Webb could feel this — some larger point that Sam hadn't quite arrived at.

Webb listened. He was a decent manager and he gave Sam full attention. When Sam paused, Webb said: "Sam, I hear you. These are real pressures. Can you send me a brief summary email of the staffing concerns? I want to make sure I have the details right before I bring it to leadership."

"Yeah, of course," Sam said. "Absolutely."

He went back to his desk and spent two hours drafting the email. When he sent it, Webb replied the following morning with a brief: "Thanks — let's find time to discuss." The time was never scheduled. Three weeks passed.

Analysis: What Went Wrong in Attempt One

Location and territory: The conversation occurred in Webb's office, at Webb's desk, on territory that was entirely Webb's. The desk itself — the physical arrangement with Webb behind it and Sam in front — replicated the standard power arrangement of a performance review or a disciplinary conversation. Sam was neurologically positioned as subordinate rather than peer. The fact that Webb was at his computer when Sam arrived meant Webb also had the option to half-attend to the screen, which further diminished Sam's perceived importance.

No request-to-meet: Sam walked in without warning, during what he perceived as a spare moment. Webb may have had something else he was about to do. He certainly wasn't prepared for a substantive conversation about staffing and workload. The absence of preparation on Webb's side meant he fell back on a managerial reflex: defer and document. "Send me a summary email" was not a brush-off — it was what you say when you're caught without context.

Sam's emotional state: By the time Sam walked through that door, he had two months of accumulated frustration. He had promised himself he would be calm and specific, and he was — barely. But the accumulated weight of those eleven incidents was present in his voice, in his scattered organization, in the August incident he hadn't meant to mention. Webb sensed an emotional weight he didn't have the context to interpret, which made him cautious.

No specific ask: Sam talked about the problem without articulating what he needed. He described symptoms but didn't arrive at a request. Webb's "send me a summary email" was partly an avoidance move, but it was also a reasonable response to a conversation that hadn't yet arrived at the question it was trying to ask.

Attempt Two: Friday Afternoon Instant Message

The email Webb requested sat in Sam's drafts folder for a week. Sam wrote three versions. Each time he reread what he'd written, it felt either too passive or too confrontational. He hit send on the third version on a Thursday evening at 9:30pm — not ideal timing for a significant workplace communication.

Webb read it Friday morning. He sent a brief reply: "Useful context. Let's get a call this afternoon — say 4?"

Sam agreed. At 4:15, Webb called. It was fifteen minutes late. Webb was on what sounded like a hands-free call in a car — Sam could hear traffic noise. Webb said: "I've only got about ten minutes, I'm heading to pick up the kids. Walk me through the main points."

Sam walked him through the main points. Webb said: "Yeah, look, these are real issues. Let me think about what we can do on the staffing side. I'll get back to you next week."

"Okay," Sam said.

Webb got back to him the following Thursday with an email saying there was no budget to add headcount this quarter but that he'd "keep an eye on the workload distribution."

Nothing changed.

Analysis: What Went Wrong in Attempt Two

Medium mismatch — the email: The initial email request had established a lean medium (written) as the venue for a complex, emotionally significant issue. This set up the phone call poorly — Webb read Sam's concerns through text, without Sam's tone or affect, and processed them in the way of someone reading a business problem rather than experiencing the weight of a relationship under strain.

Medium mismatch — the phone call: The phone call itself was a lean medium for a significant conversation. Sam needed to be able to read Webb's face — to know if his boss was genuinely engaging or performing engagement. He could not. Webb was also driving, which means a portion of his cognitive resources were actively engaged in a competing task. He was under a hard time constraint (picking up his children). Sam had ten minutes of a distracted, time-pressured half-attention.

Timing: The 4pm Friday call — especially with Webb driving — was functionally identical to Marcus's hallway moment. Webb's cognitive and emotional resources were committed elsewhere. His response to Sam's concerns was not considered; it was the kind of pat resolution that depleted people generate when they want to close out an issue before transitioning contexts.

No specific ask (again): Sam had again failed to arrive at a concrete request. He described the problem clearly, but "keep an eye on the workload distribution" is what you say when someone has described a problem without asking for a specific outcome. Webb couldn't commit to something specific because Sam hadn't named what specific thing he needed.

The Third Approach: What Sam Eventually Got Right

Nadia, Sam's partner, had been watching this unfold. She was not in operations and had no particular organizational psychology training, but she had clear eyes and genuine affection for Sam. "You've tried twice," she said one evening. "Both times you sort of... cornered him without setting it up properly. And you never actually told him what you needed from him. He doesn't know if you want more staff or a different project or to just vent."

Sam started over. He did several things differently.

Preparation: He went back to his list of incidents and reduced it to three concrete examples — not eleven. He identified specifically what he was asking for: a clear headcount commitment with a timeline, or an explicit mutual agreement that his current scope would be temporarily reduced. He was no longer asking Webb to "do something" about a vague problem. He was bringing a specific ask to a specific decision-maker.

The request to meet: Sam sent an email on Wednesday morning: "Marcus — I'd like to find 30 minutes this week or next to talk through the team capacity situation. I've thought about it carefully and I have some specific ideas I'd like your input on. When works best?" He was specific about the topic, specific about the time needed, framed it as collaborative (your input), and made it easy for Webb to say yes.

Webb replied within two hours: "Next Tuesday at 10 works — I'll block it."

Environment: Sam arrived in Webb's office at 10am on Tuesday. But this time, he had done something small and deliberate: when he sat down, he moved his chair to the side of the desk rather than directly across from it. He did this casually, claiming he needed to see a whiteboard. Functionally, it eliminated the across-the-desk arrangement that had reinforced a power dynamic Sam hadn't been able to overcome in his first attempt.

His emotional state: In the intervening days, Sam had done something that was uncomfortable but necessary: he had written out, in a private document he didn't share with anyone, everything he was angry about. He'd given himself permission to be as frustrated and accusatory as he actually felt — for two pages — and then he'd set it aside. Something about the private expression of the feeling reduced its pressure. He arrived at Tuesday's meeting nervous but not flooded.

The conversation was not easy. But it was real. Webb heard Sam's specific ask, asked clarifying questions, and committed to a specific answer by the following Monday. He came back Friday — two days early — with a concrete interim plan.

The conditions hadn't made Webb generous. But they had made both parties capable of real conversation. That was enough.

Discussion Questions

In Sam's first attempt, what specific environmental factors contributed to his failure to communicate effectively? How might the conversation have differed if Sam had chosen a conference room rather than Webb's office?
Compare Webb's behavior across both attempts. Is Webb a bad manager, an avoidant manager, or simply a manager responding reasonably to poor conditions? What evidence from the case supports your interpretation?
Sam's partner Nadia identified two problems Sam hadn't seen himself: the lack of setup and the absence of a specific ask. Why might it be easier for an outside observer to see these problems than for the person inside the situation?
Sam's third attempt used an email as a request-to-meet. Evaluate this choice. What made his email effective? What might have made it more effective still?
The chapter argues that contextual conditions are "active participants in the outcome." Which conditions in this case study had the greatest effect on outcome, in your assessment? Rank the factors (territory, medium, timing, emotional state, specific ask) in terms of their impact on Attempts One and Two.
What does this case suggest about the relationship between emotional preparation (working through private feelings) and conversational quality? Can you identify an analogous situation from your own experience?