Decision Criteria

The explicit and implicit standards a buyer will use to choose between options.

Explicit and implicit

Explicit criteria appear in an RFP or requirements list. Implicit criteria — risk aversion, an existing vendor relationship, a preference nobody will write down — frequently decide the outcome. Only asking about the explicit ones leaves you competing on a scorecard you did not help write.

Shape them early

The most valuable position is having helped define the criteria before they were fixed. Arriving after they are set means competing on someone else's terms.

How to surface and shape them

  1. Ask what would make this a clear yes, and what would make it a clear no. The second question produces far more information than the first.

  2. Separate stated criteria from operative ones. A requirements list describes what is defensible to write down, not always what decides.

  3. Find the implicit criteria: risk tolerance, incumbent relationships, internal politics, who gets blamed if it fails. These decide more deals than feature lists.

  4. Help define criteria before an RFP exists. The most valuable position is having shaped the standard, not meeting a standard someone else set.

  5. Check which criteria you do not meet and address them explicitly. Discovering a disqualifying requirement at procurement is the expensive version.

Where it misleads

  • Stated criteria are frequently reverse-engineered to justify a preference already formed, so meeting all of them does not guarantee a win.

  • Criteria change during long evaluations as buyers learn, and a list captured at discovery may not be the one used at decision.

  • Different stakeholders hold different criteria and rarely reconcile them, so there is no single list to meet.

  • Shaping criteria too obviously reads as manipulation and damages exactly the trust the tactic depends on.

RELATED TERMS

COMMON QUESTIONS

What are decision criteria?
The explicit and implicit standards a buyer will use to choose between options. The explicit ones appear in requirements lists and RFPs; the implicit ones — risk tolerance, existing relationships, who is accountable if it fails — are rarely written and frequently decisive.
How do you find a buyer's decision criteria?
Ask what would make this a clear yes and, more usefully, what would make it a clear no. The second question surfaces disqualifiers that a requirements conversation never reaches, and disqualifiers are what actually end deals.
Can you influence decision criteria?
Yes, and it is the highest-leverage position available — helping define the standard before an RFP exists rather than competing against one someone else set. It has to be done by genuinely clarifying the problem, because obvious criteria-shaping reads as manipulation.
Why do deals lose despite meeting all criteria?
Because stated criteria are frequently reverse-engineered to justify a preference already formed, and because implicit criteria never appeared on the list. A buyer can score you highest on every published requirement and still choose the option that feels least risky to be responsible for.

Learn how to apply this: RevOps 101: Revenue Operations Foundations

Definitions are the vocabulary. The courses are where you learn to operate it, with the interactive audit tools.

See the course