Constraints vs Preferences in a Decision
Separate non-negotiable constraints from preferences so a high average score cannot hide an option that fails a real requirement.
Test each requirement
- Write the observable pass condition.
- Name the consequence of failure.
- Check both options with the same evidence.
- Move non-gating differences into weighted criteria.
Constraints decide eligibility
A constraint has a pass condition and a consequence if it fails. Preferences describe better or worse performance among eligible options. Calling every strong preference a must-have eliminates tradeoffs, while treating safety, legality, or affordability as a preference allows averages to excuse failure.
A false must-have
A requirement may be a disguised attachment to the current solution. Ask whether an alternative way of meeting the underlying need would still count as a pass.
Example: a lower-cost laptop that cannot run the work
Laptop B leads on price, battery, and weight but cannot run a required application. It is removed before scoring. Battery life remains a preference because both machines clear the minimum working-day threshold.
The decision rule
What to record before acting
Use pass-or-fail treatment only when failure makes the option genuinely unusable or unacceptable.
Apply the rule in context with audit constraints and criteria. Keep the evidence and assumptions with the decision so an outcome review can distinguish reasoning from luck.
Continue within decision skills
A Practical Tie-Breaker for Close Decisions
Break a close decision by finding the fragile assumption, comparing exit costs, or running the smallest test that could change the result.
A Practical Tie-Breaker for Close DecisionsHow to Set a Decision Deadline
Set a decision deadline from the cost of waiting, the expiry of evidence, and the last date a reversible test can still influence the choice.
How to Set a Decision Deadline