Situation and why it mattered
The recurring question was simple: “How are we doing?” Existing answers leaned on historical volume and revenue-cycle reports, but leaders needed a forward-looking operating signal early enough to influence the month rather than explain it afterward.
The real question
Could leaders see early enough whether booking pace, recent visits, and cancellations pointed toward a strong or weak month?
Role and team context
I worked from the COO’s broad question, reframed the decision need, designed three business-specific signals, and brought them together in a red, yellow, and green stoplight that was quick to scan.
Approach
The view compared booking speed with the recent median for the same day of week, recent visit history with budget, and month-to-date cancellations with recent history. Thresholds reflected the nature of each measure rather than forcing one rule across all three.
Result and what changed
Operating leaders gained an earlier combined view of visits, cancellations, and booking pace. The design shifted the conversation from describing the recent past to recognizing current signals while there was still time to respond.
Evidence boundary
No quantified decision or financial outcome is documented. This case demonstrates problem framing and decision-product design rather than a financial-impact claim.
What was learned
Executive reporting becomes more useful when the measure, threshold, and visual treatment are designed around the decision, not around the data already easiest to retrieve.