The Awkwardness Before the Awkward Conversation: How to Start

A client comes to session and says they have to give feedback to a direct report. They have been here before with the same person. The last two attempts produced more confusion than clarity, and the third attempt is scheduled for Friday. They are not asking how to give feedback in general. They are asking how to start a conversation they know will fail before it begins.

The thirty seconds before the conversation begins is the actual problem. By the time the client opens their mouth, both they and the report are already inside the same loop they have been running for two months.

What the abstraction trap looks like

The client holds a detailed picture in their head of what good looks like for this work. The picture is specific. It includes the audience’s likely reaction, the political context of the project, the unwritten rules of the organization. When they look at the draft, they see the gap between it and the picture.

The trap activates when they try to describe that gap with abstract labels. “More strategic.” “More polished.” “Show more ownership.” To the client, these are shorthand for a dozen concrete details. To the receiver, they are vague, un-actionable judgments. The receiver cannot see the picture and therefore cannot see the gap. What they hear is: “What you did is not good enough.”

The receiver then makes a guess at what “more strategic” means, works hard on the guess, and a week later the same conversation happens. The client is more frustrated. The receiver is more defensive. The relationship accumulates a slow load of resentment that has nothing to do with the actual work being done.

The system the client works in reinforces all of this. Tight deadlines do not allow long conversations about what “strategic” means in the context of a two-page document. Performance reviews reward abstract qualities like leadership and initiative, which signals that these are things people should already know. The whole structure conspires to keep the target blurry and the client positioned as the sole arbiter of an invisible standard.

The moves the client has been making

The Compliment Sandwich. “You did a great job on the research, the core idea is solid. I just think the final section needs to be a bit more client-focused. Overall, great work.” This makes the feedback confusing rather than clearer. The receiver either latches onto the praise (“I thought you said it was great work?”) or dismisses the whole thing as a formality.

Escalating Precision. After two failed conversations, the client gets prescriptive. “Change the heading in paragraph one. Add the Q3 statistic in paragraph two. Send it back.” This produces a completed task. It also bypasses the actual problem. The client has converted a strategic-thinking conversation into a to-do list, become a micromanager in the process, and reinforced the receiver’s experience of being someone whose job is to execute rather than think.

The Vague Pep Talk. “I know you can do this. I have total faith in you.” This feels supportive, and it is a form of dismissal. There is a real, tangible gap in understanding, and the client has just covered it with reassurance. The receiver does not need a cheerleader. They need a map.

The shift you are coaching them toward

Stop being the Judge with the verdict. Stop being the Instructor with the secret answer key. The client’s new position is Collaborator in Diagnosis.

The problem to solve is not the receiver’s effort. The problem is the gap between the current draft and the finished product, and the client’s job is to make the invisible standard visible enough that both parties can see it at the same level of detail.

This requires the client to give up two things. First, the certainty that they are right about what good looks like, even when they are. Second, the efficiency of prescriptive feedback. They are trading five minutes of “do this, do that” for a twenty-minute conversation that may actually solve the problem for good. The frame shifts from “here is what you did wrong” to “let’s figure out why we are not aligned on the target.”

The moves that fit the new position

Name the pattern and share responsibility. The opening line: “We need to talk about this draft, and I want to start somewhere else. This is the third time we have been in this loop, and I think the problem is with my feedback. It has not been specific enough.” This single move drops defensiveness and frames the issue as a shared process problem rather than a fresh referendum on the receiver.

Replace abstract labels with observable differences. Do not say “strategic.” Put the current draft next to a document that the client considers strategic. “Let’s look at the report from the ABC project. Put it side-by-side with this one. What differences do you notice in the opening paragraph?” This makes the abstract tangible. The receiver discovers the standard through their own observation rather than receiving it as a label they cannot decode.

Check for goal alignment before task alignment. Before any line edits, the client asks: “What do we need the client to think or do after they read this document?” If the answers diverge, the misalignment is upstream of the writing. The conversation is no longer about strategic phrasing. It is about what success would look like, and the writing improves automatically once that conversation is real.

Replace evaluation with information. Instead of “this opening is weak,” the client provides the missing context. “I just came from a meeting with the client. They mentioned twice that they are worried about the timeline. The opening paragraph needs to address that in the first two sentences.” This converts a judgment into an actionable strategic input. The receiver can act on the information. They could not act on the judgment.

What to listen for in the next session

Did the client name the pattern at the start? What did the receiver do when they did?

Most receivers visibly relax inside the first two minutes of a conversation that opens with shared responsibility. If the receiver did not relax, the question is whether the client delivered the line cleanly or whether their residual frustration leaked through. Most failures here are about tone.

If the client named the pattern and the receiver still defended themselves, the formulation expands. Either the receiver is responding to a longer history of feeling judged in this organization, or the receiver is testing whether the new framing is a trick before risking the actual work. Both resolve with a second well-delivered conversation in the same frame.

When the abstraction trap is not the right formulation

Sometimes the client cannot articulate what good looks like, even with coaching. The standard exists in their head as a feeling rather than a structure. In that situation, the work shifts. The first conversation is no longer with the receiver. It is with the client, working to externalize the standard into something concrete enough to share. Until that work is done, no feedback conversation will produce a different outcome.

Sometimes the receiver lacks the underlying skill the client is assuming they have, and clearer feedback will not close the gap. That is a different conversation altogether, and the client needs to know they are in it before they walk into another meeting expecting feedback to do the work that training or reassignment would.

Most of the time, the abstraction trap is the formulation, and naming it out loud with the receiver is what dissolves it. The client’s report will be a softer relationship and a better next draft. That is the win.