Your goal: explain a delay to a non-technical executive in plain words: what happened, how
worried she should be, what you recommend and what you need from her.
Your briefing (made up for the exercise)
- Halcyon Health, a hospital group, is rolling out a sync that gives door access and the monthly
headcount report one clean record per employee, from two systems.
- Launch was set for next Monday at all five hospitals. In the pilot at one hospital, about sixty
people were matched to the wrong old record: mostly staff who left and were rehired. A few would
have been refused entry. Nothing was written to payroll, pay is unaffected.
- You caught it in the pilot, before launch. Cause: the matching rule trusts the old record too
much when someone is rehired.
- Fix: change the rule, then hospital HR reviews about three hundred uncertain records at the
pilot hospital. About a week for three hospitals whose data is cleaner; about three weeks for all
five.
- Also: last month the payroll export changed its format without notice once and a nightly run failed.
- You do not yet know how many records are uncertain at the two other hospitals.
How this works (about 20 minutes)
- Hannah plays the COO, not an interviewer. She is sharp, busy, and not hostile.
- Around fifteen minutes in she steps out of role and gives a short debrief.
- No notepad and no hints. Your report comes after.
What scores well
- A first answer in plain words in under a minute, with a number or a date
- A clear recommendation and why, not a list of options
- Honesty: what you know, what you don't, and when you will
- Naming the decision she needs to make and by when
- Staying calm when she asks "should I be worried?" or "just launch and fix it"
Tips
- Take FDE Drill · Explain It to an Exec to warm up.
- Start with the answer to her question, then the reason.