A New Quality Director Inherits a 47-Page Board Packet and a 15% Budget Cut
You are the newly hired system director of quality for a two-hospital system: a 310-bed flagship with a level III NICU and a 90-bed critical access hospital 40 miles away. Your predecessor resigned after a survey produced a 12-month monitoring plan, and the department has had no permanent leader for seven months. The board quality committee meets quarterly and receives a 47-page data packet 48 hours in advance; minutes show the same three questions going unanswered for four consecutive quarters. The CEO wants "one dashboard covering everything" built within 60 days for the next board meeting. The flagship's medical executive committee has twice voted down a revised hand hygiene policy, calling it "cookbook medicine." The system is absorbing a 15% reduction in the quality budget: you have 9.2 FTEs for roughly 400 licensed beds, two certified abstractors retiring within six months, and physician champion stipends were eliminated in the same cut. The critical access hospital's only quality coordinator is part-time and also runs infection prevention.
1. How would you structure quality governance and board reporting in your first 90 days, and what would you do with the 47-page packet and the CEO's 60-day "everything" dashboard? Justify your trade-offs.
Read the worked answer
Diagnose before designing. Interview committee members and pull the minutes to learn what the three unanswered questions actually are - they usually signal that the packet reports data without asking for a decision.
Governance layers: a board quality committee with a written charter (four to six strategic priorities, escalation criteria, minutes that record decisions and owners); a system quality council chaired jointly by the CMO or CNO and quality, meeting monthly; unit-level huddles feeding it.
Dashboard: say yes to the 60 days but negotiate scope - one page, 12–15 measures across safety, effectiveness, patient experience, throughput and regulatory readiness, each with a named owner, an explicit definition, a target, direction of goodness, a statistical process control trend, and one line on what is being done. Drill-down lives in an appendix. A v1 built from already-validated measures with data-quality gaps labeled is achievable; a v1 that invents new measures is not, and a dashboard nobody trusts is worse than none.
The packet: invert the order. Three pages of narrative and decisions requested, then exception reports only for measures off target, then full data in an appendix. Pre-brief the committee chair five days ahead. The trade-off is breadth versus usability: a narrow, trusted set that grows beats an exhaustive set that gets skimmed.
2. How do you handle the medical executive committee's second rejection of the hand hygiene policy, and how do you build physician accountability when you have no authority over physicians?
Read the worked answer
Treat the rejection as information. "Cookbook medicine" usually means clinicians were not involved in writing the standard, the measure feels punitive, or the policy conflicts with something real - glove use in place of hand hygiene, skin irritation from the product, dispensers in the wrong places. Ask the MEC leadership directly what specifically they object to and get it on the record.
Then co-design: a physician champion who is credible with peers, a one-page evidence brief focused on healthcare-associated infection harm in your own units, and a policy limited to what matters - indications, product, observation method, and explicit exceptions. Separate the standard from the measurement so clinicians are not arguing about observers while the standard is being set.
Accountability runs through existing medical staff structure, not around it: the MEC owns the standard, department chairs review unit-level results, and outliers get a peer conversation rather than a public ranking. Offer a 90-day test on two units with physician-led review of the data before system-wide rollout - that converts an ideological vote into an empirical one.
Escalation matters. If the MEC will not act, the route is the joint conference committee and the board quality committee asking the CEO and CMO for progress, not a policy slipped past the MEC. Repeated failure of a medical staff body to act on a known safety risk is itself a governance finding.
3. Where do you take the 15% out of a 9.2-FTE quality department, and what do you protect?
Read the worked answer
Protect three things and say why in writing: abstraction and validation for mandated and payment-linked measures; safety event reporting and root cause analysis capability; and survey readiness. Losing any of these converts a budget saving into regulatory and payment exposure.
Consolidate and cut the rest: duplicate dashboards and report production across the two hospitals, retrospective review that duplicates what the EHR already captures, and contracted survey preparation that duplicates internal work.
Address the retirement risk now, not in month five. The two abstractors hold undocumented abstraction rules; get those written down, cross-train a replacement, and arrange a contracted surge backup. Cross-train the critical access coordinator so infection prevention and quality each have a named backup - a single part-time person running both is a single point of failure.
On stipends, do not spend the cut restoring cash. Replace stipends with CME credit, recognition at medical staff meetings, and department-chair protected time; a small stipend was evidently not motivating enough to survive a budget review. Present the whole thing as a portfolio decision with risk attached to each line, not a flat percentage - a flat cut invites the wrong cuts. Quantify FTE per licensed bed and FTE per reported measure so the board sees the constraint.