Enterprise deals are rarely lost because a solution cannot satisfy a published requirement. They are lost because the seller never learned how the buying group would actually judge the options. MEDDIC decision criteria are the technical, business, and personal standards buyers use to compare solutions and decide whether change is worth the risk. Strong sellers do more than collect a checklist. They identify who owns each criterion, why it matters, how it will be weighted, and what proof will create confidence.

Claim Your Assessment to identify where your team can strengthen MEDDIC decision criteria in live enterprise opportunities.

That distinction comes from experience in real deals. Dick Dunkel authored MEDDIC at PTC in 1996, and David Boyle taught the first MEDICC class. At RevCentric Partners, we treat Decision Criteria as a living map of how a buying group creates consensus. The objective is not to manipulate requirements. It is to help buyers make a complete, defensible decision while ensuring your differentiated value is evaluated fairly.

What MEDDIC decision criteria really reveal

Decision Criteria reveal the buyer's definition of a good decision. A product requirement may say that a platform needs a particular integration. The underlying criterion may be faster time to value, less operational risk, or confidence that users will adopt the change. Unless the seller connects the stated requirement to the reason behind it, the team cannot position value or judge whether it is truly qualified.

Criteria are not a feature checklist

A feature checklist describes what a solution can do. Decision Criteria explain what the buying group values and how it will compare alternatives. Two vendors may both satisfy a security requirement, but one may provide the implementation model that gives the chief information security officer greater confidence. That difference only matters if the seller understands how security, implementation, and executive risk will be assessed.

Good criteria are specific enough to test. They have an owner, a reason, a relative weight, and an acceptable form of proof. If a salesperson records only "easy to use" or "integrates with CRM," the criterion is too vague to guide strategy. The next questions are who defines ease of use, which workflows matter, what adoption target is expected, and how the buyer will verify the claim.

Criteria connect the rest of MEDDIC

Decision Criteria do not operate alone. Metrics quantify what success must produce. Pain explains why the buyer cannot accept the status quo. The Economic Buyer judges whether the business outcome is worth the investment. Decision Process explains how the organization will approve and execute the choice. A seller who isolates criteria from these elements may win a technical evaluation and still lose the business decision.

This is why disciplined qualification is more than filling boxes in a CRM. Teams need a shared understanding of the buyer's logic. Our Sellers Teaching Sellers approach helps revenue organizations turn MEDDIC from vocabulary into an operating discipline used in live opportunities. It complements a disciplined B2B sales methodology and a field-ready B2B sales playbook.

The three layers of enterprise decision criteria

Complex technology decisions usually combine technical, business, and personal criteria. The labels are useful, but the real value comes from understanding how the layers interact. A technically superior solution can lose when the implementation risk is unacceptable. A compelling business case can stall when an influential stakeholder believes the change threatens their credibility or control.

Technical criteria establish feasibility

Technical criteria determine whether the solution can operate in the buyer's environment. They often include architecture, security, performance, interoperability, data governance, and deployment requirements. Sellers should not simply ask for the technical checklist. They need to know which requirements are mandatory, which are preferences, who wrote them, and what business risk each one protects against.

Business criteria establish priority

Business criteria determine whether the solution deserves funding and organizational attention. They include economic outcomes, time to value, strategic alignment, adoption, implementation effort, and total cost. These criteria should connect to Metrics and Pain. When the business case relies only on the seller's assumptions, it is not yet buyer-owned and will be vulnerable during approval.

Personal criteria create commitment

Enterprise buying is organizational, but decisions are still made by people. A champion may want to prove an initiative can succeed. An operations leader may fear disruption. An executive may need a defensible choice that protects credibility. Personal criteria are not about exploiting emotion. They are about understanding what each stakeholder needs to support the decision with conviction.

How do you uncover the real decision criteria?

Uncovering criteria is not one discovery question. It is a structured investigation across the buying group. The seller builds an initial hypothesis, tests it with multiple stakeholders, and updates it as new information appears.

1. Map the buying group. Identify the Economic Buyer, champion, technical evaluators, business users, finance, procurement, legal, security, and any executive sponsors. For each person, document their role in defining or approving criteria.
2. Ask how the decision will be judged. Request the standards, tradeoffs, and evidence the buyer will use. Ask what must be true for the initiative to be considered successful and what could make an apparently capable vendor unacceptable.
3. Trace every criterion to its reason. When a stakeholder names a requirement, ask what risk it reduces or outcome it enables. This separates a genuine priority from a borrowed line in an RFP.
4. Determine ownership and weighting. Learn who authored each criterion, who can change it, whether it is mandatory, and how it ranks against other considerations. Criteria without an owner or weight remain assumptions.
5. Define acceptable proof. Agree on what the buyer must see to validate a claim. A demo, proof of concept, security review, reference call, or implementation plan may each serve a different stakeholder.
6. Confirm across stakeholders. Compare perspectives and surface conflicts early. If the business sponsor prioritizes speed while IT prioritizes control, the seller should help the team resolve the tradeoff before final approval.

Listen for gaps and contradictions

The most valuable discovery often appears when stakeholder answers do not align. A technical team may insist that a capability is mandatory while the Economic Buyer considers the outcome marginal. Procurement may optimize purchase price while operations cares about total cost and adoption. These contradictions are not obstacles to hide. They are signals that the buying group has not yet created consensus.

A strong champion can help the seller interpret the differences, but the seller should not rely on one person's version of the criteria. Single-threaded criteria create false confidence. Qualification improves when the team can cite the criterion, owner, weight, reason, and proof in the buyer's own language.

How sellers shape criteria without manipulating the buyer

Criteria are often incomplete early in a buying cycle. Buyers know the outcome they want, but they may not yet understand every operational dependency or risk. A credible seller contributes expertise by helping the buying group consider the standards required for success. That is shaping. Manipulation begins when a seller inserts irrelevant requirements solely to eliminate competitors.

Start with the buyer's desired outcome

A differentiated capability deserves to become a criterion only when it materially improves an outcome or reduces a meaningful risk. Begin with the buyer's Metrics and Pain, then explain the connection. For example, an implementation capability matters when it shortens time to value, protects continuity, or increases adoption. The capability itself is not the business criterion; its impact is.

Teach the consequence of omission

Practitioner credibility matters here. Buyers value a seller who can explain what tends to go wrong after the contract is signed. Share patterns, tradeoffs, and questions that help the team build a more complete evaluation. Give the buyer enough context to decide whether the criterion belongs. This makes the process more defensible and positions the seller as a useful partner rather than a product advocate.

Shape before the evaluation hardens

An RFP often reflects work done before a seller became involved. By that point, criteria may favor an incumbent or a competitor that helped write them. The answer is not to attack the document. The seller should understand the business objective, identify gaps that could undermine the result, and earn permission to propose better standards. When criteria are already fixed and cannot be influenced, the team must decide honestly whether the opportunity is worth pursuing.

How do you validate decision criteria before forecasting?

Stated criteria are not automatically validated criteria. A stakeholder may describe a preference as mandatory, omit a politically sensitive consideration, or assume another executive shares their view. Before a deal earns forecast confidence, the seller should verify the criteria with the people who define and approve the decision.

Separate assumed, stated, and validated criteria

Assumed criteria come from the seller's experience or early hypothesis. Stated criteria have been voiced by at least one buyer. Validated criteria have a confirmed owner, reason, weight, and acceptable proof, and they are understood across the relevant buying group. This distinction prevents teams from treating a productive discovery call as complete qualification.

Use a mutual validation review

Summarize the criteria in a buyer-facing document or mutual action plan. Review the standards, their priorities, the proof required, and any unresolved questions. Ask the champion and other owners what is missing or inaccurate. The goal is not to force a scorecard onto the buyer. It is to make the decision logic explicit enough that both sides can prepare for a fair evaluation.

Revalidate when the deal changes

Decision Criteria can change when a new executive enters, budgets tighten, security identifies risk, or implementation timing shifts. Treat validation as an ongoing activity. During deal reviews, managers should ask what changed, who confirmed it, and how the team knows. A criterion last discussed months ago may no longer support a reliable forecast.

Explore RevCentric's practitioner-led services to turn these criteria into stronger opportunity coaching and forecast discipline.

A practical MEDDIC decision criteria checklist

A practical MEDDIC decision criteria checklist confirms that each important standard has a named owner, business reason, relative weight, and agreed form of proof. Use the questions below to inspect whether a complex opportunity has actionable criteria and to guide specific coaching conversations instead of another box-ticking exercise.

Technical criteria

• Have we identified the capabilities and workflows that are genuinely mandatory?
• Do we know which architecture, integration, security, data, and compliance requirements matter most?
• Can we explain the operational or business reason behind each major technical requirement?
• Do we know who authored each requirement and who can approve an exception?
• Have we agreed on the proof needed, such as a demonstration, technical review, or proof of concept?

Business criteria

• Are the expected outcomes quantified with buyer-owned Metrics?
• Does the business case reflect time to value, adoption, implementation effort, and total cost?
• Has the Economic Buyer confirmed what makes the investment worthwhile?
• Do we understand the strategic priorities and risks that will affect funding?
• Can the buyer defend the decision to finance and executive leadership?

Personal criteria

• Do we understand what success means for the champion and other influential stakeholders?
• Have we identified concerns about credibility, workload, disruption, control, or career impact?
• Are we helping each stakeholder communicate the decision confidently inside the organization?
• Do we know who may resist the change and why?

Ownership, weighting, and evidence

• Does every important criterion have a named owner?
• Do we know which criteria are mandatory, preferred, or negotiable?
• Have we identified conflicts between technical, business, and personal priorities?
• Has the buying group agreed on how alternatives will be compared?
• Is the required proof scheduled in the Decision Process?
• Have all material criteria been revalidated recently?

If several answers are unknown, the opportunity may still be real, but it is not fully qualified. Managers can use these gaps to coach a specific next action rather than offer generic advice such as "do more discovery." That is how MEDDIC becomes useful in the trenches.

Where decision criteria work breaks down

Decision Criteria work breaks down when sellers mistake documented requirements for shared buying-group truth. The most common failures are accepting an RFP at face value, confusing criteria with process, relying on one contact, and treating early validation as permanent.

The seller accepts the RFP at face value

An RFP is a snapshot of criteria, not proof that the full buying group agrees with them. It may overrepresent technical preferences and underrepresent adoption, executive value, or implementation risk. Sellers should respect the process while testing whether the document captures the standards that will truly decide the deal.

The team confuses criteria with process

Decision Criteria define how alternatives are judged. Decision Process defines the steps and approvals used to reach a decision. A security requirement is a criterion. A scheduled security review is part of the process. Both matter, but confusing them leaves gaps in qualification and execution.

One contact defines the whole decision

Even a strong champion sees the decision through one lens. When a seller relies on that single view, late-stage objections appear surprising. Multithreading is not merely adding contacts. It is learning how different stakeholders define value, risk, and acceptable proof, then helping the group resolve competing priorities.

Validation happens once

Teams sometimes capture criteria early and never revisit them. Complex deals evolve. Revalidation should happen after major events, including executive changes, technical findings, budget reviews, and competitive moves. A current view of the criteria makes coaching sharper and forecasts more credible.

Turn criteria into a repeatable operating discipline

Decision Criteria become powerful when sellers, managers, and enablement leaders use them consistently. Sellers need the skill to uncover and shape criteria in live conversations. Managers need a common language for inspecting evidence and coaching gaps. Revenue Operations needs fields and workflows that support judgment rather than encourage superficial completion.

That is why RevCentric emphasizes "Sellers Teaching Sellers" and "Teaching in the Trenches." Dick Dunkel authored MEDDIC at PTC in 1996. And David Boyle taught the first MEDICC class. Their experience reinforces a simple point: methodology produces value only when it changes seller behavior in actual customer situations. The same principle applies whether your organization uses MEDDIC, MEDDPIC, MEDDPICC, or MEDDICC.

A practical operating rhythm includes opportunity reviews that distinguish assumptions from evidence, coaching tied to specific gaps, and field practice using active deals. It should reinforce the broader enterprise sales strategy rather than operate as an isolated qualification exercise. Over time, better criteria work improves qualification, strengthens buyer consensus, and gives leaders a more reliable view of risk.

Frequently asked questions

What are Decision Criteria in MEDDIC?

Decision Criteria are the technical, business, and personal standards a buying group uses to evaluate alternatives. Effective criteria include an owner, reason, relative weight, and agreed form of proof.

What is the difference between Decision Criteria and Decision Process?

Decision Criteria define how the buyer will judge solutions. Decision Process defines the steps, stakeholders, approvals, and timing used to reach and execute the decision.

Can sellers influence Decision Criteria?

Yes. Sellers can ethically shape criteria by teaching buyers about important outcomes, dependencies, and risks they may not have considered. The criterion should support the buyer's success, not exist only to exclude a competitor.

How often should Decision Criteria be validated?

Validate criteria throughout the opportunity and after any major change in stakeholders, budget, requirements, technical findings, or timing. A criterion is not reliable simply because it was discussed early in the deal.

Who owns Decision Criteria in an enterprise deal?

Different stakeholders own different criteria. Technical evaluators may own feasibility requirements, the Economic Buyer owns investment logic, and users or champions often own adoption concerns. Sellers must map ownership across the buying group rather than rely on one contact.

Claim Your Assessment

If your team records Decision Criteria but still discovers late-stage surprises, the issue is not more terminology. It is field execution. RevCentric Partners helps revenue teams turn original-practitioner MEDDIC expertise into repeatable deal behavior, coaching, and forecast discipline.

Claim Your Assessment to identify where your qualification process is strong, where evidence is missing, and how to improve execution in live opportunities.