PostHog · Product sense · Entry · 45 to 60 minutes

What should happen to the Sessions page?

PostHog is a product analytics platform that helps teams understand user behavior and watch session recordings. Answer this product management case and get it graded line by line against a weighted rubric.

problem framing
product sense
prioritization
user empathy
written communication

The situation

Your manager, a product lead at PostHog, asks you to review the Sessions page after a steady stream of support questions. Users say they cannot find expected recordings there, and others do not understand what PostHog means by a session in the first place. At the same time, some people do use the page to analyze behavior by session, while others seem to treat it as a doorway to watch recordings. Assume the team has seen about 12 support threads on this topic in the past month, and the page still gets regular traffic from existing users. You need to recommend what PostHog should do next with this part of the product. The hard part is that confusing pages create support cost and trust issues, but removing or changing a page could break habits for current users and make navigation worse if there is no clear replacement. You have limited time for a near term decision and cannot run a long research project first.

What to produce

Write a 1 page product recommendation memo, 500 to 700 words.

Your answer must

Define the core problem in user terms, not just as a support issue.
Identify the distinct jobs users are trying to do on or around the Sessions page, and explain whether one page should serve both.
Lay out at least two realistic options, then recommend one direction for the near term.
Describe the main risks of your recommendation for existing users, especially people looking for recordings and people doing session based analysis.
Propose a rollout and communication plan that tells users clearly what to use instead if any workflow changes, plus 2 to 4 success metrics.

Constraints

Work within PostHog's existing analytics and recordings areas, not a full product redesign.
Optimize for a change that one small product squad could ship in the near term.
Use available support and product usage signals, and do not depend on months of new research before making a recommendation.

Format

Use short sections such as problem, user jobs, options, recommendation, risks, rollout, and metrics.

How PostHog actually played it

PostHog explains why it removed its Sessions page after users kept reporting confusion about missing recordings and unclear session definitions. The team split the page's two real use cases, session based analytics and watching recordings, and moved recordings to their own tab. It is a short, concrete example of deprecating a feature based on support signals.

Recurring confusion in support is a reason to question whether a page should exist at all
Separate the real jobs a feature does before deciding what to keep
Tell users what replaces a removed feature in the same announcement

Built from Why we're removing the sessions page by Paolo D'Amico.