The Tornado Diagram Is One Chart Every Management Team Should See
- JD Solomon
- 45 minutes ago
- 5 min read
Budgeting decisions have a regular rhythm. So do long-term capital planning efforts, at least for those organizations that do them. The normal picture is a staff member walking into the boardroom with a list of capital needs, some type of priority list, and a stack of printed spreadsheets. The board or council usually listens politely and asks an occasional question about the biggest line items. However, the question that everyone wants to understand is: what are the key variables that are driving the budget decision and which assumptions about those variables have the most variability?
A tornado diagram answers it in one picture, if you can get it in front of the room.
The Time I Didn’t Get to Show a Tornado Diagram
I landed in Tennessee around 11 am. Our project manager, Jerry, picked me up. The game plan was to meet our regional manager, Ron, for lunch and then go directly to the client’s office. There we would work with their senior management team to evaluate and prioritize a new compliance-driven capital program.
Jerry waited until we got to Chili’s with Ron to spring his concern on me. “JD, I am having a major problem with that one slide. I don’t understand it. And it's kept me awake most of the night.”
We were on the same team, so I tried to make light of it by saying, “Jerry, there’s no reason to lose sleep over a slide. Let’s talk about it.”
“You know I am an engineer,” he said stoically. “And while I appreciate you sending me the slides a week ago, I didn’t look at them until this past weekend. I just need to understand everything before I let you present something to my client.”
“You’re kidding me,” I thought as I glanced toward Ron. But his eyes told me this wasn’t going away.
As a subject matter expert who was used to dropping in out of the air to solve problems, I knew three things about this situation. First, the reason I was there was because I was an expert (not the project manager), but many project managers trained as engineers never take off their engineering hat. Second, I knew I had to go into supportive mode just as I would with the client. And third, it was Jerry’s client, so it was his call.
So I pulled out my laptop, opened Excel, and shifted my seat to be beside Jerry. I had to try but I knew I was doomed to fail.
After about ten minutes, Jerry said what we all knew he would say, “I just can’t understand this until I can actually focus on the details. Let’s pull this slide.”
“I am good with that,” I stated. “I have another way to cover this. But have you already sent the slides to the client?”
“No, just the agenda and the meeting objective. I don’t like to send the meat of the presentation in advance,” he stated.
“Oh, shit,” I thought. “We have bigger problems than a tornado diagram.”
Sensitivity analysis was just a small part of the meeting, and overall the meeting went ok. The reason I remember this story so well is that I was back in front of them two months later. This time I was explaining a tornado diagram. The executive management team understood it almost immediately; I am not sure that engineer Jerry ever did.
What a Tornado Diagram Actually Shows
A tornado diagram is a modified bar chart built to communicate the results of a sensitivity analysis, run either deterministically or probabilistically. It gets its name from its shape: the input variables with the most influence on the output sit at the top with the widest bars, and the inputs with the least influence taper down toward the bottom. That narrowing of the bars makes it like the funnel of a storm.
It’s a good fit for decisions related to understanding which variables have the most influence on the solution, prioritizing rehabilitation projects, sizing a reserve fund, ranking which assets get the next round of capital, and establishing multi-year budgets. The shape of the diagram does something a table of numbers can’t. At a glance, the tornado diagram shows which variables are actually worth arguing about and which ones are noise.
…the tornado diagram shows which variables are actually worth arguing about and which ones are noise.
The Explanation Sequence That Works in the Boardroom
Decision makers do not need a statistics lecture. They need a sequence, delivered once, in this order:
The input variables are listed down the left side of the diagram.
The vertical line running through the center of the bars represents the central tendency — usually the median result.
Each bar shows the range of variation in that central result caused by uncertainty in that one input.
Therefore, the inputs at the top of the diagram matter far more to the decision than the inputs at the bottom.
This four-point sequence works almost every time. You can then turn the presentation into an interactive conversation, if the management team or decision makers choose to.
The tornado diagram becomes a standing reference for the rest of the project or program. And once you use it, the management team will request it for their next big decision.
A Built-In Bonus: It’s Also a Quality Check
Here’s a detail that rarely makes it into the slide deck but is worth knowing before you sign off on the analysis: a tornado diagram doubles as its own quality-assurance check.
A tornado diagram doubles as its own quality-assurance check.
Every bar in a tornado diagram should touch the vertical centerline (baseline). If one doesn’t, that input’s variation isn’t actually reaching the output. There is a flaw in the underlying model that the modeler has not detected.
My team and I have caught real errors this way in analyses handed over by other consultants, simply by checking whether every bar crossed the centerline before it ever reached a decision maker.
The tornado diagram earns its keep twice: once as a communication tool for the room, and once as a review tool for whoever is responsible for standing behind the numbers.
Presenting It Well
A few habits that are worth building in.
Lead with the picture, not the labels
The input list along the left edge doesn’t need to be legible the first time the diagram goes up; only the shape does. Legibility matters later, when you drill into a specific input.
Keep the color palette disciplined
Shades of black and blue for the bulk of the bars, sharper colors like green and red reserved for the one or two points you actually want remembered.
Trust the executives
Technical staff often want to dive into the math faster than the audience is ready for; decision makers usually get to “the top matters more than the bottom” before their own advisors expect them to. After all, most executives want to know what time it is and not how the clock is made.
Why Tornado Diagrams Belong in Your Toolkit
Capital planning, risk-informed decision making, and budget prioritization all run on the same underlying question: which assumptions are worth management time, and which ones aren’t? It really gets to the central ideas of sensitivity, criticality, and priorities. A tornado diagram answers those ideas in one visual. It tends to become a visual that's requested again and again once it’s on the table.
This piece draws on material from JD Solomon’s book Communicating Reliability, Risk, and Resiliency to Decision Makers, along with tornado-diagram guidance previously published on Communicating with FINESSE.
Need help getting started? JD Solomon Inc provides solutions for program development, asset management, and facilitation at the nexus of facilities, infrastructure, and the environment.
Comments