ThinkWork

Your Methodology Switch Isn't the Problem. Your Ramp Program Is.

Before you blame the framework for the miss, check the onboarding curriculum. Most methodology switches are a company re-labeling a problem it never actually fixed.

I've sat in the room for three of these relaunches at three different companies, and the pattern is close enough to a photocopy that I can predict the slide numbers. Slide six: "why SPIN isn't working for us anymore." Slide eleven: "introducing MEDDPICC." Slide twenty: a new deal-review template with different acronym boxes. Eighteen months later, same company, same slide six with a different framework's name on it. Nobody in that room ever asks the question that actually matters: did the reps who "failed" under the old framework ever get properly trained on it in the first place, or did they just get handed the vocabulary and left to work out the behaviour on their own?

Almost every methodology switch I've been near skips that question, because answering it honestly means admitting the ramp programme is the actual problem, and that's a much less comfortable thing to put in a board deck than "the market has moved past this framework."

The tell: same reps, new acronym

Here's the diagnostic I use, and it costs nothing to run before you sign a new methodology contract. Pull ten reps who are "struggling" under the current framework. Ask them to define, out loud, what a single core term actually means in behavioural terms — not the definition, the behaviour. Under MEDDIC, ask what "identify the Economic Buyer" looks like as an actual action on a call, not as a CRM field. Under SPIN, ask them to demonstrate an Implication question live, on a made-up scenario, right now.

The overwhelming majority of the time, what you get back is a rep who can recite the acronym expansion perfectly and cannot produce the behaviour on demand. That's not a framework failure. That's a rep who was handed vocabulary in a two-hour kickoff session and never actually drilled the underlying skill until it was automatic. Swapping MEDDIC for Challenger doesn't fix that rep. It gives them a new set of words to not be able to demonstrate.

What ramp programmes skip, in order

Most onboarding curricula I've audited get the sequence backwards. They teach the framework's vocabulary first, test recall with a quiz, and call the rep "certified." The actual skill underneath the vocabulary — the discovery instinct, the ability to build and defend a business case, the willingness to disqualify a bad-fit deal — gets left to "pick it up on the job," which really means "pick it up by watching whichever senior rep happens to sit near you."

The methodology switch is a company doing the same thing again, faster, and with more confidence, because now there's a new consultant in the room telling everyone the last framework was the problem.

Why this cycle is so expensive and so easy to keep repeating

Cost centreWhat actually happensRough scale on a 40-rep team
Consultant and licensingNew methodology contract, workshop days, materials£80k–£250k depending on vendor and team size
Rep time off quota2–3 days of kickoff plus a soft ramp-down either side5–8 selling days per rep lost
CRM and process rebuildNew deal-review fields, new forecast categories, new dashboardsWeeks of RevOps time, usually underscoped
The part nobody countsReps who were never actually incompetent get quietly blamed for "not adopting the new framework," and good people leaveAttrition of reps who'd have been fine with proper reinforcement

That last row is the expensive one and it's the one that never makes the retro. A rep who was undertrained on SPIN's Implication questions doesn't magically develop the same underlying diagnostic instinct because the acronym changed to MEDDPICC. If anything, they now have two half-learned vocabularies competing for the same behaviour, and a manager who's confused about why "certified" reps still aren't doing the thing the certification was supposed to prove.

What actually breaks the cycle

Before the next methodology conversation, run the audit rather than the RFP. Three questions, in order:

  1. Was the last framework ever actually taught as behaviour, with graded practice reps, or was it taught as vocabulary with a quiz at the end? If it's the latter, a new framework changes nothing — you'll be back here in eighteen months with a new acronym and the same gap.
  2. Do you have a certification standard that measures demonstrated skill against a rubric, or a pass mark on a knowledge test? A knowledge test tells you who can define a term. It tells you nothing about who can execute it live, which is the only thing that shows up in a deal.
  3. Is your ramp reinforcement structured past week one, or does "certified" mean "attended the workshop"? Skill decays fast without deliberate reinforcement in weeks two through twelve — that's not a framework problem, it's a curriculum design problem, and it exists identically under every methodology you could pick.

If the honest answer to all three is "no, we've never actually built that," don't sign the new methodology contract yet. Build a Competency-Based Onboarding Curriculum Framework first, one that teaches the underlying behaviours — discovery, business-case construction, deal qualification — as trained and graded skills rather than acronym definitions. Pair it with a genuine reinforcement cadence using something like a Manager Coaching Cadence Checklist so the skill doesn't quietly decay the moment the kickoff excitement wears off. And track whether it's actually working with a Time-to-First-Deal Tracker Template instead of a certification pass rate, because a pass rate measures recall and a first-deal timeline measures the thing you actually care about.

Do that first, with your current framework, and you'll find out something uncomfortable: most of the "framework isn't working" problem disappears without buying a new one. What's left after that — genuinely outgrown, genuinely mismatched to your deal complexity — is a much smaller and much more honest reason to switch.

The framework was never the variable that mattered. It's just the easiest one to blame, because blaming it doesn't require anyone to admit the ramp programme was broken the whole time.

New posts

Get new posts in your inbox.

A fresh post most mornings. No digest spam, no course funnel — just the post, and one click to stop. Prefer a reader? Subscribe by RSS.

Confirm by email first. Unsubscribe any time.