Case Study 1: The Avoiding Boss and the Avoiding Employee

Overview

This case study follows Sam Nguyen, an operations manager, and his boss Marcus Webb, as they fail — month after month — to address the deteriorating performance of Tyler, a direct report whose work has been consistently incomplete and late for seven months. Both Sam and Webb default to the avoiding conflict mode. This case examines what happens when two avoiders share a management relationship, why the system becomes self-reinforcing, and what it would take — practically and psychologically — for Sam to break the pattern.

Background: The Players

Sam Nguyen, 35, Operations Manager

Sam is competent, well-liked, and genuinely good at the technical dimensions of his job. He has a quiet, even manner that his team generally finds reassuring. He was promoted into a management role two years ago and handles most of his responsibilities effectively. His conflict style is predominantly avoiding — he doesn't like friction, he doesn't trust that difficult conversations will go well, and he has a particular discomfort with situations where he might have to deliver news that hurts someone. These tendencies aren't dramatic; Sam doesn't panic or shut down. He simply finds elaborate, entirely reasonable-sounding reasons why now is not the right time to address a problem.

His partner Nadia has pointed out, with some affection and some exasperation, that Sam's most reliable superpower is making problems feel less urgent than they are.

Marcus Webb, Operations Director

Marcus Webb is Sam's boss, ten years his senior, and by every observable measure a very pleasant person to work for. He sends encouraging emails. He brings donuts on Fridays. He has never, in Sam's two years reporting to him, delivered a piece of feedback that made Sam uncomfortable. He has also never resolved a personnel problem that required sustained pressure. His management style can be described as cheerful delegation combined with benign neglect. When something goes wrong, Marcus's instinct is to express concern and then wait for it to resolve.

He does not like conflict. He does not pursue it. And having never been held accountable for not pursuing it — because his own boss is four levels above him and largely satisfied with departmental metrics — he has had no particular reason to change.

Tyler, Logistics Analyst

Tyler joined the team fourteen months ago, performed adequately for the first six months, and has been declining since. His deliverables arrive late. When they arrive, they contain errors that Sam corrects silently. Tyler is not hostile or difficult when approached; he tends to offer explanations that sound plausible in the moment (he's been sick, the data was inconsistent, he had competing deadlines) and then repeat the same pattern in the following cycle. He has received no formal performance feedback. He has not been put on a performance improvement plan. He has been managed, functionally, by being quietly compensated for.

Tyler may or may not be aware of exactly how much Sam covers for him. He has certainly noticed that there are no consequences.

The System: How Avoidance Becomes Self-Perpetuating

The avoiding mode, used once, is a choice. Used repeatedly by the same person in the same situation, it becomes a groove. Used simultaneously by two people who are both responsible for addressing the same problem, it becomes a system — and systems are significantly harder to break than individual habits.

Here is how the Sam-Webb-Tyler system functions month by month:

Month 1: Tyler's deliverable arrives three days late. Sam fixes the errors, mentions it to no one, tells himself Tyler is probably adjusting to a new process. This is technically possible. Sam's "benefit of the doubt" is genuinely reasonable at this stage.

Month 2: Late again. Sam fixes the errors again. He thinks about mentioning it to Tyler but decides he needs more data. One month is not a pattern. He is not wrong about this, exactly.

Month 3: Late again, more errors this time. Sam sends Tyler an email that says, in effect, "Just a heads up — we need to watch our turnaround time on this." Tyler replies: "Absolutely, thanks for flagging." Nothing changes. Sam has done something — sent the email — which temporarily relieves the pressure inside him. But the email has done nothing to address the problem, and Sam, who did not follow up on the email with any consequence or direct conversation, has also communicated something to Tyler: that there are no consequences.

Month 4: Webb mentions, during a check-in, that he's heard some feedback about timeliness across the team. He does not name Tyler. He does not ask Sam directly. He offers a floating observation and then moves on. Sam says, "Yeah, we're keeping an eye on it." Webb nods. Both men feel they have done something. Neither has.

Month 5: Sam covers Tyler's errors again. He has now spent, by his own rough count, approximately three hours of cumulative time correcting Tyler's work across five months. He is beginning to feel a quiet, persistent resentment that he doesn't fully name. He also begins, more frequently, to think about what a conversation with Tyler would look like — and to feel exhausted by the imagined version before it starts.

Month 6: Tyler's deliverable arrives four days late, with significant errors that affect downstream reporting. Sam spends two hours correcting it. His partner Nadia notices that Sam seems irritable at dinner. He says it's just work. He is not wrong, but he is not fully right either: it is work that he is choosing, again, not to address.

Month 7: Webb's email — "Heard there might be some performance issues with the team? Let me know if you need anything" — arrives on a Tuesday. Sam reads it. Considers it. Types: "I think we're okay for now. Will keep an eye on it." Sends it. Opens Tyler's file and starts correcting the errors.

Analysis: What Is Actually Happening

What Avoidance Is Doing to the Problem

The conflict itself — Tyler's underperformance — is not resolving itself. Conflict that is avoided does not disappear; it transforms. In this case, it has transformed in several ways:

The problem is growing. Tyler's errors are more numerous in Month 7 than they were in Month 1. Absence of feedback is feedback — specifically, it communicates that the current level of performance is acceptable. Tyler has no reason, from the signals he's received, to believe anything is wrong.

Sam's resentment is accumulating. This is one of the least-discussed costs of chronic avoidance: the avoided conflict doesn't leave the avoider's internal emotional landscape. It collects there, often transforming from a specific grievance (Tyler is late again) into a more diffuse and harder-to-address feeling (I'm exhausted, I can't depend on anyone, my team is a burden). Sam has not yet reached the point where this resentment breaks through — but the trajectory is clear.

Sam's coverage has become enablement. By correcting Tyler's errors silently, Sam has removed the natural feedback mechanism that would otherwise signal to Tyler that his work is inadequate. The errors that would cause downstream problems — and would therefore draw attention — never surface, because Sam absorbs them. Sam is, in effect, protecting Tyler from the consequences of his own performance, which removes Tyler's most powerful incentive to change.

Webb's non-engagement is a structural permission. A manager who expresses concern and then does nothing teaches his direct reports that expressing concern and then doing nothing is the appropriate response to personnel problems. Sam has been trained — by Webb's model and by the absence of any accountability for non-management — to manage the way Webb manages. This is not a conscious lesson; it is absorbed through observation.

The system has achieved a terrible stability. Nothing is in crisis (Sam's corrections prevent that). Nothing is improving. Nothing is being addressed. The three people in this system have found a pattern that prevents acute pain at the cost of chronic drift — and each of them has a stake, however unwitting, in maintaining that pattern.

What Is Preventing Sam from Acting

Sam's avoidance is not random. It has a logic, and understanding that logic is essential to changing it. Several specific fears and beliefs are operating:

The fear that direct feedback will damage the relationship. Sam generally likes Tyler. He believes, without evidence to support it, that raising the performance issue directly will make Tyler defensive or upset — and that Sam will then be responsible for managing Tyler's defensive reaction, which sounds worse than the current situation.

The belief that things will eventually improve on their own. This is the avoider's most reliable false comfort: the assumption that problems, left alone, self-correct. The evidence against this — seven months of it — has not yet fully overridden the belief.

A distorted accounting of the costs. Sam is very clear on the costs of acting (short-term discomfort, possible Tyler upset, possible awkward dynamic with Webb). He is much less clear on the accumulating costs of not acting (three hours of corrective work, growing resentment, Tyler's continued decline, his own professional responsibility as a manager going unmet). Avoiders characteristically overweight the costs of engaging and underweight the costs of continuing to avoid.

Webb's model. Webb's behavior has implicitly ratified Sam's. If the director doesn't pursue this, why should the manager?

What Would It Take to Break the Pattern?

Breaking a two-person avoidance system requires at least one person to operate differently. Let's examine what that would look like if Sam chose to shift — first to competing, then to collaborating — and what the realistic constraints and opportunities of each shift involve.

Option A: Sam Shifts to Competing

Competing in this context would mean Sam moving forward with a direct, unilateral intervention with Tyler regardless of Webb's engagement or support.

What this looks like:

Sam sends Tyler a calendar invite for a one-on-one: "Tyler — I want to meet Thursday at 10:00 to talk through your work on the logistics summary. Please block an hour." No hedging. No "whenever you have a moment."

In the meeting, Sam names the problem directly: "Tyler, I've been tracking your deliverables for several months, and there's a consistent pattern: late submissions, recurring formula errors. I've been correcting these on the back end, which isn't sustainable. I need you to understand this is a performance concern, and I need it to change."

Sam does not soften the message with apologies. He states what he has observed, what the impact is, and what he needs. He may or may not ask Tyler for an explanation at this stage — competing doesn't foreclose the possibility of hearing Tyler's side, but it leads with Sam's position rather than with collaborative inquiry.

What this accomplishes: - Tyler now knows there is a problem. This alone is significant. - Sam has discharged his managerial responsibility. - The pattern of silent correction is broken, which removes the enablement dynamic.

The risks: - Tyler may become defensive and difficult. - Webb may not support Sam's approach if Tyler escalates to him — and Webb, as an avoider, may respond to that pressure by backing away from Sam rather than backing Sam up. - Sam may feel uncomfortable in the meeting and want to back off mid-conversation. His tendency to clear his throat and defer when he senses the other person's displeasure is a real risk in a competing mode.

Is competing the right call here? It is likely the right first move — Sam needs to break the pattern of silence, and competing accomplishes that with clarity. It is probably not the right ultimate approach, because Tyler's performance issues may have explanations that matter, and because Sam's goal is not just to name the problem but to resolve it.

Option B: Sam Shifts to Collaborating

Collaborating would mean Sam approaching Tyler with the explicit goal of understanding what is getting in the way and working toward a solution together.

What this looks like:

Sam's opening in the one-on-one meeting is different: "Tyler, I want to talk about the logistics summaries. I've been noticing a pattern — late submissions, some errors that have needed correction — and rather than just flagging the problem, I want to understand what's going on from your side. Because I'm aware I've been pretty quiet about this, and I should have raised it sooner. So: what's your experience been? What's getting in the way?"

This is still assertive — Sam is naming the pattern, naming his own role in allowing it to continue, and inviting real dialogue. But he is genuinely opening space for Tyler's perspective rather than simply delivering a verdict.

What this accomplishes: - Sam may learn something important. Tyler might reveal that he's been waiting on data from another team, or that the formula structure is unclear, or that his workload in other areas has become unmanageable. - Or Tyler may reveal nothing useful — in which case Sam has the information he needs to escalate. - The conversation itself is relational in a way that competing is not — it signals to Tyler that Sam is treating him as a person, not just a performance problem, which may matter for the team's long-term dynamic.

The risks: - Sam's collaborative approach requires Tyler's genuine participation. If Tyler is simply not trying, collaborative inquiry may feel manipulative after the fact — like Sam gave Tyler a chance to explain, Tyler couldn't, and now Sam is still stuck. - Sam's natural tendency toward accommodating means the collaborating conversation could drift into something softer than intended — where Tyler offers an explanation, Sam accepts it graciously, and the accountability part of the conversation never fully lands.

Managing the drift risk: Sam should prepare, before the meeting, a clear articulation of what outcome he needs — not just what he wants to explore. "I want to understand your experience. And I also need to be clear that X needs to happen by Y date, or I'll need to escalate this formally." The collaborating intention doesn't preclude a clear consequence structure; it simply approaches the relationship with more curiosity before delivering it.

What About Webb?

Sam cannot manage Webb's avoiding style, but he can manage how he relates to it. Several options exist:

Option 1: Inform Webb directly before acting. "Marcus, I want to give you a heads up — I'm planning to have a direct performance conversation with Tyler this week. I've been tracking some ongoing issues and I think it's time to address them formally. I'll keep you posted." This gives Webb the information he needs to support Sam if Tyler escalates, and puts Webb in a position where he can no longer claim he didn't know.

Option 2: Document and create a paper trail. Sam should document his conversations with Tyler and communicate them to Webb in writing. This creates accountability in the system even if Webb's verbal engagement is minimal.

Option 3: Name the pattern with Webb directly. This is the hardest option and the one Sam is least likely to choose, given the power differential. But if Sam were operating from the most situationally flexible version of himself, he might recognize that Webb's non-management is also a problem that deserves a direct conversation: "Marcus, I want to check in about Tyler. I've been handling things pretty quietly on my end, and I'm realizing I've been doing that partly because it hasn't felt like there was much organizational support for addressing it directly. Can we talk about how you want me to manage performance issues going forward?"

This is collaborating directed upward — assertive enough to name the pattern, cooperative enough to genuinely invite Webb's input.

Key Takeaways from This Case

Two avoidance styles in the same management chain create a system that perpetuates problems rather than resolving them. The problem doesn't disappear; it accumulates, transforms, and eventually becomes larger or more expensive than the conversation that was avoided.
Avoidance that functions as coverage removes the natural consequences that drive change. Sam's silent corrections are not just a workload issue; they are an active mechanism that prevents Tyler from experiencing the feedback he needs.
The costs of avoidance are real but diffuse. They accumulate slowly (resentment, worsening performance, missed development) rather than producing a single painful moment — which is why avoiders consistently underestimate them.
Breaking a two-person avoidance system requires at least one party to shift mode. Sam cannot control Webb; he can only change his own behavior. That change — even unilaterally — can alter the system's dynamic.
Competing and collaborating are both more appropriate than continued avoidance here. Competing breaks the silence cleanly and clearly; collaborating may produce deeper understanding and better long-term outcomes. The ideal sequence may be: use competing to break the pattern (name the problem unambiguously), then shift to collaborating to understand what's driving it and build a real solution.
Managing up is part of managing down. Sam's ability to address Tyler is partly constrained by Webb's avoidant style. Choosing to inform and document — even if Webb doesn't fully engage — changes Sam's situation and his professional responsibility.

Discussion Questions

At what month, if any, do you think Sam's avoidance stopped being reasonable and became problematic? What changed at that point?
Webb's avoidance is arguably more damaging than Sam's because of his positional authority. Do you agree? What special responsibilities does positional power create around conflict engagement?
If you were Sam, which shift would feel harder: initiating a direct conversation with Tyler, or initiating a direct conversation with Webb? Why?
The case suggests that Sam's corrections have "enabled" Tyler. Is this framing fair? Is it possible to help someone in a way that harms them?
What organizational conditions — culture, HR processes, management training — would make it harder or easier for a system like the Sam-Webb-Tyler triangle to persist?