Selling@Zero Distance

The Gap Isn’t in Your Rep

When revenue slips, there’s a reflex almost every leader reaches for. Assess the team. Score the skills. Find the gaps. Build a plan to close them.

It’s tidy. It’s defensible. It feels like rigor.

And it quietly measures the wrong thing.

The hidden assumption

Every skills assessment carries a buried premise: that a salesperson is a closed system. A bundle of competencies (questioning, listening, objection handling, cadence) that can be inventoried, scored one to five, and topped up wherever the number runs low. Get every competency to mastery and performance follows.

But a sale doesn’t happen inside the seller. It happens in the space between two people. The most fluent rep in the building will stall against a buyer they can’t get close to, and a “low-scoring” rep will close because, in that room, the distance was small.

Performance lives in the relationship, not in the résumé of skills the seller carries into it.

Score the seller in isolation and you’ve measured one side of a two-way event. Then treated the number as if it explained the whole.

More technique is not the answer

There’s a second assumption hiding underneath the first: that the path to better selling is more. More skills, more frameworks, more things the rep should consciously be doing right.

Anyone who has studied performance in any field knows it rarely works that way. Tim Gallwey put it cleanly decades ago: performance equals potential minus interference. The bottleneck is seldom a missing technique. It’s the interference sitting on top of capability the person already has: self-consciousness, pressure, the noise of trying too hard.

Here’s the uncomfortable part. A detailed scorecard, handed to a rep across thirty competencies, is itself a source of interference. You cannot make someone more present in a buyer conversation by making them more self-conscious about everything they might be doing wrong. Judgment doesn’t sharpen performance. Awareness does, and the two are not the same thing.

Symptoms are not causes

Look at the items that show up on nearly every assessment as gaps to fix: active listening, better questions, objection handling, follow-up. These aren’t causes. They’re symptoms.

A rep who can’t listen well, who pitches before they understand, who meets every objection with a discount: that rep isn’t failing a technique module. They’re operating at distance. Drill the objection script all you like; if the relational distance is high, the objections keep coming back in new clothing. You’re treating leaves and ignoring the root.

A better diagnostic question

The question worth asking isn’t what skill is this person missing. It’s where is the distance.

I find it in three places.

Name the distance and the fix usually becomes obvious, and it usually isn’t a training module. It’s the removal of friction, not the addition of skill.

Measure velocity, not snapshots

None of this means stop measuring. It means measure the right thing at the right level.

A skills snapshot tells you what a rep looked like on the day they were scored. It says little about the system that actually produces revenue. And that system has a shape:

Every lever in that equation sits downstream of distance. Win rate climbs as relational and structural distance fall. Cycles shorten as friction leaves the process. This is measurement you can actually move, and it points at the relationship, not at an individual’s deficiency report.

Better still, it’s measurement in service of motion. The job isn’t to see a gap and score it. It’s to see, to measure, and then to animate: to keep working the live system rather than filing a static verdict on a person.

The reframe

The instinct to assess the rep comes from a good place. Leaders want visibility before the quarter ends, not after. That instinct is right.

But the gap is rarely in your rep. It lives in the distance between your seller and the buyer’s world, and you will not find that on a scorecard built to grade individuals one to five.

If the gap isn’t in your rep,
where is it?