Spider Diagrams: Identifying Critical Variables

1. What is a Spider Diagram?

A spider diagram (also known as a sensitivity chart) is a graphical tool used to display the results of a sensitivity analysis. It plots the project's financial outcome—typically Net Present Value (NPV) or Present Worth (PW)—on the vertical axis against the percentage change of various input variables on the horizontal axis.

Each variable (like unit cost, demand, or initial investment) is represented by its own line. All the lines intersect at a single point, which represents the base case—the project's NPV when all variables are at their most likely, or forecast, values (i.e., at 0% deviation).

The main purpose of this diagram is to make the relative sensitivities of the variables immediately obvious. The key to interpreting it is simple:

The steeper the slope of a line, the more sensitive the project's outcome is to changes in that variable.

A steep line means that even a small change in that input variable will cause a large swing in the project's NPV, making it a critical factor to monitor. A flat line indicates that the NPV is not very responsive to changes in that variable.

2. Building and Interpreting the Diagram: A Worked Example

Let's walk through how to create and read a spider diagram using a concrete example. The process directly builds on the one-variable-at-a-time analysis we performed in the last lesson.

As you can see from the resource, the process is:

1. Calculate the base case NPV. This is the central point of your diagram.
2. For each variable, calculate the NPV at different percentage deviations (e.g., -20%, -10%, +10%, +20%) while keeping all other variables at their base case values. This generates the data points for each line.
3. Plot these points on a graph to create the spider diagram.

Reading the Results

Now, let's interpret the 1-year spider diagram from the resource:

• Most Sensitive Variable: The line for Unit Price is by far the steepest. This tells us that the project's success is extremely dependent on the final selling price. A small deviation from the forecast price will have a massive impact on the NPV.
• Least Sensitive Variable: The line for Operating Cost is the flattest. This means that even a significant percentage change in operating costs will have a relatively small effect on the overall profitability.
• Direction of Impact:
  • Lines with a positive slope (like Unit Price and Demand) show that as the variable increases, the NPV increases. This makes sense—selling more units or selling them at a higher price improves profit.
  • Lines with a negative slope (like Unit Cost and Labour Cost) show that as the variable increases, the NPV decreases. This is also intuitive—higher costs reduce profit.

From a management perspective, this diagram sends a clear message: "We must be very confident in our pricing strategy. Let's invest more time in market research to validate the unit price. We can be less concerned about minor fluctuations in our operating cost estimates."

Alternative View: The Tornado Diagram

The resource also introduces the Tornado Diagram. It presents the exact same information but in a different format. Instead of sloped lines, it uses horizontal bars representing the range of NPV outcomes for each variable. The bars are sorted by length, with the longest (most sensitive) at the top.

This is the 5-year Tornado Diagram from the resource. It clearly shows that 'Unit Price' has the widest range of NPV outcomes and is therefore the most sensitive variable, followed by 'Unit Cost' and 'Demand'.

Both diagrams lead to the same conclusion, but some people find the "tornado" shape more immediately impactful for ranking variables by risk.

3. Strategic Implications

Identifying the most critical variables is not an academic exercise. It directly informs your project strategy and risk management plan.

Once your spider diagram has flagged the high-sensitivity variables, you can take targeted action. For a software project, this might involve:

• If 'Demand' or 'User Adoption Rate' is the most sensitive: You should prioritize investing in market analysis, user surveys, and possibly developing a Minimum Viable Product (MVP) to test the market's appetite before committing to full-scale development.
• If 'Development Time' is the most sensitive: You might focus on using a more agile development process, hiring additional developers to reduce the timeline, or using more robust project management tools to mitigate delays.
• If a third-party 'API Cost' is the most sensitive: You would dedicate significant effort to negotiating a favorable, long-term contract with the provider or architecting your system to make it easier to switch to an alternative provider if costs escalate.

The diagram tells you where to spend your most valuable resources: time and money, to reduce uncertainty and mitigate risk.

Conclusion

You've now learned how to bridge the gap between raw data and actionable insight. A spider diagram is an essential communication tool that translates the results of a sensitivity analysis into a clear visual format, making it easy for both technical and non-technical stakeholders to understand a project's risk profile.

• Key Takeaways:
  • Spider diagrams visually represent the impact of changes in input variables on a project's financial outcome (like PW or NPV).
  • The core principle is that the steepness of a variable's line is proportional to its sensitivity. Steeper means more critical.
  • The slope's direction indicates a positive or negative relationship with the project's value.
  • Interpreting a spider diagram allows you to identify the most significant risks and strategically allocate resources to manage them.

Preview of the Next Lesson

Sensitivity analysis and spider diagrams are powerful, but they have a limitation: they only change one variable at a time. In the real world, variables often move together. For example, a market downturn could simultaneously lower customer demand and put downward pressure on the price you can charge.

In our next lesson, we will explore scenario analysis, a technique for evaluating a project under different, coherent future conditions (like an optimistic, pessimistic, or most likely scenario) where multiple variables change at once.