Pretend you are the hospice ops lead and force the outpatient hospice package to survive questions about who can freeze a census cap, how IDG meeting rewrites are timed across teams, and which override classes still lack a named owner when the live sample disagrees with the slide.
This seat sits between hospice tools and the bereavement narrative leadership will quote. It asks which census trees invent completeness the page export never measured, which IDG windows look crisp on a slide and soft in the live sample, and what happens when a rehospitalization ladder lands because ownership is incomplete. A green hospice board does not answer those questions. The review needs the census map, IDG calendar, override packet, and the named person who can freeze a hospice path.
Bring exhibits, not slogans
Hand over the hospice tools in use, census cap review draft, IDG meeting rewrite plan, override packet, last payer-visible rehospitalization gaps, and one recent case where a delayed freeze hurt a hospice narrative. Include which hospice promises still bypass the same review. State the decision: clear the hospice change, revise specific controls, or hold until a census owner is named.
Boundaries matter. The hospice ops lead can challenge untested census caps, IDG windows that ignore measured lead time, exceptions without a kill switch, and override paths without logging. Clinical outcome ownership stays with treating clinicians. Spend ceilings belong in the same packet so a quiet dashboard does not hide a brittle hospice path.
Authority questions worth answering in writing
- Which critical census class still lacks a tested freeze path with a measured age-out, and who owns the gap?
- What must hold before an IDG meeting rewrite can promote into a lasting policy, and who can waive it without a written reason?
- How does a declined census exception become visible to the requester within the claimed window?
- What is the measured time from a failed bereavement finding to a human with freeze authority?
- Which shared override can ship many hospice changes without failing a single rehospitalization health check?
- Who has authority to pause exceptions or force a hospice 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 hospice authority, force one named decision before the next tool change starts.
Leave a hospice ledger
Run the role in Pingpong with the same exhibits the hospice team will use. Have the home team answer each objection in writing. The useful output is a short hospice ledger: approved census classes, blocked classes, freeze windows, and the person who can call a freeze.
For adjacent hospice work, pair this seat with a census cap review, an IDG meeting rewrite, a bereavement caseload spike stress test, and a rehospitalization ladder. The war-game decisions hub has more seats. Before approving the package, make the hospice ops lead write the exact freeze and census check that will decide whether the change continues.