Hotjar.

Where Hotjar fits on a long engagement.

Session replay is the fastest route to understanding a problem nobody can reproduce. Watching ten recordings of a failing checkout usually explains more in twenty minutes than a week of hypothesis, because the behaviour is real rather than reported.

Heatmaps are more often misread. Aggregate click density tells you where attention went, not why, and it is easy to build a confident narrative on top of a pattern that has a mundane explanation. It is a tool for generating hypotheses rather than settling them.

What an assigned team does with Hotjar.

Session replay answers questions nobody can specify in advance, which makes it a standing capability rather than a tool you buy for a project. Its value is highest in the week after a release and in the hour after a support escalation.

Interpreting behaviour well takes product context that accumulates, so it belongs inside a continuous design assignment under outsource UX design rather than a one-off audit.

What we use Hotjar for.

• Understanding an unreproducible bug Watching what the user actually did before the failure, rather than relying on a ticket description.
• Locating funnel drop-off Finding the exact step where people leave, so effort goes to the step that matters.
• Checking a launch Observing real behaviour on a new flow in its first days, while changes are still cheap.

How Hotjar capacity is assigned.

Behavioural research sits within an outsourced design team assignment rather than being scoped separately. Capacity is agreed as a committed monthly capacity rather than per skill.