How to Present Simulation Results to the Board
Present simulation results to the board as one page that leads to one decision. Start with the decision you are asking for, show the two to four options you compared and how each performed on the same scenarios, translate the model outputs into money, delivery and risk, name the assumptions that matter and who owns them, and state what would make you reopen the decision. Keep charts, runs and model details in the appendix. If the board cannot decide from the page alone, the page is not ready.
Why simulation results stall in the boardroom
Simulation work often ends as technical charts: utilization by station, queue lengths, flow times, a 3D animation of the new hall. Useful to engineers, they create two problems in the boardroom.
First, the board cannot see what is being decided. A chart of buffer levels does not say "approve option B for this amount by this date". Second, the meeting turns into a model tour. Someone asks why a forklift moves a certain way, the next twenty minutes go to details, and the decision moves to the next meeting.
The board then decides on habit, on trust in the sponsor, or not at all. What helps is a clearer link between the model and the decision.
Start with one decision sentence
Before you build any slide, write one sentence that states the decision. It should include what is approved, how much money is committed and when it takes effect.
For example: "Approve the relayout of hall 2 with a central buffer, at the budget in the business case, with installation in the August shutdown."
Everything else on the page supports or challenges that sentence. If you cannot write it, the work is not ready for the board. It may still need a comparison of options, covered in How to Compare CAPEX Options When Every Scenario Looks Plausible, or a business case, covered in How to Build a Digital Twin Business Case.
What goes on the one page
A board page built from simulation has six parts. Each fits in a few lines.
- The decision sentence: what, how much, when.
- The options compared: two to four named options, including "defer", and one line on why weak options were dropped earlier.
- The scenarios used: the base case and the stress cases every option went through, such as a demand drop, a slower bottleneck station or a late supplier.
- The ranking and trade-offs: which option is recommended, what it gives and what it costs, in business terms.
- The main assumptions: the three to five inputs the result depends on, each with an owner.
- The reopen trigger and review date: what event would make you rerun the model, and when you will check the result against reality.
Put the downside cases on the page next to the base case. A board that sees only the base case will assume it is the plan. What a Sensitivity Analysis Should Show Before Approval shows how to present which inputs the result depends on.
Translate model outputs into board language
Engineers speak in queues and utilization. Boards decide on money, delivery and risk. Someone has to translate before the meeting.
| Model output | What it means for the board |
|---|---|
| Queue time in front of the bottleneck | Risk of late deliveries and overtime |
| Work in progress on the floor | Working capital tied up and floor space used |
| Bottleneck moves to another station | Where the next problem and the next investment will be |
| Weeks until stable output after installation | When the benefit starts to show in the numbers |
| Output when a key station runs slower in a variant | How exposed the plant is to one weak station |
| Forklift and cart utilization | Whether more transport equipment or drivers will be needed |
Use this language in the ranking. "Option B gives slightly less output in a normal week, ties up less inventory and loses less when the paint line runs slower" is a sentence a CFO can act on. "Option B has lower mean utilization at station 4" is not.
See results a board can read
Once the comparison is translated into delivery risk and working capital, the board page gets much shorter. The demo shows that translation on DBR77 Digital Twin results, and when a 3D or VR view is worth showing in the meeting.
Run a 30-minute review that ends with a decision
A board slot is short. Use a fixed agenda so the time goes to the decision.
- Minutes 0 to 5: the decision sentence, the options and the recommended ranking. Agree on what is being decided.
- Minutes 5 to 15: downside cases and the inputs that could change the ranking. List the risks to accept or to remove.
- Minutes 15 to 25: the decision itself (approve, approve in stages, pause or reject) with the reason.
- Minutes 25 to 30: owners, dates and the next review point, written into the minutes.
Send the page and the appendix ahead of the meeting, so questions about details arrive in writing before the meeting.
What to keep in the appendix, and what to refuse in the room
The appendix is where board members, or the people they delegate to, can check the work. It should contain the scenario list, the main results per option, the sensitivity runs, the model boundary (what the model includes and what it leaves out) and the source of the main inputs.
In the room, politely turn down four things:
- live edits to the model (note the question and answer it in writing)
- new options that did not go through the same scenarios, which can enter the next round
- debates about how the 3D looks, since visual quality does not change the decision
- deep dives without a question to answer, which belong in a follow-up
Visuals still have a place when they shorten the decision. In a plant expansion project for a car lamp manufacturer, management reviewed the final design in VR, which helped them choose the sequence of transferred processes faster. The VR review answered a clear question, and that is a fair test for any visual you bring.
The test before you send the page
Give the page to someone who was not involved in the project. Ask them to explain the decision, the main risk and why the losing options lost. If they can, the page is ready. If they need the model, a chart or the engineer to explain it, tighten the page first.
Two more checks help. Finance should see how cash timing differs between the options. Operations should recognize the shift and flow assumptions behind the result. If either group cannot, they will raise it in the room, and the decision will slip.
FAQ
How long should a simulation summary for the board be?
One page for the decision, plus an appendix. If the main argument needs more than a page, the decision is probably not yet clear enough.
Should we show the 3D model or animation to the board?
Only if it answers a question the board has, for example the order of machine moves during a relocation. A short VR or 3D review can speed up such choices. A general model tour usually slows the meeting down.
How do we show uncertainty without confusing the board?
Show the recommended option in the base case and in two or three downside variants with different fixed assumptions, side by side. Then name the one or two inputs that would change the ranking and who checks them.
What if the board asks for an option we did not simulate?
Note it and promise a written answer after it has gone through the same scenarios as the others. Deciding on an untested option in the room removes the reason for running the model.
Conclusion
Write the decision sentence first, before any slide exists. Then hand the draft page to a colleague outside the project. If they can explain the decision, the main risk and why the other options lost, send it with the appendix ahead of the board meeting.
Preparing an investment decision for the board?
If the board meeting is a few weeks away, send us the decision sentence and the options on the table. We can help you pick the scenarios that belong on the page.
Sources
Want to test a decision from your plant?
Describe the decision to a DBR77 expert and we will show how DBR77 Digital Twin compares the options on output, waiting time and transport load.
Questions
Have a question about this topic?
Tell us what it is about. We will reply within one business day.
Digital Twin newsletter
Short notes on testing layout and flow decisions on a model, and news from DBR77 Digital Twin. You can unsubscribe at any time.