Pretend you are the ED ops lead and force the emergency package to survive questions about who can freeze a boarding crisis path, how left-without-being-seen ladders are timed across pods, and which ESI classes still lack a named owner when the live sample disagrees with the slide.
This seat sits between ED tools and the throughput narrative leadership will quote. It asks which boarding trees invent completeness the page export never measured, which LWBS windows look crisp on a slide and soft in the live sample, and what happens when an ESI rewrite lands because ownership is incomplete. A green ED board does not answer those questions. The review needs the boarding map, LWBS calendar, ESI packet, and the named person who can freeze an ED path.
Brief the seat with exhibits
Hand over the ED tools in use, boarding draft, LWBS ladder, ESI packet, last payer-visible boarding gaps, and one recent case where a delayed bed assignment hurt an ED narrative. Include which ED promises still bypass the same review. State the decision: clear the ED change, revise specific controls, or hold until a boarding owner is named.
Boundaries matter. The ED ops lead can challenge untested boarding rules, LWBS windows that ignore measured lead time, exceptions without a kill switch, and override paths without logging. Clinical outcome ownership stays with attending physicians. Spend ceilings belong in the same packet so a quiet dashboard does not hide a brittle ED path.
Questions that force owners
- Which critical boarding class still lacks a tested hold path with a measured age-out, and who owns the gap?
- What must hold before a left-without-being-seen ladder can promote into a lasting policy, and who can waive it without a written reason?
- How does a declined ESI exception become visible to the requester within the claimed window?
- What is the measured time from a failed boarding finding to a human with freeze authority?
- Which shared override can ship many ED changes without failing a single throughput health check?
- Who has authority to pause exceptions or force an ED rollback at week end without waiting for the system owner?
Require observed, inferred, or unknown labels. Observed claims need a source. Unknowns become owners and due dates. When two teams claim the same ED authority, force one named decision before the next tool change starts.
Leave an ED ledger, not slogans
Run the role in Pingpong with the same exhibits the ED team will use. Have the home team answer each objection in writing. The useful output is a short ED ledger: approved boarding classes, blocked classes, LWBS windows, and the person who can call a freeze.
For adjacent ED work, pair this seat with a boarding crisis stress test, a left-without-being-seen ladder, an ESI triage rewrite, and the ICU ops lead seat. The war-game decisions hub has more seats. Before approving the package, make the ED ops lead write the exact freeze and boarding check that will decide whether the change continues.