What 'Competency-Based Coaching' Actually Means, and Why Most Coaching Programs Never Get There
Not a values poster. Not a scorecard bolted onto a CRM. A working definition, and the three things that have to be true before you can claim it.
Every enablement deck I've reviewed in the past few years has a slide with the words "competency-based coaching" on it, usually next to a stock photo of a handshake. Fewer than one in five of those programmes survive me asking what specific competency was observed last week, at what level, tied to what practice. That's not a semantics complaint. If those three parts aren't in place, what's running is structured feedback, which is genuinely useful, just not the thing on the slide — and the gap between the two shows up directly in ramp time.
A working definition, not a poster
Competency-based coaching has exactly three parts, and all three have to be true at once:
- Observed behaviour mapped to a named competency. Not "handled the pushback well" — a specific competency with a name, like Objection Reframing, that exists on a list somewhere and means the same thing every time it's used.
- Graded against a defined level for that competency. Not a 1-to-5 gut-feel scale — an actual rubric where a 2 and a 4 are described in behavioural terms, so two different observers watching the same call would land on the same number.
- Tied to a specific practice path. Not "keep working on it" — a named next rep, drawn directly from the gap between the observed level and the level above it.
Miss any one of these and you don't have competency-based coaching. You have an opinion, a scorecard, or a nice conversation, depending on which part survived.
Where most programmes actually stop
Part 1 is the one nearly everyone gets, because it's the cheap part — you can buy or borrow a competency taxonomy in an afternoon, tag it into the CRM, and call the job done. It's also the part that feels most rigorous from the outside, because it comes with a list.
Parts 2 and 3 are where the wheels come off, and for a boring reason: they're expensive. Writing an actual level ladder for a competency — what a 2 looks like versus a 4, in language specific enough that two managers watching the same recording agree — takes real subject-matter labour from someone who's actually done the job at a senior level. Most orgs don't have that person free, so "graded against a level" quietly becomes "scored 1 to 5 based on how the observer felt," which isn't grading, it's a mood ring with numbers on it.
Part 3 fails for a different reason: it needs a cadence, not just a document. A practice path only works if someone checks whether the rep actually did the rep, and that requires manager time most enablement calendars never account for. So the loop closes at "logged in the CRM" instead of "changed on the next call," and the feedback — however accurately it was tagged in part 1 — dies in a field nobody reopens.
The cost of stopping at part 1 shows up as a ramp problem before it shows up anywhere else. A new hire told they're "developing" on Discovery has no way to know whether that means they're one behaviour away from Proficient or nowhere close, and neither does their manager three months later when the quarterly review rolls around and the same word is still sitting in the same field. A new hire told they're at level 2 on Discovery Questioning, with level 3 defined as "asks a follow-up question tied to the buyer's previous answer, not a scripted next line," knows exactly what changes between now and the next call. The taxonomy costs the same either way. The difference is entirely in whether anyone bothered to write the level ladder underneath it.
A worked example
Take Objection Reframing as the named competency.
| Level | Behaviour |
|---|---|
| 1 | Acknowledges the objection, then repeats the original pitch |
| 2 | Acknowledges, then pivots straight to a feature list |
| 3 | Reframes around the cost of the objection itself (e.g., what "too expensive" is actually protecting against) |
| 4 | Reframes around a quantified cost of inaction specific to that prospect |
| 5 | Pre-empts the objection earlier in the call so it doesn't surface as a late-stage stall |
A rep observed doing level 2 doesn't need "handle objections better" as a next step. They need one drill: take the three most common objections logged against their deals this month and rebuild the response at level 3, checked against something like an Objection-Handling Skill Practice Swipe File so the reframe has a real structure behind it rather than a vibe. That's a practice path. "Keep working on objection handling" is not.
The test
If you want to know whether a coaching programme is actually competency-based or just says so on a slide, skip the manager and ask a rep two questions: what specific competency are you working on right now, and what are you doing differently tomorrow because of it. If the answer is a category ("communication," "confidence") rather than a named, level-defined skill with a next action attached, the programme has part 1 and nothing else — however good the deck looks.
If you're building the taxonomy from scratch, start from something structured rather than a brainstorm — The Core 12 Sales Competency Framework gives you named competencies to work from instead of inventing your own on a whiteboard, and an Individual Development Plan (IDP) Template for Sales Reps forces the level-and-practice-path discipline that most CRM tagging skips entirely.
Competency-based coaching isn't hard to describe — three sentences will do it, as above. It's hard to resource, because parts two and three both cost real time from people who are already busy doing the job rather than documenting it. If that's not resourced yet, that's fine — structured feedback still beats none. Just take the phrase off the slide until the rubric and the practice cadence actually exist behind it.