Overview
What this was
This case shows the judgment required to separate a training problem from a business-system problem and say so to leadership.
- Interviewed nine director-level stakeholders across the opening functions
- Tested their explanations against historical opening data
- Built the Opening Readiness Risk Panel in SQL and Power BI
- Facilitated functional owners through defining indicators, thresholds, and ownership
The system
Diagnosis, build, and how it ran
The request and the diagnosis question
Leadership initially asked for
More training
More trainers onsite
More post-opening trainer support
The question I asked
What is actually causing opening risk?
Which function controls that risk?
Which risks are visible early enough to act on before launch?
A readiness problem is assigned to the function that controls the risk. Training is one input among several and is used where it matches the risk.
Site, infrastructure, and business readiness had been collapsed into one conversation, which made every failure sound like a people problem. Separating the domains showed that several risks belonged to construction, IT, or business readiness.
Diagnose
Three risk domains, seven leading indicators
Select a domain to see what is measured and who owns it.
Are physical milestones complete enough for technology deployment and training to happen without rework?
- Construction milestone variance
- Active construction overlapping deployment
- Site handoff and access readiness
Primary owner: Construction (overlap shared with IT)
Each indicator carries a threshold and a named owner. Two of the seven route to training; five route to other owners.
From lagging to leading
After-the-fact model
Opening underperforms
Teams reconstruct what happened
Training becomes the convenient explanation
Leading-indicator model
A risk threshold changes
The owner becomes visible
A decision is required, with a date
The intervention happens before launch
“Who caused this opening to fail?” became “What risk is visible now, who owns it, and what intervention will change the outcome before launch?”
How it reads in practice
In the sample panel, six openings are in view: two on track, three at risk, one critical. The top driver is site, affecting three of the six. The panel goes past status. It names the two decisions required this week and who has to make them.
Post-opening escalations during the first three operating days are recorded as validation. They appear after launch, so pre-launch decisions rely on the leading indicators available earlier.
The sample panel uses fictional openings and data to show the risk model, ownership, and executive decision view.
I am willing to tell leadership when the evidence points to a construction, IT, or business-readiness intervention.
What changed
- One shared definition of readiness across functions, argued into shape by the owners themselves
- Risk raised before launch with an owner attached
- Training applied only where the data showed a genuine readiness gap
The reported outcome is the shared definition of readiness and the more proactive process.
Measurement
What changed
9
Director-level stakeholders interviewed across functions
3
Risk domains separated: site, infrastructure, business
6 of 7
Indicators available before launch
Evidence
Artifacts for this case
Supplied samples are public-safe and sanitized.
Opening Readiness Risk Panel (fictional data)
The executive risk view, leading indicators by launch, threshold logic, and the owner assigned to each risk.
Format: PDF · fictional openings and data
Illustrative dataView risk panel