The Goal of a Product Sense Answer

Product sense is not about memorizing metrics or frameworks. It is about showing that you can quickly understand a business, identify what matters most, and make good product decisions grounded in data.

Think of it as telling a story:

Understand the business → Understand the product → Understand the users → Define success → Measure it correctly.

The steps below walk that story end to end. Each Quick check is a question to try in your head first — then click to reveal the model answer. The gap between your take and the model answer is where product sense actually grows.

Step 1 — Understand the business first

Before talking about metrics or user behavior, zoom out and understand the company. Ask:

What problem does this product solve?
How does the company make money? What is its business model?
Who are its competitors?
How is the industry changing, and what makes this product different?

Don't jump into details yet — start with the big picture. Without understanding the business, it is hard to know which metrics actually matter.

Quick check. Before reading on, put it in your own words: what problem does Spotify solve, how does it make money, who are its main competitors, and what is its biggest cost tension?

Step 2 — Understand the product structure

How the product is built determines what the team must solve. Ask:

Subscription or transactional?
A marketplace with buyers and sellers (one-sided or two-sided)?
A social network? Content-driven or search-driven?

Different structures need different success metrics.

Quick check. Classify each of these by product structure — Netflix, Uber, Airbnb, TikTok, Amazon. What is each one, structurally?

Step 3 — Understand the user journey

Walk the user from first touch to loyal habit:

Discover → Sign up → Try the core feature → Become active → Build a habit → Stay loyal

At each stage ask: where do users drop off, what blocks them, and which step creates the most value? If the product has multiple user types, map each journey separately — Uber has riders and drivers, YouTube has viewers and creators, Airbnb has guests and hosts. Each has different goals and metrics.

Quick check. Map Uber's two user journeys — rider and driver — and name a key drop-off in each. What connects the two sides?

Step 4 — Identify what the product really cares about

Every successful product has one core objective. Ask: if this product is succeeding, what is happening?

Quick check. In one phrase each, what does success happening look like for Netflix, Uber, LinkedIn, and Amazon?

Step 5 — Define the North Star Metric

The North Star Metric (NSM) is the single measure of the core value the product delivers. A good one:

Measures real value, not popularity.
Reflects long-term success and ties closely to business growth.

Avoid vanity metrics — total downloads, registered users, page views — which look impressive but don't prove the product is healthy.

Quick check. Pick a defensible North Star for Uber, Spotify, and Airbnb — then explain why registered users is a vanity metric.

Step 6 — Break the North Star into drivers

One number isn't enough — decompose it into the smaller metrics that explain why it moves. These drivers show you where a problem lives.

Revenue = Users × Paid-conversion rate × ARPU

A subscription product's revenue, broken into levers

Net new users = New users − Churned users + Reactivated users

Growth, broken into levers

Quick check. If net new users dropped this month, which driver would you check first — and how does the decomposition guide you?

Step 7 — Add guardrail metrics

Optimizing one metric can quietly harm the business, so every important metric needs a guardrail that catches unintended side effects. Common guardrails: retention, customer satisfaction, churn, crash rate, content quality, and trust & safety.

Quick check. You ship more push notifications and DAU rises 8%. Before celebrating — which guardrails must you check?

Step 8 — Put it together: a research framework

Once you understand the business and the metrics, investigate problems systematically instead of guessing:

Business
  → Competitors & business model
  → Product structure
  → User journey
  → Core product value
  → North Star Metric
  → Driver metrics
  → Guardrail metrics
  → Identify the problem
  → Recommend improvements

This keeps your thinking organized and ties every recommendation back to a business goal.

Common mistakes to avoid

Jumping straight to metrics without understanding the business.
Choosing vanity metrics (total users, downloads).
Listing many metrics without explaining how they connect.
Forgetting guardrail metrics.
Ignoring different user groups in a marketplace or social product.
Focusing only on engagement, ignoring revenue and retention.

Strong product sense isn't the longest list of metrics — it's understanding why each metric matters and how it connects to the product's success.

A simple mental framework

Whenever you get a product-sense question, run this sequence:

Business → Product → Users → User Journey → Core Value
        → North Star → Drivers → Guardrails → Insights → Recommendations

Follow it consistently and your answers will be structured, logical, and close to how experienced PMs and data scientists actually reason. For the metrics half in depth, see the How to Define Metrics guide.