Identify Pain in MEDDPICC (And Why You Need to Implicate It)

A common New Year’s goal is to lose weight.

Most people fail. Because it stops at, “I want to lose weight.”

That’s a problem. It isn’t a reason to change.

Now ask: Why do you want to lose weight? What happens if you don’t? Take the problem and make it much bigger. Now the problem isn’t weight. It’s life itself.

That’s implicating pain. And it’s the difference between a deal that sits and a deal that moves.

What Identify Pain Really Means

MEDDPICC calls it Identify Pain. In my own discovery guide, I call it Implicate Pain, on purpose.

Identifying pain is hearing a problem. Implicating pain is connecting the problem to the broader business consequences of not solving it.

Most sellers stop at the first step. They hear a familiar trigger like “pipeline problem,” “visibility problem” or “efficiency problem,” assume they understand it, and jump to a solution.

They might even be right. But the buyer doesn’t feel heard, the messaging never sounds like them, and abstract pain is easy to live with.

This is also why a CRM checkbox proves nothing. Clicking “Pain Identified” doesn’t mean you know pain.

Why It Matters

When the pain stays at the surface, everything that follows becomes fragile:

• Your demo becomes generic.
• Your champion is unarmed.
• Your business case is a guess.
• Your forecast is hope.

It’s also how you lose to the status quo. When a buyer acknowledges a problem but never feels its full weight, doing nothing wins. That’s the first gate in Competition.

The Progression: Problem, Implication, Metrics

There’s an order to this. Skip steps and you’ll pitch too early.

1. Identify the problem. What’s happening, and where exactly does it show up?
2. Implicate the pain. What happens because of it? What breaks downstream? What risk increases? What goals become unattainable?
3. Quantify it into metrics. How big is the cost, in dollars, hours, conversion rates, cycle time, churn, risk exposure or missed revenue?

If you don’t implicate the problem, you won’t create urgency. If you don’t quantify it, you won’t earn priority. Step three is where Identify Pain hands off to Metrics.

What Implicating Pain Sounds Like

The drill-down doesn’t always sound the same, but it follows a pattern:

• The problem: “I just heard you say X. Can you tell me more about that?”
• The implication: “What happens because of that? Who else feels it? What are you struggling to achieve because of this?”
• The history: “How long has this been going on, and what have you tried to fix it?”
• The baseline: “If you had to guess, what do you think this is costing the business in time, risk or actual dollars?” If they don’t know, ask, “Who would know?”

The first answers are almost always real and almost always useless for a business case. When I sold Recruitment Process Outsourcing to an auto body chain, the executives first told me, “We can’t service cars fast enough. Customers are complaining. Insurance companies are frustrated with us.”

So I kept asking, “Why does that matter?” until the CFO put his hand up and asked what I was getting at. One more question found the number, in their own math. (The full story, with the numbers, is in Cost of Inaction.)

That’s the point of implication. The case for change stops being yours to make. It becomes theirs.

How to Grade It: What Done Looks Like

Done means you can connect the whole chain: problem > solution > value > justification for change > downstream business impact.

Red sounds like every other deal. “We have a pipeline problem.” “Forecast is messy.” “We need visibility.” It might be true, but it isn’t usable. Red usually happens when a seller hears a problem and goes straight to a solution.

Yellow feels meaningful, which makes it dangerous. You’ve identified a problem but haven’t connected it to the bigger picture, or you’re working from only one stakeholder’s version of reality.

Green sounds like: “This is happening, in this workflow, to these teams, it’s costing this amount, it creates these second-order consequences, and leadership agrees it must be solved in this timeframe.”

Green also requires more than one voice. I don’t care if you’re speaking to the CEO, they don’t speak for the business. CEOs see CEO problems. CFOs see CFO problems. That’s why green means the pain is implicated for every relevant persona and tied to a business priority.

Common Mistakes

• The seller’s reflex. You hear a problem and jump to “I can solve that,” or move on to your next discovery question. That’s where deals fail to progress to yellow or green.
• No unique win story. If you can swap the customer’s name on the opportunity and the problem still applies perfectly, you’re stuck in a generic label. Generic problem labels don’t close deals.
• Mistaking pain for priority. Pain can be real and still not get funded. If you can’t connect it to a strategic objective, it becomes background noise. Ask the problem owner, “What priorities can we attach this project to?”
• Stopping at verbal implication. Many sellers get the buyer to feel the implication on a call, then never translate it into a narrative the buyer can repeat internally.

Plays to Move Pain From Red to Green

Face of Discovery. Before you meet a new stakeholder, build a hypothesis of what they care about. Put it on a slide with their picture and three to five bullets, then invite them to correct you: “I did my homework on you. I might be wrong on some of this, but here’s what I think you care about. Can you correct me and help me unpack it?” It shortcuts the shallow “what challenges do you have” dance.

Peel the Onion. When they name a problem, don’t move on. Ask what happens next, then what, why that matters, who else it impacts, what happens if they fix it, and what happens if they don’t. You’ve peeled enough when a metric, a number or something quantifiable appears.

Faces of Impact. Interview a cross-section of people, ask the same questions, and build a simple deck with each person’s photo and the specific problems and metrics they described. Words are easy to ignore. Faces are not. I won a $3.6 million deal with this play. The executive team didn’t believe the issue was as severe as my champion said, so we interviewed end users around the world and documented what they told us. It revealed a global problem they couldn’t dismiss.

Value Pyramid. Build it with the buyer, from the bottom up: operational pain, functional impact, strategic consequence, and the big-picture gain. Fill in what you believe and invite them to challenge it. The deal stops sounding like a tool purchase and starts sounding like a business decision.

Once the pain is implicated, the quantifying plays (Back of the Napkin, Cost of Delay) live on the Metrics page.

How It Connects to Deal Management

MEDDICC calls it Identify Pain and Metrics. SPIN calls it Problem and Implication. Sandler calls it the Pain Funnel. Different words, same destination.

In Deal Management, implicated pain lives in two criteria. Current State is the verified reality of what’s happening today, with the problem implicated and quantified into a baseline. Change Justification turns that pain into a narrative an executive would defend: why change, why now, and what it costs to wait.

That’s why the done definition runs all the way to justification and downstream impact. Pain you can’t carry into a business case stays pain.

Where to Go Deeper

• How to Build a Business Case turns implicated pain into a decision document, with a free template.
• 75 MEDDPICC Discovery Questions has the full question set for every letter.
• Next letter: Champion. Or go back to the MEDDPICC overview.