Identifying Objectives and Alternatives
What this domain tests
Objectives are what the decision-maker ultimately values; alternatives are the means. Candidates must separate fundamental objectives (ends) from means objectives (ways to achieve ends), and must resist treating a stated alternative as the objective. A strong answer builds a means-ends network: ask "why does this matter?" to climb to ends, and "how could we achieve this?" to descend to means.
Know the difference between a constraint (a must-meet threshold) and an objective (something to maximize). Confusing them collapses the option set. Also know that alternatives should be generated before evaluation; premature evaluation kills creativity.
Traps in questions
- Means mistaken for ends: "Our objective is to buy new software" - buying is a means; the end may be faster reporting.
- Constraint as objective: treating a budget cap as a goal to minimize rather than a limit to respect.
- Anchoring on the first alternative: evaluating option one before generating others.
- Missing the do-nothing option: the status quo is always an alternative and must be compared.
Worked example
A city wants to reduce commute times. Means: add lanes, add bus lanes, congestion pricing, telework incentives. Ask why each matters: faster commutes may serve economic productivity and quality of life, which are ends. A constraint might be "no new debt." That constraint rules out some means but is not itself an objective. Listing ends first, then means, then constraints, produces a cleaner comparison.
Rule of thumb
Climb with "why?" until the answer is a value, not an action. Descend with "how?" until the answer is something you could actually do next quarter.