Why this document exists
Session recording tools (Microsoft Clarity, Hotjar, Contentsquare) show where your users hesitate, but not why.
To find out, you need a reading framework that combines three layers:
- what you see on screen,
- what the user is asking themselves at that exact moment,
- and the architectural decision that creates this friction
Without this framework, a session review turns into free-form commentary, and every team reads the same footage differently. With it, the creative, CRO, and tech teams speak the same language, and the meeting ends with the right test instead of a list of "ideas to explore."
You need to read Clarity sessions as diagnostics, not as replays. Discover 20+ behavioral signals, their architectural causes, and the priority tests that go with them.
