Techniques to ascertain the distribution of possible financial outcomes of a capital project

Welcome to Project Evaluation!

Hi there! In the previous chapters, you learned how to calculate the Net Present Value (NPV) and Internal Rate of Return (IRR). These are great tools, but they usually rely on point estimates—basically, our "best guess" for things like future sales or interest rates. But as we know, the real world rarely follows our "best guess."

In this chapter, we are going to look at how we can stop pretending the future is certain and instead look at the distribution of possible outcomes. By the end of these notes, you will understand how businesses measure risk and what happens when things don't go exactly to plan. Don't worry if the math looks scary at first; we will break it down step-by-step!

Quick Review: Remember that a project is usually "good" if its NPV is positive. The techniques we are about to learn help us see how likely it is that the NPV will stay positive even if the world changes.

1. Sensitivity Analysis

Imagine you are baking a cake. You want to know: "If I accidentally add 10% more sugar, how much sweeter will it taste?" Or "If the oven is 10 degrees hotter, will it burn?" This is exactly what Sensitivity Analysis does for a project.

What is it?
Sensitivity analysis examines how much the NPV of a project changes when you change one single variable at a time, while keeping everything else the same (ceteris paribus). Common variables include sales volume, the discount rate, or the initial cost of equipment.

How to do it (The Sensitivity Margin):
A common way to measure sensitivity is to calculate the Sensitivity Margin. This is the percentage change in a variable required for the NPV to become zero.
The formula is:
\( \text{Sensitivity Margin} = \frac{\text{NPV of the project}}{\text{Present Value of the variable being tested}} \times 100 \)

The "So What?" Factor:
If a small change in a variable (say, a 2% drop in sales) makes the NPV turn negative, the project is highly sensitive to that variable. Management needs to watch that variable very closely!

Pros:
- It is very simple to understand and calculate.
- It identifies which variables are the "risk drivers."

Cons:
- It only changes one thing at a time. In reality, if sales drop, your costs might also drop. Sensitivity analysis ignores these connections.
- It doesn't tell you the probability of that change happening.

Key Takeaway: Sensitivity analysis is a "What if?" tool for single variables. The lower the sensitivity margin, the riskier the project is regarding that specific variable.

2. Scenario Analysis

While Sensitivity Analysis looks at one change, Scenario Analysis looks at a whole "world" of changes. It considers the impact on NPV when multiple variables change at the same time in a way that makes sense together.

The Three Common Scenarios:
1. Base Case: Our most likely set of assumptions.
2. Worst Case: High costs, low sales, high interest rates (everything goes wrong).
3. Best Case: Low costs, high sales, low interest rates (everything goes right).

Example:
If you are opening a coffee shop, a "Worst Case" scenario might involve a new competitor opening next door and the price of coffee beans rising simultaneously. Scenario analysis helps management see the range of possible NPVs.

Key Takeaway: Scenario analysis is more realistic than sensitivity analysis because it allows variables to change together. However, like sensitivity analysis, it doesn't usually tell us how likely those scenarios are to happen.

3. Probability Distributions and Expected Values

If we want to get really "actuarial," we start assigning probabilities to different outcomes. This allows us to calculate a single "average" outcome, known as the Expected Value (EV).

The Math:
The Expected NPV is the sum of each possible NPV multiplied by its probability:
\( E[NPV] = \sum (PV_i \times P_i) \)
Where \( PV_i \) is the outcome and \( P_i \) is the probability of that outcome.

Understanding Risk through the Distribution:
- Mean (Expected Value): The average outcome if we did the project many times.
- Standard Deviation: A measure of "spread." A high standard deviation means the project is very risky because the actual result could be very far from the average.
- Coefficient of Variation: This is \( \frac{\text{Standard Deviation}}{\text{Expected Value}} \). It helps compare the risk of two projects with different sizes.

Common Mistake to Avoid:
Don't assume the "Expected Value" is the most likely outcome. It's just a weighted average. If a project has a 50% chance of making \$100 and a 50% chance of making \$0, the EV is \$50, even though you will never actually make exactly \$50!

Key Takeaway: Probabilities turn "guesses" into "statistical distributions." This allows us to quantify the risk of the NPV falling below zero.

4. Monte Carlo Simulation

Sometimes a project is so complex that we can't calculate the distribution by hand. This is where Monte Carlo Simulation comes in. Think of this as "Virtual Reality" for finance.

The Process:
1. Use a computer to assign probability distributions to all risky variables (e.g., "Sales follow a Normal distribution").
2. The computer randomly picks a value for every variable and calculates the NPV.
3. The computer repeats this thousands of times.
4. The result is a beautiful graph (a frequency distribution) showing all possible NPVs and how likely they are.

Why use it?
It handles correlations between variables well (e.g., if inflation goes up, interest rates usually go up too). It gives a very detailed picture of risk.

The Downside:
It can be a "black box." If you put bad data in, you get bad data out ("Garbage In, Garbage Out"). It also requires specialized software and can be expensive to set up.

Key Takeaway: Simulation is the most powerful tool for seeing the full distribution of outcomes, but it requires computers and high-quality data.

5. Decision Trees

Some projects aren't just "start and wait." They involve sequential decisions. For example: "We will test the product today. If it succeeds, we build a factory next year. If it fails, we abandon it."

How they work:
- Squares represent decision nodes (points where management chooses a path).
- Circles represent chance nodes (points where the outcome is out of our control).
- You work backwards from the future to the present to find the best current decision.

Key Takeaway: Decision trees are great for projects with different "stages" and for showing the value of flexibility (the option to change your mind later).

Summary Checklist

Can you explain the difference?
- Sensitivity: Change one variable at a time.
- Scenario: Change a group of variables to fit a "story."
- Expected Value: The probability-weighted average.
- Simulation: Thousands of computer-generated "what-ifs."
- Decision Trees: Planning for multi-stage decisions.

Did you know?
The name "Monte Carlo Simulation" comes from the famous Monte Carlo Casino in Monaco. Because the technique relies on randomness and chance (like rolling dice), it was named after the world's most famous gambling destination during the development of the atomic bomb!

Don't worry if these concepts feel abstract! In the exam, you'll often be asked to perform a simple calculation for one of these or discuss the advantages and disadvantages of each. Practice with past paper questions to get comfortable with the wording!