Mixpanel · Metrics · Mid · 45 to 60 minutes

Should Mixpanel rethink its navigation?

Mixpanel is a product analytics platform that helps teams understand how people use their products. Answer this product management case and get it graded line by line against a weighted rubric.

Metric design
Product judgment
Experimentation
Trade-off analysis
Structured communication

The situation

You are the PM for a core product experience area at Mixpanel. The design lead and a product executive have asked you to assess whether Mixpanel's main navigation is helping or hurting users as the product grows. Today, navigation elements are split across a top bar and a sidebar, and there are signs that some users are unsure where to go for certain tasks and pages. Internal teams have raised concerns about discoverability, but a navigation change would affect many workflows, and experienced customers may be sensitive to disruption. You need to recommend how to evaluate the problem and what success would look like before the team commits engineering and design time. The challenge is that confusion can look similar to low feature interest, and a change that improves discovery for some users could slow down others. Leadership wants a data grounded plan, not a redesign pitch. They expect you to use Mixpanel's own analytics thoughtfully, define the right usage metrics, and show how you would decide whether to keep the current structure, test alternatives, or make no change.

What to produce

Write a 1 to 2 page product memo.

Your answer must

Define the user problem clearly, including why split navigation might create confusion and which user groups are most likely affected.
State the decision you are trying to make and list 3 to 5 metrics you would use to judge it, including at least one discoverability metric and one guardrail metric.
Describe how you would use product data to distinguish navigation confusion from genuinely low demand for a destination or feature.
Propose a test or analysis plan that could support a decision, including key segments, event instrumentation, and how long you would monitor results.
Discuss the main trade-offs of changing navigation versus keeping it as is, and give a recommendation for next steps with clear success criteria.

Constraints

Work only from the information in this prompt and general knowledge of what Mixpanel is, do not assume unpublished roadmap details or customer facts.
Your initial plan should rely primarily on existing product analytics and currently available qualitative signals, not a brand new research program.
Keep the scope to navigation structure and discoverability within the existing product shell, not a full visual redesign or new feature strategy.

Format

Use short sections with headings: problem, metrics, analysis plan, trade-offs, recommendation.

How Mixpanel actually played it

Mixpanel used its own product data to guide a navigation redesign, after learning the split between top bar and sidebar confused users. The post shows the problem, the consolidation to the left side and the key metrics that improved, such as more people reaching Lexicon. A neat example of measuring a UX change with product metrics.

Name the user confusion before redesigning
Pick specific usage metrics to judge the change
Dogfood your own analytics for product decisions

Built from How we build with data: Experimenting with Mixpanel's new side navigation by Mixpanel team.