The Error of Using a Hypothetical Example That's Obviously About Them

You’re staring at the calendar invite for your one-on-one with Mark. It’s in ten minutes. For the last three weeks, you’ve been trying to figure out how to tell him that his part of the project is consistently late, and the excuses are wearing thin. The whole team feels it. You feel it. You’ve rehearsed an opening line in your head, a gentler way in: “So, let’s imagine a hypothetical situation. Say there’s a team member, let’s call him ‘Steve,’ who is having trouble hitting his deadlines. What advice would you give ‘Steve’?” It feels clever. Diplomatic, even. It avoids direct accusation. But a knot in your stomach tells you it’s a bad idea. You’ve been on the receiving end of a “hypothetical” like that before, and you remember exactly how it felt: condescending, cowardly, and deeply irritating. You type into your search bar, “how to talk to a team member about missing deadlines without a huge fight.”

The move you’re about to make, the thinly veiled hypothetical, is seductive because it promises a shortcut past the discomfort of confrontation. It feels like a way to deliver a difficult message while giving both of you plausible deniability. But it’s a trap. The mechanism at play isn’t diplomacy; it’s a communication double bind. You are forcing the other person to participate in a charade. They must pretend they don’t know you’re talking about them, while simultaneously understanding the message and changing their behaviour based on it. It’s a game where the only winning move is not to play, but you’ve just made them the main character. The result isn’t clarity; it’s a quiet, seething resentment that erodes the very trust you were trying to preserve.

What’s Actually Going On Here

When you present a hypothetical that is clearly about the person in front of you, you put them in an impossible position. They have three responses, and all of them are bad.

1. They can play along. They can engage with the story about “Steve,” offering thoughtful advice about time management or communication. In this case, you both collude in the fiction. But now they see you as someone who is not courageous enough to speak to them directly. You lose credibility. They leave the conversation feeling manipulated, not supported, and the original problem remains unaddressed because it was never actually named.

2. They can call it out. They can say, “Are you talking about me?” This forces the game into the open. Now you, the manager, are on the back foot. You either have to admit to the ruse, confirming you were being manipulative, or double down on the lie (“No, of course not, it’s just a general example!”), which insults their intelligence and makes you look foolish. This response escalates the conflict, which is the exact thing you were trying to avoid.

3. They can stonewall. They can give a minimal, non-committal answer like, “Hmm, I don’t know,” and refuse to engage with the hypothetical at all. This is a quiet refusal to play your game. The conversation grinds to a halt, the tension hangs in the air, and you’ve achieved nothing except making the relationship more awkward.

The system you work in often quietly encourages this kind of indirectness. When an organisation’s culture punishes failed confrontations more than it rewards resolved issues, people learn to avoid directness. Managers who “keep the peace” get promoted, even if their teams are simmering with unspoken resentments. So you learn to hedge, to soften, to talk about “Steve,” because you’ve seen what happens to people who are blunt and direct, they get labelled as “not a team player” or “difficult.” Your attempt to be diplomatic is a logical adaptation to a system that prefers silent dysfunction over noisy problem-solving.

What People Usually Try (and Why It Backfires)

When the hypothetical doesn’t land, we tend to double down on other indirect moves. You’ve likely tried these, because they feel like the right thing to do in the moment.

• The Vague Generalisation. After the “Steve” example falls flat, you abandon the specific point and switch to a broad statement.

  “I just want to make sure everyone on the team has the resources they need to succeed.” This backfires because it’s a statement about nothing. It’s a retreat from the specific problem, signaling that you are officially dropping the subject. Mark knows it, you know it, and the unaddressed issue now feels even bigger.

• The Second-Hand Concern. You attribute the concern to an anonymous “other.”

  “There’s been some chatter from the team about feeling the pressure of deadlines.” This makes you look like you’re hiding behind gossip. Instead of owning the feedback as your own observation, you’re triangulating. This invites Mark to get defensive about “the team” instead of engaging with you about his work.

• The Pre-emptive Solution. You jump straight to giving advice to the hypothetical person.

  “So, what ‘Steve’ probably needs is a better project management tool, or maybe to block out his calendar.” This is condescending. You’re not only talking about him in the third person, but you’re also prescribing a solution without ever having diagnosed the problem with him. You’ve made it clear this isn’t a conversation; it’s a lecture in disguise.

The Move That Actually Works

The way out is not to find a more clever or more gentle way to be indirect. The move that works is to be cleanly and respectfully direct. This requires separating your observation of the facts from your interpretation or judgment of those facts. It’s the interpretation (“you’re unreliable,” “you’re making excuses”) that triggers defensiveness. The facts themselves are much harder to argue with.

The goal is to present a clear, observable reality and then make a genuine inquiry about it. You are not presenting a case for the prosecution; you are laying out a shared problem that you need their help to understand and solve. This positions you as a collaborator, not an accuser. It says, “Here is what I am seeing. Here is its effect. I am missing your side of the story. Please fill me in.”

This approach works because it treats the other person as a competent adult. You are trusting them to handle a direct conversation. You are not trying to manage their feelings by wrapping the message in a confusing hypothetical. By being direct, you are showing respect for their ability to engage with reality. This builds the trust that the hypothetical move destroys. It’s more uncomfortable in the first thirty seconds, but it’s the only path to a productive conversation.

What This Sounds Like

These are not scripts to be memorised, but illustrations of how to structure a direct opening. The structure is always: Here is the specific, neutral observation. Here is the concrete impact. Now, help me understand.

• For the late project work:

  “Mark, I wanted to talk about the last two project milestones. They were both submitted a day after the deadline. The direct impact was that the QA team had to work over the weekend to stay on track. Can you walk me through your process and what’s been happening on your end?” Why it works: It’s just facts. The dates are undeniable, and the impact is specific and measurable. The question is open-ended and assumes he has a perspective worth hearing.

• For a client who isn’t doing the work:

  “When we spoke last Tuesday, we agreed you would draft the email to your supplier. I see it hasn’t been sent. My concern is that we’re losing momentum. What got in the way for you this week?” Why it works: It connects a past agreement to a present observation. It names your concern (“losing momentum”) without judgment, and asks a genuine question.

• For a colleague who interrupts in meetings:

  “In the team meeting this morning, when Sarah was explaining the Q3 data, you jumped in to correct her numbers three times. I noticed that after the third time, she stopped contributing. I need to understand what you were seeing in that moment.” Why it works: It’s a specific, recent behavioural observation. It links the action to an impact you witnessed. The question “I need to understand what you were seeing” is one of genuine curiosity, not accusation.