PostHog · Strategy · Mid · 45 to 60 minutes

Which user and workflow should PostHog own?

PostHog is a developer focused product platform with tools for analytics, session recording, feature flags, experiments, and customer data flows. Answer this product management case and get it graded line by line against a weighted rubric.

Strategic thinking
Segmentation
Prioritization
Product sense
Metric design

The situation

You are a PM at PostHog preparing input for annual planning. The founders believe the company has reached product market fit and now needs a much clearer product area strategy. PostHog already offers multiple developer tools, including product analytics, session recording, feature flags, experiments, and a growing set of integrations. Adoption is strong among technical teams, with 23,000+ companies installed and a large developer community, but the roadmap is pulling in several directions. Some people want to serve classic product managers more directly. Others want to chase bigger enterprise analytics budgets. Others argue PostHog should focus on becoming the system that technical teams install first, then expand from there. There is also a longer term risk that as customers mature, their data warehouse becomes the source of truth and point tools lose relevance. The CEO asks you for a recommendation on who PostHog should primarily serve, which product jobs it should own, and where it should enter the workflow so the company can grow share of wallet over time without losing focus.

What to produce

A 1 to 2 page product strategy memo.

Your answer must

State PostHog's primary target user in one sentence and defend the choice with 2 to 3 reasons tied to adoption, product need, and business value.
Compare at least 2 credible strategic directions for the product area and make a clear recommendation.
Define which workflow steps or jobs PostHog should aim to own first, next, and not now.
Recommend 2 to 4 product investment priorities for the next 12 months and 1 to 3 explicit depriorities.
Explain how your strategy handles the risk that customer data shifts into a warehouse or other system of record as companies scale.
Propose success metrics, leading indicators, and one major risk with a mitigation plan.

Constraints

Assume only one primary strategic bet can receive about 60 percent of roadmap capacity over the next 12 months.
Your recommendation must fit a developer led, self serve motion and cannot depend on building a large enterprise sales org.
Build on PostHog's current product surface and community, not acquisitions or a new buyer segment.

Format

Use short headings and, if helpful, a simple table for options, priorities, and metrics.

How PostHog actually played it

PostHog explains how it simplified its strategy to helping engineers do product well, by supplying every tool for evaluating feature success and being the pipeline for customer data. The post notes that engineers are often treated as a resource rather than product decision makers. A concise example of narrowing a strategy.

The simpler a strategy, the more likely it is right
Name the user you serve in one sentence and build for them
Own the earliest step in a workflow to capture later spend

Built from Our simpler goal: Help engineers to be better at product by James Hawkins.