We Scored 40,000 Coaching Moments Against 54 Competencies. Managers Coach Five of Them and Ignore the Rest.

Pull the coaching logs from any six-month stretch at a mid-market B2B sales floor and count what actually gets said out loud. Objection handling comes up constantly — reps get drilled on it in one-to-ones, role-played in team meetings, dissected on call reviews. Discovery depth barely gets a mention. Negotiation, the competency that decides whether a deal closes at list price or gets discounted into a loss-making account for three years, shows up so rarely in manager feedback it might as well not be part of the job. This isn't a hunch about manager laziness. We scored it. Across 40,000 coaching moments captured against The Mastery Standard's 54-competency taxonomy — call reviews, one-to-ones, deal debriefs, spanning SaaS, financial services and industrial distribution teams — five competencies absorb the overwhelming majority of manager attention. The other 49 get scraps, and a handful get nothing at all.

This matters more than "managers have blind spots," which is the kind of line that gets a nod in a QBR and changes nothing. It matters because the five competencies managers gravitate toward are, almost without exception, the ones that are easiest to catch on a single listen-back and easiest to score without much expertise. The competencies they skip are the ones that actually separate a rep who survives year one from one who's still there, thriving, in year five.

Where manager attention actually goes

Here's the distribution, ranked by share of the 40,000 scored moments that touched each competency, with the top five accounting for nearly four in five coaching mentions.

And here's where the same 40,000 moments leave five foundational competencies, each one load-bearing for anything past a rep's first six months on the job.

Why the gap exists, and why it isn't a people problem

None of this is about lazy managers. It's structural. Objection handling happens inside a single utterance you can quote back verbatim. Multi-threading happens across six weeks and four stakeholders, and unless a manager is tracking the account the way the rep is, there's no single moment to point at. Negotiation mostly happens in the final stretch of a deal cycle, often over email or in a room the manager isn't in, and by the time it's visible the outcome is already locked in — coaching it after the fact is autopsy, not development.

There's a second, less comfortable reason. Coaching negotiation, business case construction, or multi-thread mapping requires the manager to actually be good at those competencies themselves, and to be able to name the technique rather than just the vibe. "Good energy on that call" is a sentence anyone can say. "You anchored on their stated budget instead of your own list price, which cost you eleven points of margin before the conversation even started" requires a manager who understands negotiation as a taught skill rather than a personality trait some reps happen to have. Most managers were promoted for being excellent individual performers, not for being able to articulate why a technique works — a separate problem, and one for another post.

What this costs, concretely

A rep who gets coached on objection handling forty times in a year and never once on qualification rigor will get very good at surviving a call they shouldn't have taken in the first place. That's not a hypothetical — it shows up as pipeline that looks healthy at the top and evaporates at commit. Deals slip not because the rep couldn't handle "we need to think about it," but because nobody ever coached them on the four questions that would have surfaced the real objection eight weeks earlier, when there was still time to do something about it.

Enablement leaders who run a coaching programme without checking the distribution are, in effect, running a programme that reinforces whatever the manager already finds easy, and quietly starves the rest of the competency model of any development at all. If your rubric has 54 competencies on paper and five of them absorb 80% of actual coaching time, you don't have a coaching programme mapped to a framework. You have a habit with a framework taped to the front of it.

What to actually do about it

Three moves, in order of effort:

1. Audit the distribution before you fix anything. You cannot correct a skew you haven't measured. Pull three months of coaching notes and tag every mention against your competency list — most enablement teams have never done this once.
2. Set a coaching quota per competency cluster, not per rep. If discovery, qualification, negotiation and multi-threading combined get less than a fifth of coaching time in a given quarter, that's a target to fix, not a footnote.
3. Give managers something to point at for the invisible competencies. The reason objection handling gets coached to death is that it's easy to catch. Make the hard-to-catch competencies just as catchable — a structured Discovery Call Scorecard turns "did they go deep enough" from a vibe into a checklist, and a Team Skill-Gap Heatmap Generator makes the gap visible at team level instead of living only in your gut.

If you run enablement and you've never audited what your managers actually coach against what your framework says they should, run the Coaching Effectiveness Scorecard for Managers over a month of notes before you build anything else. You will not like the distribution. That's the point of measuring it.

The uncomfortable ranking

Objection handling isn't overcoached because it's the most important competency in the model. It's overcoached because it's the cheapest to coach. Discovery, negotiation, and multi-threading aren't undercoached because they don't matter — they're undercoached because they're expensive to catch and expensive to judge. A competency model is only doing its job if it's changing what gets said in the room. Otherwise it's decoration, and decoration doesn't close the deals your team is currently losing at the qualification stage, three months before anyone notices.