Field Notes: Four Teams, Four Methodologies, One Identical Failure

I was hired to audit four sales teams last year, for four different reasons, running four completely different named methodologies. One had been on Sandler for eleven years and wanted to know why win rates had gone flat. One had rolled out MEDDIC three years ago and wanted to know why forecast accuracy hadn't improved. One had just finished Challenger certification and wanted a baseline before wider rollout. One was SPIN-trained under a previous manager and wanted a sanity check ahead of a leadership change. Four different frameworks, four different tenures, four different stated problems. I listened to roughly thirty calls per team. All four had the identical failure, in the identical place, for the identical reason. The framework on the wall had nothing to do with it.

The four teams, at a glance

Team one: eleven years of Sandler, still skipping the pain funnel's floor

Sandler's whole architecture is built around not pitching until pain is quantified — the pain funnel is designed to force a rep down from surface complaint to business impact to personal impact before any product gets mentioned. Call after call, I heard reps nail the upfront contract beautifully, open with genuine curiosity, get a prospect to admit "yeah, onboarding takes too long" — and then, within one exchange, pivot straight to "so what we do is..." Nobody asked "too long compared to what" or "what does that actually cost you when it happens." The pain funnel has a floor. These reps were stopping two rungs above it, every single time, after eleven years of the exact vocabulary that tells them not to.

Team two: three years of MEDDIC, and Metrics still means a guess

The rep would say, on tape, "the prospect's target is 15% reduction in ramp time," log it in the Metrics field, and move straight to the champion conversation. Not once across the calls I sampled did a rep ask "how did you arrive at 15%" or "what's that worth in pounds once you get there." Three years of MEDDIC and the team had perfected populating a field called Metrics with a number nobody had pressure-tested. The eight-letter framework was fully installed. The one behaviour it exists to force — verifying a claim before building a business case on it — wasn't happening.

Team three: eighteen months of Challenger, insight straight into pitch

Challenger reps had the teaching pitch memorised and delivered it well — a genuinely differentiated point of view, landed with confidence. Then, the moment a prospect nodded along, the rep moved straight to "that's exactly what our platform does" without ever checking whether the nod meant "I recognise this problem" or "I've already solved this a different way and your insight doesn't change my plan." Challenger's own model requires a reframe step precisely to test whether the insight has actually shifted the prospect's thinking. Skipped, every time, in favour of the pitch that was clearly the part reps had rehearsed hardest.

Team four: newly SPIN-trained, implication questions asked then ignored

This team asked textbook SPIN questions — situation, problem, implication, need-payoff, in order, correctly labelled in their own notes. The implication question would land ("so if this keeps happening, what does that do to your Q4 number?"), the prospect would answer with something specific and quantified, and the rep would say "got it" and move to a feature walkthrough within the same breath — never restating the implication back, never letting the prospect hear their own number out loud twice. The question got asked. The answer got heard, logged, and then functionally discarded.

The pattern underneath all four

Every one of these teams skipped the same step: the point in the conversation where you make the prospect's stated pain uncomfortable and specific before you make yourself useful. Sandler calls it the pain funnel's floor. MEDDIC calls it verifying Metrics. Challenger calls it the reframe. SPIN calls it Implication and Need-Payoff. Four names, one behaviour, and four teams that had memorised the name well enough to pass a certification and still hadn't built the behaviour underneath it.

That's the actual finding, and it's an uncomfortable one for anyone about to spend the training budget on a fifth framework: the methodology was never the variable. All four frameworks contain a verification step. All four teams knew the label for it. None of the four had built the discipline of actually sitting in the discomfort of an unverified claim long enough to press on it, because pressing on it is socially harder than pitching, and pitching is what feels like progress.

Why this happens regardless of what's on the wall

Two reasons, and neither is about framework literacy.

First, verification questions produce silence, and silence reads as risk to most reps — a pause after "what does that cost you" feels like the call stalling, so the instinct is to fill it, and filling it with a pitch feels productive in a way that filling it with a second, sharper question doesn't.

Second, managers coach the pitch far more than they coach the verification step, because the pitch is the part they can hear going well or badly in thirty seconds, and the verification skip is only visible on a full call listen — which is exactly the audit I was doing, and exactly the thing weekly deal reviews rarely have time for.

What actually closes the gap

Not a new framework. A Discovery Call Scorecard that scores the verification moment specifically — not "did they ask a SPIN question" but "did they push once more after the first answer" — and a Call Coaching Feedback Template a manager fills in against real call audio, not memory, so the coaching targets the fifteen seconds that actually mattered instead of the general vibe of the call. If you want the sharpest version of the actual skill underneath all four frameworks' verification step, the Implication & Need-Payoff Question Cheat Sheet is framework-agnostic enough to bolt onto any of the four teams above without touching what's already on the wall.

None of these four teams needs to switch methodologies. All four need a manager who listens to full calls often enough to hear the exact half-second where a real question turns into a pitch, and who coaches that half-second specifically instead of the deck it came from.