How to Coach Technical Reps Who Are Weak Communicators

Every enablement leader has this rep. They know the product deeper than anyone on the team, they are the person the rest of the floor pings when a prospect asks something hard, and their win rate is mediocre. Coaching technical reps on communication is a specific job, and the usual playbook of more product training makes it worse, because product knowledge is the thing they already have.

Where Technically Strong Reps Lose the Room

The gap is rarely one big flaw. It is a set of recognizable behaviors that compound over a call.

• Over-explaining. Asked whether the platform supports SSO, the rep answers yes and then keeps going for ninety seconds about the identity provider architecture. The buyer got their answer in the first word and spent the rest of the time waiting. Repeat that pattern across a call and the rep has used most of the airtime without learning anything.
• Jargon density. One unfamiliar term is fine; any buyer tolerates it. Three in a single sentence forces the listener to either interrupt or quietly stop tracking. Most stop tracking, and nobody in a first meeting admits it.
• Answering a question nobody asked. The buyer asks how long implementation takes. The rep hears an implicit doubt about technical depth and answers that instead. The buyer now has to ask the original question again, or drop it.
• Missing the non-technical stakeholder. There are usually two or three people on the call. The rep locks onto the one who speaks their language, typically the engineer or the technical evaluator, and stops addressing the economic buyer entirely. That buyer leaves the call without a single sentence they could repeat to their own leadership.
• Flat delivery. A monotone voice reads as low conviction even when the content is strong, and technical reps are disproportionately affected because they are concentrating hard on precision. Precision and energy compete for the same attention.
• Filler under pressure. The stumble usually arrives right after a question the rep cannot answer cleanly, which is exactly the moment the buyer is judging confidence.

Why This Never Surfaces in a Deal Review

Deal reviews are run on content. Did we identify the champion, did we get to the economic buyer, what is the compelling event. A technically strong rep passes those questions easily, because they can describe the deal accurately. The call itself is what went wrong, and the call is not in the room.

The second reason is that this rep is valuable. They answer the hard questions other reps cannot, so managers protect them and route escalations to them. Nobody wants to tell the smartest person on the team that they are hard to follow, so the feedback gets softened into “work on your executive presence.” That phrase gives the rep nothing to do on the next call, and it lands as an insult about personality rather than a description of behavior.

Diagnose Before You Coach

Pull three recent recorded calls from this rep and score them for specific, countable things rather than an overall impression.

Start with talk time. Talk time ratio is a blunt instrument, and for this profile it is the fastest signal you have, because over-explaining shows up as a rep who dominates the first half of a discovery call. Then count how many questions the rep asked after minute ten, when the technical discussion usually takes over. Then mark the first moment in each call where the non-technical stakeholder stopped speaking, and look at what the rep said in the minute before it.

Write down actual quotes. A coaching conversation built on the sentence the rep said lands completely differently from one built on your characterization of how they came across. You are naming a behavior in a moment.

Coach One Behavior at a Time

Open with the thing they are good at, honestly and specifically, because they know they are the technical authority and any feedback that ignores it will be discounted. Then take exactly one behavior into the session. The instinct is to hand over the full list. The full list is overwhelming and produces a rep who becomes self conscious mid call, which makes delivery worse for a month.

Pick the behavior with the highest leverage for that rep. For most technical sellers it is answer length. Give them a rule they can execute under pressure: answer the question in one or two sentences, then stop and ask whether they want the detail. That rule works in real time in a way that “be more concise” never will. The habit of saying more with less is built from a rule like that repeated until it stops requiring thought.

The Drills That Change It

Reading advice about concision does not change how anyone speaks on a live call. Ericsson’s model of deliberate practice, revisited by Macnamara and Maitra in Royal Society Open Science, describes the conditions that do: effortful repetition on one specific sub skill, with immediate feedback. That is the shape the drills need to take, and it is the reason AI roleplays fit this profile so well. In Yoodli, the rep gets the same buyer persona, the same hard question, and a scored playback, as many times as it takes.

The two sentence answer. Run an AI roleplay where a buyer persona fires rapid technical questions and the rep has to answer each in two sentences before offering more. Ten questions in a row. The constraint is the training.

The non-technical stakeholder in the room. Use a multi persona scenario with an engineer and a CFO. Score only one thing: did the rep translate at least one technical answer into business terms without being asked. This is the same skill a good technical briefing requires, and it transfers directly to the parts of the call the economic buyer remembers.

The jargon swap. Take the five terms this rep uses most and have them explain each to a buyer persona who has never heard them. No slides.

Delivery isolation. Filler words and flat pace respond to targeted repetition with immediate feedback more than to any amount of advice, which is why reducing filler words works best as its own drill rather than as one note inside a general call review. Yoodli scores filler rate and pacing on every roleplay automatically, so the rep sees the number move without a manager sitting in. This is standard practice in engineering organizations where solutions engineers and technical specialists present constantly, and it applies just as directly to sellers in tech and SaaS.

What to Measure

Measure the behavior first and the outcome second, because the outcome moves on a deal cycle and you need a signal sooner than that.

On behavior: talk time ratio, questions asked per call, average answer length on technical questions, filler rate. All of these are countable from recorded practice and from real calls, and all of them should move within a few weeks if the drills are running.

On outcome: multi threading rate, stage conversion from first meeting to technical evaluation, win rate on deals with a non-technical economic buyer, and certification pass rate if this profile is failing your pitch certification. Manager time matters too. Harness cut sales training review time by 75% with Yoodli, which is the difference between a manager who can run this kind of targeted drill with several reps and a manager who can only do it with the one rep whose deal is closing this quarter.

How Long Does Coaching Technical Reps on Communication Take?

Plan on three weeks for the first behavior, then decide whether to add a second. Here is what that looks like for a rep whose problem is answer length.

Week one is diagnosis. Score three recorded calls, pull the quotes, and hold one coaching conversation that ends with a single rule the rep agreed to. Do not assign drills yet. The rep needs to hear the rule in their own words before repetition does any good.

Week two is daily repetition. Ten two-sentence answers a day in an AI roleplay, five days, against the same buyer persona. Ask the rep to send you one scored session at the end of the week. The point is a habit forming under low stakes, and a manager reviewing every session turns low stakes back into high stakes.

Week three is transfer. The rep runs the rule on live calls and you re-score the next three recordings on the same metrics you used in week one. If average answer length dropped and questions asked went up, the behavior moved. If the numbers did not move, the rule was wrong for this rep. Pick a different rule before you add more repetition.

A few things break this timeline. Skipping the diagnosis and starting with drills is the common one, because the rep never sees their own quotes and treats the whole thing as a manager’s opinion. Stacking two behaviors in the same three weeks is the other. Answer length and stakeholder translation are separate skills, and a rep working on both at once usually improves neither.

The Objections You Will Hear

“This rep closes enough.” Sometimes true. Check whether their deals are concentrated with technical buyers and whether they stall at the point where a business case has to go up a level. That pattern is the tell.

“You will coach the expertise out of them.” The rule constrains answer length in a first meeting. The depth stays available and gets deployed when the buyer asks for it, which for a technical evaluator will be often.

“They will resist.” Some do, right up until they see a scored playback of their own call next to a quantified answer length. Data about their own behavior is an argument this profile respects.

Start with one rep, one behavior, and three weeks of drills before you build a program around it. If you want a place to run that kind of repetition, Yoodli’s AI roleplays let a rep rehearse the same technical moment against the same buyer persona until the delivery holds.