S17 · company simulation

Delay notifications through the whole company

People, data and outputs in this scenario are simulated. Each stage is recorded when you commit; the reveal comes after.

4stages
40 minabout
0stages committed

The brief

The synthetic airline wants to notify passengers by SMS when a flight is likely to be delayed by an hour or more. A model gives each departing flight a delay probability. All people, opinions, prices and rates are simulated or hypothetical.

Volumes (simulated): 1,000 departures a day, 12% of them delayed by an hour or more (120 flights), 150 passengers per flight. Economics (hypothetical): an SMS costs 0.05 EUR per passenger (7.50 EUR a flight). A timely notice to the passengers of a truly delayed flight avoids 20% of them contacting the call centre at 4.00 EUR a contact (120.00 EUR a flight). A needless notice triggers contacts from 3% of passengers (18.00 EUR a flight).

Colleagues: a product manager who wants "every likely delay notified"; an airport operations lead; a legal and communications reviewer; a security lead; a finance partner; the commercial director.

Stage 1 of 4

Each colleague sends you a request before they will agree to launch. You must decide which requests are proper gates.

Which requests are appropriate launch gates? Select all that apply.

Operations asks for precision and recall of the notification rule on recent weeks, by airport, not only overall.Legal and communications asks for the notice wording to be reviewed, with no statement of cause and no promise of compensation.The product manager asks to see the model's AUC and to launch on any value above 0.80, since that is the usual bar.Security asks how the sender identity is protected so that fake delay notices cannot be mistaken for the real ones.The commercial director asks the data science team to confirm in writing that false alarms will never occur in production.