A Sales Methodology and a Skills Framework Are Not the Same Thing
MEDDIC tells a rep what to do on a call. It doesn't tell you what they're good at — and conflating the two is why methodology rollouts keep 'not sticking.'
Every enablement leader has sat through the same post-mortem. The methodology rollout was thorough — training days booked, certification quiz passed, laminated one-pagers on every desk — and six months later reps are back doing exactly what they did before. The verdict is always the same: "it didn't stick." The verdict is almost always wrong. What didn't stick wasn't the methodology. It was a skill the methodology assumed the reps already had.
Two different documents pretending to be the same thing
A methodology is a sequence. MEDDIC tells a rep the order to establish Metrics, Economic buyer, Decision criteria, Decision process, Identify pain, Champion. Sandler tells a rep to build rapport, qualify pain, and hold off proposing until pain and budget are both confirmed. Challenger tells a rep to teach, tailor, and take control. Every one of these is a script for sequence and emphasis — what to cover, and roughly when.
None of them tell you whether the rep in front of you can actually execute the step. MEDDIC says "identify the economic buyer." It says nothing about whether your rep has the competency to get a gatekeeper to introduce them to one, or to reframe a champion conversation into an economic-buyer meeting without the champion feeling bypassed. Sandler says "qualify pain before proposing." It says nothing about whether the rep can ask a second and third layer of discovery question once the first, comfortable answer arrives. Challenger says "teach a commercial insight." It says nothing about whether the rep can build one, or deliver it without sounding like they're reading a slide.
That's the whole distinction in one line: a methodology tells a rep what to do; a skills framework describes whether they're able to do it.
Where rollouts actually break
| Methodology step | What it prescribes | Competency it silently assumes | What happens when the competency is missing |
|---|---|---|---|
| MEDDIC — Economic Buyer | Identify and engage the EB | Multithreading / stakeholder access | Rep keeps running the deal through the champion and marks the EB box "assumed identified" in the CRM |
| Sandler — Pain funnel | Layer questions from surface to root cause | Discovery questioning depth | Rep asks one good open question, gets a workable answer, and stops — pain stays surface-level |
| Challenger — Teach | Deliver a commercial insight that reframes the buyer's view | Commercial insight construction + reframing under pushback | Rep delivers a generic industry stat instead of an insight built for this buyer's specific situation |
| MEDDIC — Decision Criteria | Shape criteria before RFP stage | Consultative influence / early engagement | Rep engages after criteria are set and calls the loss "we were late to the deal" |
| Any — Negotiation close | Hold value, trade concessions for commitments | Negotiation structure under pressure | Rep concedes on price early to "keep momentum," undercutting the whole methodology's earlier work |
Look at that middle column. None of it is methodology-specific. Discovery questioning depth, multithreading, commercial insight construction, negotiation structure — the same four or five competencies keep showing up underneath completely different branded methodologies. That's the tell. If your Challenger rollout and your MEDDIC rollout are both quietly failing on the same handful of reps, the shared cause isn't either methodology. It's the skills underneath both of them.
The diagnostic enablement leaders skip
Most rollouts start with the methodology and hope the skill arrives as a side effect of repetition. Run it backwards instead. Before you certify anyone on a new methodology, grade the underlying competencies it depends on, on real calls, not a role-play in the training room. If half your team can't hold a second layer of discovery question without going quiet, no amount of MEDDIC terminology painted over that gap will close it. You'll get reps who can recite "what's the economic impact of the problem" as a memorised line and can't follow up when the answer is vague — which, on tape, sounds worse than not asking at all, because now it's obviously scripted.
This is also why methodology "refreshers" so rarely fix anything. A refresher re-teaches the sequence. It doesn't touch the competency. Send a rep who lacks discovery depth through Challenger training twice and you get someone who can now recite two methodologies' worth of vocabulary while still asking single-layer questions on the call.
What a skills framework actually gives you that a methodology can't
A competency framework — the kind behind The Core 12 Sales Competency Framework — gives you something a methodology structurally can't: a way to grade a rep independent of which playbook they were trained on. A rep can be excellent at commercial insight and still run a technically imperfect MEDDIC sequence, and close more than the rep who nails every MEDDIC box with a generic pitch. The methodology grades compliance with a sequence. The framework grades whether the underlying capability exists, which is the thing that actually predicts outcome regardless of which methodology sits on top of it.
If you're mid-rollout and something isn't landing, don't reach for a new methodology. Check the Deal Health Calculator (MEDDIC-Weighted) against actual call behaviour on the specific step that's stalling, and use something like the Discovery Questioning Skill-Builder Cheat Sheet to work the underlying skill directly rather than re-running the same sequence training a third time.
Methodologies are useful. They give a team shared vocabulary and a shared sequence to check deals against. But a shared vocabulary isn't a shared capability, and enablement teams that keep buying new methodologies to fix the last one's "failure to stick" are buying the same non-solution in different branding. The rollout wasn't the problem. The skill gap wearing its costume was.