Define the Decision Before Comparing Options
Define the decision as one action, one owner, one deadline, and one outcome before comparing options that may solve different problems.
A clear decision has a boundary
A vague question such as which tool is best invites unlimited research. A bounded question names who will act, what job must be done, when the choice takes effect, and which alternatives are actually eligible. This prevents features for a different problem from controlling the comparison.
Write a one-sentence decision brief
- Name the person or group with authority.
- State the outcome the choice must support.
- Set the decision date and review date.
- List only options that can meet the same job.
Example: choosing software for one workflow
A team initially asks which project platform is best. It rewrites the decision as which of two approved platforms should support a 12-person client-delivery workflow from January through June. Security approval and data export become gates, while unrelated enterprise features leave the comparison.
When the frame is too narrow
A narrow frame can hide a better third option or an upstream problem. Before locking it, ask whether changing the process would remove the need to choose at all.
The decision rule
What to record before acting
Compare options only after they have been defined as competing ways to achieve the same bounded outcome.
Apply the rule in context with structure the two eligible options. Keep the evidence and assumptions with the decision so an outcome review can distinguish reasoning from luck.
Continue within decision skills
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.
Constraints vs Preferences in a DecisionA 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 Decisions