A product lead brought a heatmap to critique week as if it were a verdict. The shipping-address screen glowed. “People spend time here, so it is important,” they said. Important compared with what? The cell was bright because the few sessions that reached it stalled, reread the form, and left. Most sessions never arrived. The empty screens earlier in the queue were the actual story.
Heatmaps aggregate attention without order. Screen Flow Analytics restores order. We drew nine cells for that checkout. Cell three — a coupon sheet that opened from a tiny link — sent a third of sessions back to the cart. Cell three was almost invisible on the heatmap because dwell time was short. People did not linger. They bounced.
What we did instead of arguing about colour
Twelve annotated replays. Written marks only: entered, reread, opened interrupt, returned, abandoned. No adjectives. After the twelfth session the coupon sheet was obviously a screen, not a “feature.” The team moved the coupon to a later cell, after address validation. Completed orders improved. The heatmap still glows on address. We do not present it anymore.
This is not an argument against heatmaps as a scout. It is an argument against letting a scout give the keynote. If you cannot place a bright cell on a grid, you do not yet know whether it is a destination or a trap.
A limitation worth saying
Our recordings missed in-store staff using the same web checkout on a shared tablet. Those sessions would have changed dwell on address for a different reason — typing with a customer watching. The grid is still incomplete for that group. We wrote that sentence on the brief. It belongs there more than a red overlay does.