The Enablement Maturity Model Everyone Applies to Programs and Nobody Applies to Headcount
Maturity models get invoked for enablement content, cadence, and tooling all the time — and almost never for the one thing they should actually govern, which is how headcount scales stage to stage.
Every enablement leader I've worked with can recite a maturity model from memory. Ad hoc, then defined, then scaled, then optimised — or some four-box variant with different labels but the same shape. They'll use it to decide whether the certification programme needs a rebuild. They'll use it to justify a new content cadence. They'll use it to argue for a platform migration. What they almost never use it for is the one decision it's best suited to govern: how many people the function needs, doing what, at each stage. Headcount gets decided the way headcount always gets decided in sales orgs — reactively, one fire at a time — while the maturity model sits in a slide deck answering questions nobody asked it.
The model, briefly
Strip the jargon and most versions collapse to four stages:
- Ad hoc. No formal programme. Whoever's loudest in sales leadership decides what gets taught. Content is scattered, ownership is unclear.
- Defined. A curriculum exists. Onboarding has a shape. Someone owns the content calendar.
- Scaled. Certification is tiered, coaching is systematised, content production has a cadence independent of any one person's memory.
- Embedded. Managers deliver reinforcement as part of the job, not as a special enablement-run event. Enablement's own headcount growth slows because the muscle has moved into the line.
Everyone applies this to programme design. Almost nobody applies it to the org chart.
What each stage actually implies for headcount, and what happens instead
| Stage | What the model implies about headcount | What actually happens |
|---|---|---|
| Ad hoc | One generalist, doing everything badly, is correct — hiring a specialist here is premature | Leadership hires a senior enablement lead to fix morale, and the role has no programme to run |
| Defined | The generalist should split into content-owner and delivery-owner — two different skill sets one role can't hold at scale | The single generalist burns out and leadership adds a second generalist instead of a specialist |
| Scaled | Headcount should specialise further into a content owner, a certification owner, and a coaching-cadence owner | Enablement stays a flat team of generalists because nobody re-planned the org chart against the model |
| Embedded | Enablement headcount growth should flatten relative to rep headcount, because managers now carry reinforcement | Enablement keeps growing 1:1 with reps because nobody deliberately shifted reinforcement to managers |
The pattern in that right-hand column is always the same shape: hiring decisions get made in response to whoever complained loudest last quarter, not in response to what the model says the org needs to make the next stage stick.
The two failure modes this produces
Hiring the generalist too early. An org at the ad hoc stage, with no defined curriculum and no cadence, brings in a senior "Head of Enablement" expecting them to run a mature function on day one. There's nothing yet for that seniority to manage — no team, no cadence, no certification to administer. The hire spends eighteen months building the defined-stage artifacts a mid-level programme manager should have built, at a director's salary, and gets measured against scaled-stage outcomes the org was never structurally ready to produce.
Failing to specialise when scaling. The inverse failure, and more common. An org hits the scaled stage — tiered certification, real cadence, a content backlog — and keeps the same flat team of two or three generalists who built the defined stage, instead of splitting the role. Content quality degrades because the person building it is also running live coaching sessions. Coaching quality degrades because the coach is also fielding ad hoc content requests from a VP who wants a one-off deck by Friday. Nobody's incompetent; the org chart just never caught up to the stage the programme is actually at.
The ratio guide nobody publishes
As a rough operating guide, not a law:
- Ad hoc: one generalist can reasonably cover 50–75 reps, because there's no cadence to maintain, just fires to put out.
- Defined: the ratio tightens to roughly 1:40–50 once a real curriculum exists, because someone now has to maintain it rather than just react.
- Scaled: headcount should specialise rather than simply add more generalists — a content owner, a certification owner, and a coaching-cadence owner covering roughly 1:30–40 reps between them, each doing one job well instead of three jobs badly.
- Embedded: the ratio of enablement headcount to rep headcount should start falling, not rising, because managers are now doing the reinforcement enablement used to do themselves.
What to do before your next headcount request
Map what you actually have — not what the deck says, what genuinely exists — against the four stages. Use something concrete as the yardstick: if your certification programme still looks like a checklist rather than the tiered structure in a Sales Certification Rubric (Novice-to-Expert Levels), you're not at the scaled stage regardless of team size. If managers aren't running a defined reinforcement rhythm — check it against a Manager Coaching Cadence Checklist — you haven't reached embedded, no matter how many enablement staff you have.
Then make the headcount ask the model implies, not the ask that fixes this week's complaint. If the honest answer is that your whole function needs re-architecting rather than one more hire, that's an org design conversation, not a requisition — the Sales Org Design Blueprint is the right place to start that conversation, not the job posting.
A maturity model that only ever tells you what content to build next isn't a maturity model. It's a content calendar wearing a more expensive name.