Decision Tree Analysis Calculator
Advanced decision analysis with expected monetary value and risk assessment
Use this when
Use this during initiation, governance design, stakeholder planning, integrated change control, or a structured option-selection workshop.
Prepare
Agree decision criteria and definitions first, then gather stakeholder evidence, strategic objectives, constraints, impacts, and accountable owners.
Decision supported
The output supports transparent prioritization, ownership, engagement planning, change recommendations, and escalation paths.
Practitioner guidance and limitations
Interpret and act
Use the calculation to make assumptions visible and facilitate alignment. Record the decision, rationale, dissent, owner, and review date.
Professional caution
A score can hide disagreement. Facilitate the conversation behind each rating and check for bias, double counting, and missing stakeholders.
Common questions about this analysis
What does the Decision Tree Analysis Calculator help a project manager decide?
Advanced decision analysis with expected monetary value and risk assessment Use the result to support a documented decision, action, threshold, or follow-up rather than treating it as a stand-alone score.
How reliable is the Decision Tree Analysis Calculator?
Reliability depends on the quality, consistency, and status date of the inputs. Validate source data, record assumptions, and test material results against your approved baseline and expert judgment.
When should the Decision Tree Analysis Calculator not be used on its own?
A score can hide disagreement. Facilitate the conversation behind each rating and check for bias, double counting, and missing stakeholders.
Which inputs require the most attention?
Agree decision criteria and definitions first, then gather stakeholder evidence, strategic objectives, constraints, impacts, and accountable owners.
What should be shared with stakeholders?
Share the result together with units, status date, source data, assumptions, confidence or range, interpretation, recommended action, owner, and next review date.
Learn the topic: concept, PMP lens, and common mistakes
Core concept
Governance tools make decision criteria, accountability, stakeholder needs, and change impact explicit. Their value comes from the conversation behind the rating, not the score alone.
Professional application
Facilitate agreement on definitions first, document dissent and assumptions, then record the decision, accountable owner, and review trigger.
PMP exam and practice lens
Integrated change control evaluates impact before approval. Stakeholder engagement is planned and monitored throughout delivery. In RACI, each activity should have clear accountability.
Common mistakes
- Scoring criteria before agreeing what each score means
- Double-counting related criteria
- Ignoring affected stakeholders who do not have formal authority
Before you trust the result
- Confirm one status date and consistent units.
- Retain the input source, owner, and confidence.
- Sense-check the result against an independent benchmark.
- Record the decision, action owner, and review date.
Related practice tools
Multiple outcome evaluation
EMV calculations
Probability analysis
Best path identification
Decision Parameters
For present value calculations
Analysis time period
Decision Options
Likelihood of success
Expected financial result
Likelihood of success
Expected financial result
What is Decision Tree Analysis?
Decision tree analysis is a quantitative risk analysis technique recognized by the PMBOK Guide as a core tool within the Perform Quantitative Risk Analysis process. It uses a tree-like model of decisions and their possible consequences, including chance event outcomes, resource costs, and utility values. Each branch represents a decision path, and each node represents either a decision point where you choose an action or a chance point where probability governs the outcome.
The foundation of decision tree analysis is Expected Monetary Value (EMV), which multiplies the probability of each outcome by its financial impact. By calculating EMV for every branch and summing across chance nodes, project managers can identify the decision path that maximizes expected value. This technique is particularly powerful when you face multiple decision alternatives with uncertain outcomes, such as choosing between building a custom solution versus buying an off-the-shelf product.
Decision trees connect directly to sensitivity analysis because they reveal which probability or outcome variable has the greatest effect on the final EMV. When you adjust a single probability or outcome value and observe how the optimal decision changes, you are performing a sensitivity analysis on your decision tree. This connection is frequently tested on the PMP exam and is a hallmark of rigorous project risk management.
Decision Tree EMV Formula Explained
Probability is expressed as a decimal between 0 and 1, representing the likelihood of a specific outcome occurring. Financial Outcome is the monetary value associated with that outcome -- positive for gains, negative for losses. The Expected Monetary Value for a decision branch is simply the product of these two values.
For decisions with multiple possible outcomes on a single branch, you sum the EMV of each outcome: EMV(total) = (P1 x O1) + (P2 x O2) + ... + (Pn x On). The decision with the highest total EMV is mathematically optimal when you are risk-neutral. Present value adjustments can be applied using the discount rate and time horizon to account for the time value of money.
Step-by-Step Guide to Decision Tree Analysis
Define the decision clearly and identify all viable alternatives. Each alternative becomes a major branch emanating from the root decision node.
Identify the chance events (uncertainties) that affect each alternative and assign probabilities. Ensure probabilities at each chance node sum to 1.0.
Estimate the financial outcome for each end branch. Include all relevant costs, revenues, and intangible benefits converted to monetary terms.
Calculate the EMV for each branch by multiplying probability by outcome. Roll up values through chance nodes by summing EMVs, then compare decision branches.
Select the alternative with the highest EMV as your optimal decision. Document assumptions, validate with sensitivity analysis, and present to stakeholders for approval.
Real-World Example
Scenario: A project manager must decide whether to build a custom analytics platform or license an existing SaaS solution
• Build Custom: 60% probability of success, $200,000 outcome if successful, -$50,000 if it fails
• License SaaS: 85% probability of success, $120,000 outcome if successful, -$20,000 if integration fails
• Build Custom EMV: (0.60 x $200,000) + (0.40 x -$50,000) = $100,000
• License SaaS EMV: (0.85 x $120,000) + (0.15 x -$20,000) = $99,000
Result: Build Custom has a marginally higher EMV ($100,000 vs. $99,000), but the SaaS option has far less downside risk. A risk-averse organization would choose SaaS despite the $1,000 EMV difference.
Common Mistakes to Avoid
- Confusing decision nodes with chance nodes -- Decision nodes (squares) represent points where you make a choice; chance nodes (circles) represent points where probability determines the outcome. Mixing these up leads to fundamentally flawed trees.
- Probabilities not summing to 1.0 -- At every chance node, the probabilities of all branches must total exactly 1.0. Leaving probability gaps or double-counting outcomes invalidates your entire EMV calculation.
- Ignoring opportunity costs -- Each decision branch should include the opportunity cost of not choosing the alternative. Omitting this biases the tree toward options that appear cheaper but sacrifice hidden value.
- Using EMV alone for risk-averse decisions -- EMV assumes risk neutrality. In reality, most organizations are risk-averse for large losses. Always pair EMV analysis with a risk attitude assessment for high-stakes decisions.
PMP Exam Tips
Decision tree questions on the PMP exam almost always involve calculating EMV. You will typically see a scenario with two or three alternatives, each with stated probabilities and financial outcomes. Work through each branch methodically: multiply probability by outcome for each path, sum the EMVs at each chance node, and compare across decision alternatives. The highest EMV wins unless the question specifies risk aversion.
Watch for questions that combine decision trees with contingency reserves. Remember that the contingency reserve is based on the EMV of identified risks. If a risk has a 30% probability and a $100,000 impact, the contingency reserve allocation would be $30,000 (the EMV). This connection between decision tree analysis and reserve analysis is a favorite exam topic.
Finally, know that decision trees are a tool of the Perform Quantitative Risk Analysis process, not Qualitative Risk Analysis. Qualitative analysis uses probability-impact matrices and risk categorization, while quantitative analysis uses numeric techniques like decision trees, Monte Carlo simulation, and sensitivity analysis to calculate specific risk exposures.