Give Managers Language for a Difficult Coaching Conversation

Managers often postpone feedback when their first thought sounds like a judgment. "You need more executive presence" leaves a seller facing a verdict with no clear next move. The manager might have noticed a real pattern, yet the wording turns observed work into a claim about personality. An enablement consultant helps managers use language tied to one moment, one question, and one future attempt.

Begin with a source both people inspect. A manager might listen to a recorded customer conversation, observe a meeting, read a follow up email, or join preparation for a customer discussion. Before speaking with the seller, write notes covering the point in the interaction, the customer's question or action, the seller's response, and the reason this moment matters. "The call felt unfocused" gives little help. "After the buyer asked about timing, you described reporting options before asking about their deadline" gives both people a shared starting point.

Ask about intent before offering an interpretation. Sellers often hold context outside the source. Perhaps a buyer raised timing during a prior conversation. Perhaps the seller tried to answer an issue from an earlier email. A manager might say, "When the buyer asked about timing, I heard reporting details before a question about their deadline. What were you trying to learn there?" This opening leaves room for explanation, which helps the manager choose a relevant request rather than assume a motive.

Use a fictional practice situation during manager training. Dev supports Rosa, a frontline manager. Rosa says, "Asha needs more executive presence." Dev asks Rosa what Asha did. Rosa replies, "She answered every question with a feature." They listen to a recorded call. At minute twelve, a buyer asks whether the group will need approval before a summer launch. Asha lists reporting options, then offers a product demonstration. Dev asks Rosa to describe only what she heard.

Rosa begins with, "Asha missed the strategic question." Dev asks for another version without a label. Rosa says, "The buyer asked about approval before a summer launch. Asha described reporting options, then offered a demonstration. I did not hear a question about who approves the launch or what date matters." Dev asks what Rosa wants to ask Asha. Rosa answers, "What were you trying to learn when you offered a demonstration?" Her revised language starts a discussion about a decision in the conversation, rather than an argument about talent.

After listening, explain the effect using only the available interaction. An effect need not predict revenue or claim knowledge of a buyer's private view. Rosa might say, "We left approval and timing unclear, so our notes do not show who should join a next meeting." This sentence stays close to work the manager heard. Avoid phrases such as "You always rush" or "You lack confidence." One conversation rarely supports a permanent trait, and such statements offer no precise behavior for a later attempt.

Make one request for practice. A long list of corrections turns feedback into vague homework. Rosa chooses the next customer discovery call scheduled for Thursday morning. She asks Asha to pause after a timing question and ask, "Who needs to approve the launch, and when do they need a decision?" Asha writes those questions in preparation notes. Rosa joins the first ten minutes and listens for a pause before Asha responds. The request names an action, a setting, and an observer.

A seller might offer a reasonable challenge. In the fictional situation, Asha says, "The buyer had already said their procurement group was involved." Rosa acknowledges the point. "You are right. I heard procurement earlier. I still want a question about the person who approves timing for this launch. Would you try one question which separates procurement from launch approval?" Rosa does not need to win an argument. She needs an accurate shared attempt. Recognition of relevant context lets the request stay specific.

Prepare managers for emotion without turning a difficult conversation into therapy. A seller might become quiet, frustrated, or embarrassed. Do not fill silence with additional analysis. Rosa might say, "Take a moment. I want your view before we settle on a next try." When Asha says feedback feels unfair, Rosa returns to the source. "Let us listen to the ninety seconds around the buyer's question. Tell me what you hear first." If Rosa notices irritation in her own response, she pauses and schedules another discussion instead of forcing agreement during a rushed exchange.

Practice language in short sessions. Ask every manager to bring one sentence planned for an upcoming conversation. A partner plays a fictional seller and asks, "What did I do?" The manager replaces labels with one moment from work. The partner then asks, "What do you want me to try next?" The manager states one behavior and one upcoming opportunity. An observer listens for unsupported claims, more than one request, or an absent follow up date. Rotate roles after each round so managers experience both sides of the discussion.

Give the observer a narrow job. During Rosa's first practice, Dev listens only for source based language. During a second round, he listens only for a request with a place and date. Narrow observation prevents everyone from commenting on every sentence. After each round, the manager rewrites one sentence in a notebook. For example, "Lead the meeting better" becomes, "When the buyer changes topics, ask which issue matters most before offering a demonstration." The revision supplies a specific action for the seller's next attempt.

Keep a short record after the coaching conversation. Write the observed moment in one sentence. Write the seller's stated intent in one sentence. Write the agreed retry and next observation date in one sentence. This record limits memory drift. At the next review, Rosa asks Asha what happened when she used the approval question, then compares Asha's account with the new conversation. The record does not settle every disagreement, though both people have a shared reference.

Consultants should notice language which turns behavior into identity. "You are not consultative," "You are too junior," and "You do not know how to lead a meeting" provide no useful path. Translate each label into an observation and request. "You did not lead the meeting" might become, "After the buyer changed topics, you moved to a demonstration without checking which issue mattered most." The manager then asks for a single question during the next similar moment. This approach respects the seller while keeping attention on the work.

End the fictional practice inside a scheduled action. Rosa and Asha meet at 8:45 on Thursday before the customer call. Rosa writes one prompt on her note page: "What did you seek to learn before answering timing?" After the call, Asha opens her preparation notes and circles the approval question she used. Rosa records the minute from the call and places a ten minute review on Friday's calendar, where Asha will listen to the response before choosing her next question.