The Awkwardness Before the Awkward Conversation: How to Start

The cursor blinks. On one half of your screen is the draft your team member, Alex, just submitted. On the other half is a blank message to him. You can feel the familiar tightness in your chest. This is the third time you’ve had to address the same issue with his work. It’s not about typos; it’s about a fundamental lack of… something. Depth? Strategic insight? You type, “Hey Alex, do you have a minute to connect about the draft?” and delete it. Too ominous. You try again. “Hey, some quick thoughts on this.” Too dismissive. You find yourself searching for phrases like “my employee gets defensive when I give feedback” because you know exactly how this conversation will go: you’ll try to explain the problem, Alex will get quiet and tight-lipped, and you’ll walk away feeling like a micromanager who just demoralised a good employee.

The problem isn’t the conversation itself. It’s the thirty seconds before you even begin. The real issue is a communication pattern that has already failed twice and is about to fail a third time. You’re both stuck in a loop where your attempts to clarify the standard are heard as a judgment of the person. You’re trying to point to a target he can’t see, and he thinks you’re just telling him he’s a bad shot. This pattern is so powerful that the conversation is over before it starts.

What’s Actually Going On Here

This recurring sense of dread is often rooted in what could be called an “abstraction trap.” As the manager or senior professional, you hold a picture in your head of what “good” looks like. This picture is detailed and specific. It includes the audience’s likely reaction, the political context of the project, and the unwritten rules of the organisation. When you look at the work, you see the gap between the reality and your mental picture.

The trap is sprung when you try to describe that gap using abstract labels. You say, “This needs to be more strategic,” or “It lacks polish,” or “I need you to show more ownership.” To you, these words are shorthand for a dozen concrete details. To your colleague, they are vague, un-actionable judgments. They can’t see the picture in your head, so they can’t see the gap. All they hear is, “What you did is not good enough.” They then make a guess at what “more strategic” means, work hard on the guess, and a week later, you’re both back in the exact same room, even more frustrated.

The system you work in makes this worse. Tight deadlines don’t allow for long conversations to unpack what “strategic” means in the context of a single two-page document. Performance reviews reward abstract qualities like “leadership” and “initiative,” reinforcing the idea that these are things people should just know. The entire structure conspires to keep the target blurry, forcing you into the role of the sole arbiter of an invisible standard.

What People Usually Try (and Why It Backfires)

When faced with this recurring conversation, most competent professionals make a few logical moves to try to soften the blow or fix the problem. They almost always make the pattern stronger.

• The Compliment Sandwich. You try to cushion the criticism with praise. It sounds like: “You did a great job on the research here, and the core idea is solid. I just think the final section needs to be a bit more client-focused. But overall, great work.” This doesn’t make the feedback clearer; it makes it confusing. The other person latches onto the praise (“I thought you said it was great work?”) or dismisses it as a disingenuous formality.

• Escalating Precision. After the first failed attempt, you get more prescriptive. It sounds like: “Okay, just do this. In paragraph one, change the heading. In paragraph two, add the statistic from the Q3 report. And send it back to me.” This gets the task done, but it bypasses the actual problem. You’ve replaced a conversation about strategic thinking with a to-do list. You become a micromanager, and your colleague feels like an order-taker with no agency.

• The Vague Pep Talk. You try to address their defensiveness by focusing on their potential, not their work. It sounds like: “I know you can do this. I have total faith in you.” This feels supportive, but it’s a form of dismissal. It completely ignores the fact that there is a real, tangible gap in understanding. They don’t need a cheerleader; they need a map.

A Different Position to Take

The way out is not to find a better technique for delivering feedback. It is to take a completely different position in the conversation. Stop being the Judge with the verdict. Stop being the Instructor with the secret answer key.

Your new position is that of a Collaborator in Diagnosis.

You are not there to tell them what’s wrong. You are both sitting on the same side of the table, looking at the same problem. The problem isn’t the person; the problem is the gap between the current draft and the finished product. Your job is to make the invisible standard visible, to clarify the target so you can both see it with the same level of detail.

This means letting go of the need to be right. It means letting go of efficiency in the short term. You are trading five minutes of quick, prescriptive feedback for a twenty-minute conversation that might actually solve the problem for good. Your goal is not to fix this one document. It’s to fix the process by which you both talk about the work. You are shifting from “Here is what you did wrong” to “Let’s figure out why we’re not aligned on the target.”

Moves That Fit This Position

This isn’t a script, but a set of moves that flow from the position of a co-diagnostician. They are designed to stop the old pattern in its tracks and start a new one.

• Name the pattern and share responsibility. Start the conversation by starting the real conversation. It sounds like: “We need to talk about this draft, but I want to start somewhere else. This is the third time we’ve been in this loop, and I’m guessing it’s as frustrating for you as it is for me. I think the problem is with my feedback, not your effort. It’s clearly not been specific enough.” This immediately lowers defensiveness and frames the issue as a shared process problem.

• Replace abstract labels with observable differences. Don’t use the word “strategic.” Instead, put the current draft next to a document that is strategic. It sounds like: “Let’s look at the report from the ABC project that we all agreed was a success. Put it side-by-side with this one. What differences do you notice in the opening paragraph?” You are making the abstract tangible.

• Check for understanding of the goal, not the task. Before diving into edits, make sure you’re aligned on the purpose. It sounds like: “Before we get into line edits, can you tell me in your own words: what do we need the client to think or do after they read this document?” If your answers are different, you’ve found the root of the problem. It has nothing to do with writing; it has to do with a fundamental misalignment on the objective.

• Give information, not evaluation. Instead of saying “This opening is weak,” provide the missing context. It sounds like: “I just came from a meeting with the client, and they mentioned twice that they’re worried about the project timeline. Our opening paragraph needs to address that concern directly in the first two sentences.” This transforms a judgment (“weak”) into actionable, strategic information.