MEDDICC Without a Quality Bar Is CRM Theater [49]

Tim, a solution engineering leader, opens the episode by sharing a frustrating discovery: two opportunities from completely different customers (a 400-person logistics company and a regional bank) had nearly identical metrics entries using vague language like "improve efficiency, reduce manual work, save time." This prompted reflection on why his team of 12 SEs, whom he meets with weekly, allowed such generic documentation to persist.

The core issue identified is not that MEDDICC as a framework is flawed—team members can recite the letters—but rather that the organization never defined what excellence actually looks like in each field. The leader draws a parallel to his own experience as an SE where a 30-minute MEDDICC training session happened once and never surfaced again.

When the framework was rolled out organization-wide with launch events, e-learning, and certification badges, roughly half the reps maintained the fields properly while the other half filled them in the night before pipeline reviews, essentially completing a form rather than working a deal.

To establish a quality bar, the leader created one-page standards per segment. For mid-market logistics deals, a strong metrics entry must name a specific number the customer already reports internally, include the current value and desired target, and identify who owns the metric (e.g., "Pick error rate is 2.3%, they want it under 1, the ops director reports it monthly"). The other half of the page explicitly shows what a walkaway example looks like: when the honest answer is that no metric has been identified and the champion won't introduce the team to operations—marked as acceptable but indicating the deal isn't qualified yet.

The leader emphasizes that most standards only showcase the good version, which incentivizes people to fabricate positive entries. With three continental regional teams, the temptation was to write standards centrally and attach a completeness report, but this approach yielded 90% field completion with total fiction underneath.

The solution implemented was having each SE manager co-author the segment-specific standard with their sales counterpart, then checking two things: does the standard exist, and does anyone reference it? Reinforcement happens in existing meetings—deal reviews, forecast calls, and one-on-ones—where managers ask one specific question: "Read me the identify pain entry on your biggest deal." Reading it verbatim rather than paraphrasing reveals whether the documentation is real or superficial.

A director was piloting a tool that autofills MEDDICC from call transcripts to solve hygiene problems, but the leader initially dismissed this as "shit in, shit out." However, an unexpected diagnostic value emerged: when the tool couldn't fill in metrics fields from the transcript, it signaled that nobody asked the question during discovery, turning empty fields into a discovery diagnostic rather than a stenographer function.

The actionable recommendation is to compare two live opportunities in the same segment by reading their metrics fields back-to-back; if you can't distinguish which customer is which, the problem is not training but standards. The move involves writing one page per segment showing a great example and a walkaway example with the sales counterpart present, then reinforcing it through deal reviews for a quarter without announcement—the page itself changes nothing, but the repetition does.