Analytics · Dashboard reading
The darkest cell is
not the answer.
Heatmaps are excellent at compressing a week of activity into a pattern the eye can recognize. That strength invites a mistake: assuming the brightest or darkest block is automatically where the operation broke.
The reframe
Color shows concentration. Constraint requires a second measure.
A departure cell can be busy because demand was high and the team handled it well. A neighboring cell with fewer vehicles can be the true failure because staffing dropped, the garage route changed, or a queue carried over from the prior interval.
Read the heatmap as a question generator. It locates time and place. It does not supply cause.
Four passes
Turn color into an operating question
First: read the denominator
Volume
Counts
A cell showing cars or requests tells where work accumulated, but larger properties will naturally dominate.
Rate
Per labor hour
Normalizing by labor can reveal workload pressure that raw volume hides.
Experience
Wait percentile
A P90 heatmap asks where service became unreliable rather than where the most cars appeared.
Exceptions
Incident rate
Use an explicit denominator so a small shift with one issue does not look equivalent to a large shift with many.
Second: check the time boundary
A fifteen-minute cell is a reporting box, not a wall in the operation.
→The constraint can begin in one cell and become visible in the next. Inspect the lead-in and recovery, not only the colored peak.
Third: layer the operating context
People
Scheduled and present labor
A schedule says who was planned. Punches and assignment changes say what capacity was actually available.
Place
Stand and parking zone
A remote stack or elevator route can move the constraint away from the visible curb.
Cohort
Demand source
Event releases, checkouts, residents, and restaurant turns create different wave shapes.
State
Open work entering the cell
Carryover queue is inherited pressure. Attribute it without pretending the interval started empty.
Fourth: open the records underneath
The best heatmap lets the manager move from pattern to named sessions and incidents without exporting a new report.
Verify
Sample ordinary cells
A quiet-looking block can still contain one serious failure. Review both hot and normal areas.
Explain
Read the timeline
Requests, acknowledgments, retrievals, handoffs, and exceptions reveal the mechanism behind the color.
Act
Record one decision
Change a staffing start, pre-stage rule, or stand handoff, then mark the expected effect for later review.
The dashboard rule
Every color needs a route to the underlying work.
A heatmap should help a manager move from 'Thursday evenings are dark' to 'this queue begins after the banquet release while one runner is still covering the remote floor.' That second sentence can change an operation.
The takeaway: use heatmaps to find where to look, then use operating records to learn what constrained the shift.
