Start with the distinction
Core relationship: Start with the decision objective and stakeholders. Mark non-negotiable constraints, then define a small set of non-overlapping preferences with observable scoring anchors.
For define decision criteria before comparing options, begin with write the objective and finish with anchor the scale. The sequence keeps the starting facts, intermediate result, and final limit visible instead of relying on memory.
Work through the reasoning
Write the objective
State what the decision should achieve and over what period. Capture the result before moving to identify constraints. A written output shows whether the next deduction follows from the evidence or quietly adds a new assumption.
Identify constraints
Remove infeasible options before weighted scoring. Compare this output with the warning about criteria from features. If that failure still fits, revise the representation before using the result in another deduction.
Define preference criteria
Avoid double-counting the same benefit under different names. Use define preference criteria as a checkpoint. Name the input, the change made, and the conclusion that becomes available so another reader can reproduce the move.
Anchor the scale
Describe what low, middle, and high scores mean before seeing option performance. Finish by stating what this step establishes and what it leaves undecided. That boundary prevents a valid local conclusion from being stretched beyond the question.
Concrete example
Write the objective in the case
A software choice may require regional data storage as a constraint. Response time, total cost, training effort, and integration reliability can then be scored as preferences using defined evidence.
Why anchor the scale matters
The case starts with write the objective, then uses identify constraints to control the next inference. The conclusion is acceptable only after anchor the scale. Changing any fact that supports those moves can change the answer, while an unrelated detail should not.
Where the method breaks
Criteria from features
A vendor feature list is not the same as stakeholder value. Return to write the objective and rebuild only from information the problem actually provides.
Everything is critical
If every preference becomes a constraint, no tradeoff remains possible. Compare the disputed move with define preference criteria; the two should use the same definitions and direction.
Weights without evidence
A precise percentage cannot repair a vague criterion. Run the practice task while deliberately watching for weights without evidence. Record the first point where the reasoning begins to drift.
Check against criteria from features
Questions for identify constraints
- Can another reader reproduce write the objective from the stated information?
- Did you complete identify constraints without reversing or enlarging the claim?
- Does the result survive the failure mode criteria from features?
- Which part remains uncertain after anchor the scale?
This check is specific to the method above. A clear answer should expose the evidence chain and the point where a different fact would produce a different conclusion.
A short practice task
Choose an upcoming decision and write two constraints plus four preferences before listing options. Ask another stakeholder what important outcome is missing.
Continue after anchor the scale
Use the problem prioritization guide for the broader method, then apply the idea in the decision matrix calculator. Keep the written reasoning so the next attempt can improve a specific step rather than simply repeat the exercise.
Compare this method with Run a Pre-Mortem Before an Important Decision, then continue to Opportunity Cost in Problem Prioritization for a different reasoning task.