Core idea: A decision tree shows decisions, chance events and terminal outcomes as branches so the sequence of choices and information remains visible.
When this model is useful
Use it when later choices depend on earlier events, such as piloting before launch, testing before treatment or expanding after demand is observed.
The method is most useful when the question, alternatives and time horizon are stated before calculations begin. It should clarify tradeoffs and identify which assumptions deserve attention, not merely produce a score.
Inputs and evidence
Decision nodes, chance events, branch probabilities, outcome values, follow-up choices and any cost of waiting, testing or obtaining information.
Use consistent units, definitions and periods across options. Mark estimates clearly, record their source and use ranges when precision is not supported. Evidence should be proportionate to the cost, risk and reversibility of the choice.
Step-by-step method
Build the sequence from left to right, assign probabilities at chance nodes, value terminal outcomes and work backward to compare paths.
- Write the decision question and accountable owner.
- List realistic alternatives and eliminate any that fail hard constraints.
- Collect evidence and separate verified facts from assumptions.
- Run a base case and at least one downside test.
- Record the chosen option, accepted tradeoffs and review triggers.
Practical example
A company can launch fully, run a pilot or stop. The pilot costs money but may improve the later launch decision by revealing demand and technical problems.
The point of the example is not the exact numbers. It is the discipline of using the same boundaries for every option and making the decision drivers visible.
Common mistake and limitation
Large trees can imply unsupported precision and become unreadable. Combine similar states and focus on uncertainty that can change a decision.
Review whether the result changes under reasonable alternative assumptions. A close or fragile ranking should be presented as such rather than converted into false certainty.
Questions to ask before deciding
- What evidence would change the preferred option?
- Which consequence is missing because it is difficult to measure?
- Could a threshold or constraint override the numerical result?
- Who receives the benefits and who bears the costs or risk?
- When should the decision be reviewed?
Professional context: Legal, tax, investment, safety, medical, engineering and regulated decisions require qualified, jurisdiction-specific advice.