Hotjar's Product Planning Playbook: Evidence Banks, Opportunity Trees, Impact Analysis

Hotjar runs its entire product planning cycle on three lightweight artifacts — an Evidence Bank, Opportunity Trees and Impact Analysis — contributed to at least twice per week, and the company says they keep goal setting light enough to avoid what it calls planning fatigue.

The model, described by Hotjar's VP of Product in a ProductLed article, rests on one structural decision: decouple the work from the goals. Goal setting at Hotjar is not a priority list or a prescribed sequence of steps. It is the identification of where the goalposts are, with flexibility for teams to decide how to reach them.

How does Hotjar structure annual and quarterly goals?

Hotjar sets objectives along key metrics on an annual basis, and those annual intentions stay steady even as weekly or quarterly objectives shift in response to the marketplace. The company recently embarked on a new three-year product strategy, under which it sets annual company objectives, then tribe and squad quarterly objectives.

Four principles govern the cadence:

• Align cycles with the calendar. Whether goals reset every two weeks, every month or every quarter, the cadence must support the overall strategy.
• Stay flexible on the how. A quarterly objective to convert one hundred new customers leaves room to try different approaches without resetting the objective.
• Publish a goal-setting calendar. Hotjar's operations team releases one each quarter so the whole company knows what is expected, when, and by whom.
• Set expectations well in advance. This keeps planning intact when team members fall ill or take vacation.

The takeaway: fixed goalposts plus a published calendar keep a changing market from breaking the plan.

How do tribes and squads set goals?

Hotjar organizes product work into tribes — design, data, engineering and similar teams — and each tribe contains squads focused on different points of the customer journey. Each tribe sets its own goals and objectives in support of the company-wide annual objectives. Tribe-level objectives steer all squads in the same direction while leaving them flexibility on execution.

The stated failure mode is real: an individual squad moving forward on its own can pursue sub-optimizations and lose sight of how the product is greater than the sum of its parts.

What is the Quarterly Goal Hub?

The Goal Hub is a simple artifact with a timeline, linked to boards, pages, metrics and dashboards. It specifies which activities are assigned to each squad, product manager, tribe or executive team member, holding all of them to the same level of accountability. It serves two purposes:

• Capturing questions publicly. Questions and responses live in a system visible to everyone, which prevents silos from forming.
• Accounting for the human factor. Holidays, scheduled leave, company-wide events and maternity leave get planned in, even for an ambitious quarter.

What is the PM's three-phase system?

Hotjar treats the Evidence Bank, Opportunity Trees and Impact Analysis as core ways of working, not quarterly-only exercises. Product leadership is responsible for delineating which activities are normal ways of working and which belong to the goal-setting cadence; when that line blurs, teams burn out on planning.

Evidence Bank. A single, searchable repository mixing quantitative data, qualitative anecdotes and market signals. All product managers contribute — Hotjar averages at least two contributions per week — and contributors include links so anyone can reach the source of each data point. The premise: a shared repository lets the broader team spot evidence and trends no individual would find alone. Hotjar's guidance is blunt about the tradeoff: an imperfect solution beats ignoring the problem, because waiting for the perfect one produces chaos, rework and redundancy.

Opportunity Trees. These consume the evidence bank's data. A team member arrives at the board, views weekly active users, average revenue per account and basic B2B metrics with a performance summary, then moves to the tree. Tribe objectives and key results sit on the left; each PM outlines opportunities, frames hypotheses, and links to the informing evidence. Ideas land in a Solutions column, open to squad input. The VP of Product deliberately limits personal involvement to objectives, key results and occasionally opportunities — any solution they propose must carry the same evidence and assumptions as anyone else's. Sizing and selecting opportunities remains one of the PM's most important responsibilities, because not every good idea is worth building.

Impact Analysis. Every change carries uncertainty, so Hotjar compares the predicted impact of maintaining the status quo against pursuing a tree solution. The analysis varies — finance may help with modeling, engineering with feasibility — and starts from a hypothesis plus its supporting data, using ultra-lightweight templates. The output is a repeatable evaluation that feeds the next goal-setting cycle with already-assessed opportunities.

From there, quarterly goal setting begins with an informal discussion: leadership and PMs share qualitative, quantitative and market context, evaluate performance against annual objectives, then refine tribe objectives so PMs can plan squad objectives.

What rituals round out the cycle?

Two optional-but-recommended practices accompany each quarter:

• Office Hours. Leadership holds daily open slots until squad-goal deadlines. No slides, no formality — the point is a safe space for PMs to raise hard questions that would seriously affect their squad's work.
• Challenge Days. PMs pair in groups of two, ideally with partners outside their daily circle, and challenge each other's objectives, hypotheses and impact analyses. Hotjar credits the format with cross-pollinating ideas across tribes, seeding peer mentorship and preventing PMs from working on an island.

The framework's conditions are worth noting: it presumes a stable annual strategy, tribes with clear charters, and leadership willing to publish calendars and hold itself to evidentiary standards. Where those preconditions fail, the artifacts become overhead. As product orgs flatten planning into continuous discovery, models like this — goal setting as a lightweight byproduct of daily working habits — point to where the practice is heading.