Presenting Flow Simulation Data to Theme Park Stakeholders and Investors
The Translation Problem
Flow simulation produces rich, detailed output: density maps, throughput curves, queue formation timelines, cascade analysis. For engineers and experience designers, this data is gold. For stakeholders — the executives, investors, and board members who approve budgets — it's incomprehensible.
The gap between simulation output and stakeholder understanding is where good projects die. A designer who can't explain why Room 3 needs to be 20% larger will get the budget cut. A designer who translates "Room 3's throughput bottleneck reduces daily capacity by 440 guests, costing $13,200 per day in lost revenue" will get the expansion approved before the presentation ends.
Know Your Audience
Different stakeholders care about different things:
Financial stakeholders (CFO, investors): Care about revenue, ROI, and payback period. Translate flow data into dollars.
Operational stakeholders (VP of Operations, park GM): Care about daily guest counts, staffing requirements, and maintenance access. Translate flow data into operational parameters.
Creative stakeholders (Chief Creative Officer, show designers): Care about experience quality, pacing, and narrative integrity. Translate flow data into experience metrics (density, dwell time, encounter quality).
Safety stakeholders (Risk management, legal): Care about maximum occupancy, emergency egress, and liability exposure. Translate flow data into safety margins.
The Revenue Frame
For financial stakeholders, every flow metric should have a dollar value attached.
Throughput → Revenue: "This design processes 1,800 guests per day. At $28 per ticket, that's $50,400 daily revenue. Widening Room 3 by 15% increases throughput to 2,200 guests per day — $61,600 daily. The additional revenue is $11,200 per day, or $4.1M per year."
Congestion → Lost Revenue: "The current design develops a bottleneck at Station 5 that reduces effective throughput by 18% during peak hours. Peak hours account for 40% of daily attendance. The lost throughput during peak hours costs approximately $3,600 per day in guests who can't be admitted."
Queue time → Guest satisfaction → Revenue: "Simulation shows average wait time of 45 minutes under current design. Industry research shows that wait times over 30 minutes reduce guest satisfaction scores by 15%, which correlates with a 10% reduction in repeat visits. For an attraction generating $15M annually, that's $1.5M in lost repeat-visit revenue."
Visualization Techniques
Heat maps. Color-coded floor plans showing guest density. Red = overcrowded. Green = comfortable. Instantly communicable — no explanation needed.
Present heat maps side by side: "Current design" (showing red zones) vs. "Proposed design" (showing green zones). Stakeholders immediately see the improvement.
Time-lapse animations. Animated simulations showing guest dots moving through the attraction over a compressed full operating day. Stakeholders can watch congestion build, see queues form, and observe the cascade effect in real time.
These are the most powerful presentation tools. A 60-second animation communicates more than 20 pages of data tables.
Throughput curves. Line charts showing guests per hour throughout the operating day. The curve's peak is daily capacity. Show the current design's curve against the target line:
Guests/hr
300 | Target ─────────────────
| ┌──────┐
250 | ┌─────┘ └──────┐
| │ Current Design └─────┐
200 |────┘ └────────
|
└─────────────────────────────────────── Time
9AM 10AM 11AM 12PM 1PM 2PM 3PM 4PM
The gap between the curve and the target line is the throughput deficit. The area of the gap is lost guest-hours. Multiply by ticket price for lost revenue.
Scenario comparisons. Present three scenarios side by side:
| Metric | Current Design | Option A (+15% Room 3) | Option B (+Bypass Lane) |
|---|---|---|---|
| Daily throughput | 1,800 | 2,200 | 2,050 |
| Peak wait time | 45 min | 22 min | 30 min |
| Construction cost | Baseline | +$350K | +$120K |
| Annual revenue gain | — | +$4.1M | +$2.6M |
| Payback period | — | 31 days | 17 days |
Stakeholders can immediately compare options and make informed decisions.
The Three-Number Summary
For executive presentations, distill simulation results into three numbers:
- Daily capacity: How many guests can the attraction serve per day under realistic conditions?
- Revenue ceiling: What's the maximum daily revenue based on that capacity?
- Experience quality score: A composite metric combining average wait time, average density during experience, and percentage of guests encountering unplanned queues.
These three numbers tell the complete story: capacity (can we serve enough guests?), revenue (does the business case work?), and quality (will guests have a good time?).
Handling Objections
"The simulation is just a model — reality will be different." Response: "Yes, all models are approximate. But our simulation's throughput predictions are typically within 10-15% of actual performance for attractions of this type. The alternative — building first and measuring second — risks a $2M correction if the model is wrong. The simulation costs $20K."
"We can fix flow problems with operations after we open." Response: "Operational fixes (additional staff, flow managers, queue management) cost $200K-500K annually in perpetuity. A design fix during construction is a one-time cost. Here's the comparison..."
"Can't we just make Room 3 smaller and save money?" Response: "Here's the simulation with the smaller Room 3. Daily throughput drops from 2,200 to 1,600. That's $4.9M in annual revenue lost to save $200K in construction. The smaller room pays for itself negatively — it costs more in lost revenue than it saves."
When to Present Simulation Data
Concept phase: Present high-level throughput projections to validate the business case. "Can this attraction meet its revenue targets?"
Schematic design phase: Present detailed flow analysis to guide room sizing, path widths, and interactive station placement. "These are the specific design changes needed."
Design development phase: Present scenario comparisons to guide final design decisions. "Here are three options with their cost and throughput trade-offs."
Pre-construction review: Present final simulation as validation. "The approved design meets all throughput, quality, and safety targets under realistic conditions."
Post-opening: Present actual performance vs. simulation predictions. "Here's how the real attraction performed compared to our model. Here are the areas where we can optimize operations."
Building Stakeholder Confidence
The best way to build stakeholder confidence in simulation is a track record. If you've simulated previous attractions and can show that actual performance matched predictions within 10-15%, stakeholders will trust the current simulation.
If you don't have a track record yet:
- Reference published case studies of flow simulation in theme parks (Disney Imagineering, Universal Creative, and others use pedestrian simulation extensively)
- Present the simulation methodology transparently — show the inputs, assumptions, and sensitivity analysis
- Offer conservative projections (use the "expected case," not the "best case")
Want simulation data that speaks your stakeholders' language? Join the FlowSim waitlist and generate throughput projections, revenue impact analysis, and visual flow reports for your next attraction pitch.