Measuring the Product You Chose
Measuring the Product You Chose
IN THIS LESSON
If the interviewer asks how you would measure the product you just recommended, apply the same causal logic used in Success Measurement: define the customer outcome, identify the behavior that indicates the product is producing that value, and choose metrics that make that behavior legible.
This is a bridge lesson rather than a second Success Measurement curriculum. The full method belongs in that module. Here, the job is to connect measurement to the concrete product you already designed.
What this task proves about you
A product recommendation is stronger when you can explain how you would know whether it is actually working.
This follow-up shows whether you can distinguish the customer value you want from the observable behavior or proxy you can measure. It also shows whether the product mechanism you described is clear enough to generate a sensible measurement plan.
Start with the customer outcome
Return to the pain you selected and ask what would be meaningfully better if the product worked.
For the adaptive study planner, the desired customer outcome is not simply that learners open the planner. The product exists to help deadline-driven learners use their limited study time more effectively so they can make better progress toward the result they care about.
That outcome anchors the measurement discussion. Without it, metrics can become a list of whatever events happen to be easy to instrument.
Identify the value-producing behavior
Ask what the customer does when the product is delivering its intended value.
For the planner, an important behavior may be completing recommended study work according to the plan. Opening the product or viewing the countdown may be useful supporting behaviors, but they are less direct evidence that the recommendation is changing how the learner allocates time.
The exact behavior should follow from the product mechanism. If you designed a parking product that recommends where to park and includes the parking-to-venue travel time, a useful behavior might be customers choosing the recommended parking destination and completing the trip with greater predictability.
Explain why the behavior matters before naming the metric. The metric is only useful because it measures something causally connected to the customer outcome.
Choose a simple primary metric
Once the key behavior is clear, choose the simplest interpretable metric that captures it reasonably well.
For the planner, you might measure the total amount of recommended study work completed or the number of recommended sessions completed. Which formulation is better depends on what most directly represents value in the product you designed.
Do not make the metric more sophisticated than the decision requires. A complicated composite score does not create better measurement merely because it includes more information.
If the true outcome is hard to observe, use a proxy and state the relationship you are relying on. For example, if actual exam outcomes arrive slowly or are unavailable for many users, following the study plan may be a useful leading indicator. The proxy is credible only to the extent that its relationship to the desired outcome is plausible and can eventually be checked.
Add only the supporting metrics that change interpretation
A primary metric usually needs some context.
You may want to know how many customers are using the product, whether use persists over time, whether the product is reliable, or whether an important negative outcome is increasing. Add those metrics when they help explain the primary outcome or protect against a plausible failure mode.
For the planner, a high amount of completed recommended work would look less attractive if learners routinely abandon the product after a few days, if recommendations become infeasible after schedule changes, or if following the plan increases time spent without improving preparedness.
Do not reproduce the entire Success Measurement taxonomy inside a Product Sense follow-up. Choose the few measures that are most consequential for this product and explain why they are useful.
Measure the product you actually chose
The measurement discussion should inherit the specificity of the solution.
If the key product idea is a prominent countdown and a daily recommendation, it may be useful to measure whether learners act on that recommendation. If the product is a marketplace, measure the behavior on both sides that is required for the exchange to produce demand-side value. If the product is a recommendation system, measure whether customers accept or act on the recommendation and whether that behavior improves the intended outcome.
Avoid switching back to generic company metrics simply because they are familiar. The broader business objective still matters, but this follow-up is asking how the chosen product contributes to it.
Practice
Take one completed Product Sense recommendation and answer:
- What customer outcome should improve if this product works?
- What customer behavior most directly indicates that value is being created?
- What simple primary metric can measure that behavior?
- Is the metric the outcome itself or a proxy? If it is a proxy, what relationship are you assuming?
- Which one or two supporting or guardrail metrics would materially change how you interpret the result?
Present the measurement plan in a short paragraph. If you find yourself listing many metrics without explaining what they tell you, return to the behavior and simplify.
For the full method, including ecosystem analysis, North Star selection, tracking metrics, proxies, and guardrails, use the Success Measurement module.
The point
Measure the product by tracing the same causal chain that justified building it. Start with the customer outcome, identify the behavior that indicates the product is creating that value, choose a simple interpretable metric, and add only the supporting measures needed to understand or protect the result.
Was this lesson helpful?
Your feedback helps improve lesson quality.