A Multi-Site Dashboard Should Explain the Gap Between Your Best and Worst Tuesday
Two sites achieve the same monthly revenue. One delivers a steady experience; the other alternates between excellent days and costly recoveries. The group dashboard colours both green.
Averages are useful for summary. They are poor substitutes for understanding variation. In an experience-led business, customers encounter a particular visit, not the group’s mean performance.
Start with a comparable operating moment
Choose a recurring customer moment that matters commercially: arrival, order fulfilment, treatment readiness or recovery. Define it consistently enough to compare locations without pretending they are identical.
A city restaurant and a destination restaurant may have different demand patterns. A hotel with groups cannot be compared mechanically with one dominated by individual travellers. Segment the comparison where those differences change the meaning of the measure.
Use a small number of measures tied to the promise. Waiting time without information, repeated customer explanations, incomplete handovers and unresolved problems may be more revealing than a broad satisfaction score.
Follow the pattern over time
A single poor day can have a specific cause. Persistent variability suggests a different management problem. Plot observations in time order so leaders can see whether performance is improving, deteriorating or fluctuating.
The NIST guidance on process stability explains the role of time-based plots and control charts in assessing variation. Formal statistical methods need suitable data and competent interpretation; a decorative chart with arbitrary limits does not provide that discipline.
For many leadership teams, the immediate improvement is simpler: preserve the sequence, show the sample size and annotate known operational changes. Do not erase a difficult day from the discussion simply because the month finished on target.
Investigate conditions before ranking managers
Differences may reflect staffing, equipment, customer mix or conflicting priorities. They may also reflect leadership capability. The dashboard should trigger investigation rather than deliver a verdict before those conditions are understood.
Visit a reliably strong site and observe what makes its results repeatable. Check whether it has an advantage that other sites lack. A practice worth sharing should be distinguishable from an unusually favourable context.
Do the same at a struggling site. Ask what staff must compensate for and what information they cannot obtain in time. A request to work harder is unhelpful if the underlying problem is an unavailable resource or a contradictory target.
Make the review produce an operating decision
Each significant pattern should lead to a test, a resource decision or a justified decision to observe further. Assign an owner and specify the customer outcome expected to change.
Avoid turning every fluctuation into a new initiative. Overreaction can make an operation less stable. Equally, a familiar problem should not remain on the dashboard indefinitely without a decision.
Q Branch’s operational excellence work connects management visibility to the experience customers receive. A useful dashboard should help leadership understand why an ordinary Tuesday differs across the estate, and what can be done to narrow the avoidable gap.
Representative photograph: Unsplash.






Comments