Skip to content

Use-Trace Heatmap

Visualization artifact — instantiates Revealed-Use Path Alignment

Aggregates many individual traces into a single visual field so the places where actual behavior concentrates — and diverges from the intended path — jump out at a glance.

One person cutting a corner is an anecdote; ten thousand cutting the same corner is a signal you can see. Use-Trace Heatmap pools many individual traces — footfalls, clicks, queue positions, dwell times — into one intensity map laid over the intended path, so the reader can see where behavior actually concentrates and how far it has drifted from the route the design expected. Its defining move is aggregation-into-legibility: it turns a mass of separate observations into a pre-attentive picture that a stakeholder grasps in a second. Crucially, it shows the where and the how much, not the why — it is an attention-director, not an interpreter or a judge.

Example

A museum wants to know why its blockbuster gallery feels congested while a prized side room stays empty. Anonymized foot-traffic counts, gathered over a season, are rendered as a heat overlay on the curator's intended serpentine route. A bright diagonal band lights up where visitors cut straight across the hall toward the exit, ignoring the designed switchback; the side room holding a celebrated canvas barely registers as a faint smudge. The heatmap doesn't say why people skip the canvas — poor signage, an awkward doorway, sheer fatigue are all still open — but it converts a vague staff impression ("people seem to rush the end") into a specific, sited claim: the intended path is being short-circuited here, and this artwork is being missed there. That picture is what tells the team where to point the next, interpretive step.

How it works

What sets the heatmap apart from the other capture tools is that it aggregates and registers, and stops there:

  • Pooling. Thousands of individual traces are summed into intensity, so a pattern too diffuse to notice one-at-a-time becomes a shape.
  • Registration. The intensity field is laid over the intended path, so divergence — not just activity — is what the eye reads.
  • Magnitude, not motive. It reports concentration and location at a glance and deliberately leaves cause to a downstream tool.

It is meant to be read in a second and to raise the right question, not to answer it.

Tuning parameters

  • Grid resolution — fine cells expose small detours; coarse cells show gross flows. Too fine reads as noise, too coarse hides the interesting deviation.
  • Aggregation window — how long a span is pooled. A long window gives a stable, trustworthy pattern but masks a recent shift; a short one is current but jittery.
  • Normalization — raw counts versus counts normalized by exposure or footfall. Raw counts over-weight already-busy areas and can invent a "hotspot" that is just where everyone already is.
  • Overlay baseline — which intended path the trace is registered against. Pick the wrong reference route and ordinary behavior looks like deviance.
  • Colour scale break — where the palette's thresholds fall. A mis-set scale can manufacture a hotspot or wash a real one out.

When it helps, and when it misleads

Its strength is compression: it turns an unreadable pile of individual traces into an at-a-glance map that aligns a whole room on where the lived path and the official path have parted, cheaply and before anyone has argued about causes. It is the fastest way to make a divergence undeniable.

Its central blind spot is that a heatmap can only light up people who are present — the deterred, excluded, and absent leave no mark, so the map silently omits exactly the users a redesign might most need to serve.[1] Because it carries no "why," it also invites the reader to project a convenient cause onto a hot band. And its most common misuse is running it backwards: tuning the window and colour scale until the picture "proves" a redesign already chosen. The discipline is to treat the heatmap as a question-raiser — hand its hotspots to interpretation and to an explicit check for who is missing before acting on them.

How it implements the components

Use-Trace Heatmap realizes the capture-and-comparison side of the archetype's machinery — the parts a visualization can fill:

  • use_trace_capture — it is captured trace, rendered as an aggregate intensity field rather than a list of events.
  • intended_actual_path_comparison — registering the trace over the intended route so divergence is what the eye reads is the artifact's entire purpose.

It does not interpret why the concentration exists — candidate causes are catalogued in Workaround Inventory and recovered in Frontline Go-Along Interview — nor assess or decide, which belong to Safety and Accessibility Review and Route Closure with Alternative.

Notes

A heatmap is descriptive, not evaluative — a single map is a snapshot. Sequencing two of them (before and after a change) is raw material for Before/After Trace Monitoring and Trace Decay Review, but the pairing, not the picture, is what carries a verdict.

References

[1] Survivorship bias — reasoning only from the cases that are visible while the ones that never appear are silently dropped, as in Abraham Wald's wartime analysis of returning aircraft. A use-trace heatmap shows the behavior of those who showed up; the people a design already turned away leave no trace to shade. ↩