Why decision tree matters to a first-time founder
A decision tree makes assumptions visible before a founder commits money or time. It separates choices the team controls from uncertain events it does not. Adding probabilities and pay-offs can reveal which assumptions drive the answer and where cheap research would improve the decision.
Examples of decision tree
A founder can launch now for $20,000 or run a $3,000 pilot first. The pilot has a 60% chance of strong demand, leading to launch, and a 40% chance of weak demand, leading to cancellation. Mapping both branches shows the cost, timing and possible outcomes clearly.
Common misunderstanding
It is not a prediction machine. Probabilities and pay-offs are estimates, and omitted outcomes can make the neat diagram misleading. A tree also differs from an organisational flowchart: its branches represent decisions or uncertain events, not reporting lines or a fixed operational process.
When to use it
Use one for a decision with a few meaningful stages, uncertain outcomes and measurable consequences, such as testing before launch or choosing a supplier. Keep branches manageable and test sensitive assumptions. For routine reversible choices, a short checklist may be faster and equally useful.