TL;DR: Most product teams measure product health, not product strategy. These are different things. Product health metrics (daily active users, retention, NPS) tell you how the product is performing. Strategy metrics tell you whether the strategy you chose to pursue was the right one. A product can have excellent health metrics and a failing strategy at the same time. This guide covers the four questions strategy measurement actually needs to answer, the metrics that reveal strategic direction rather than operational performance, and how to build a quarterly strategy review that produces something other than a retrospective on what shipped.

The difference between product health and product strategy

This distinction is the starting point for everything else in this guide.

Product health measures how the product is performing right now: engagement, retention, revenue, satisfaction. A healthy product has users who return, pay, and recommend it. Health metrics are essential and should be tracked continuously. They tell you whether the product is working.

Product strategy answers a different question: is the direction we chose to invest in moving us toward a sustainable, differentiated market position? A team can ship every roadmap item, hit every quarterly health metric, and still be executing a strategy that will look obviously wrong in eighteen months.

The measurement failure most product teams have is treating health metrics as strategy metrics. When a board asks "is your product strategy working?" and a CPO answers with DAU growth and NPS improvement, they have answered the health question and left the strategy question unanswered.

Strategy measurement requires metrics that reveal whether the strategic choices you made are creating the competitive position and customer outcomes you intended. These are not the same as health metrics, they take longer to appear, and they are harder to collect. But they are the only metrics that tell you whether the strategy was right.

The four questions strategy measurement needs to answer

A product strategy, reduced to its core, is a set of choices about which customers to serve, which problems to solve for them, and how to do that in a way that is difficult for competitors to replicate. Measuring whether the strategy is working means measuring whether those choices are producing the intended outcomes.

Question 1: Are you winning with the customers the strategy is designed for?

Every strategy targets a specific customer type. The question is not whether all customers are engaged, but whether the customers the strategy is designed for are engaged at a disproportionately high rate. If your strategy is built around serving enterprise engineering teams, the relevant measure is not overall retention but retention in enterprise engineering accounts specifically. If that cohort is retained and expanded at a higher rate than your other customers, the strategy is working with its intended target. If it is not, the strategy is either wrong about who to target or wrong about what those customers need.

Question 2: Are you solving the specific problem the strategy identifies as central?

Most product strategies include an implicit or explicit theory: if we solve problem X for customer Y, they will find our product uniquely valuable. The strategy measurement question is whether customers are actually experiencing the solution to that specific problem, not just using the product in general. A team whose strategy is "help engineering managers get cross-project visibility without attending every standup" should measure whether engineering managers are achieving that outcome, not whether the product is used frequently by anyone.

Question 3: Is the differentiation your strategy relies on actually differentiating?

Strategy requires a reason why your product is better for the target customer than alternatives. The measurement question is whether that differentiator is actually producing different outcomes than competitors for that customer. This is the hardest question to measure, because it requires some knowledge of what customers experience with alternatives, which typically comes from win/loss interviews, NPS verbatims, and competitive displacement data rather than product analytics.

Question 4: Is the strategic position becoming more defensible over time?

A strategy that works today is valuable. A strategy that compounds value as time passes is a competitive moat. The measurement question is whether the advantages your strategy relies on are growing or eroding. A strategy built on data network effects should show increasing accuracy or relevance as more customers use the product. A strategy built on switching costs should show declining churn rates as customer tenure increases. If the strategic advantage is not measurable in these terms, it may not exist in a meaningful form.

Leading indicators that reveal strategic direction

Standard product health metrics are lagging indicators that tell you what happened. The metrics below are the ones that tell you whether your strategy is on track before the lagging indicators confirm it.

Cohort divergence: target customers vs everyone else

This is the most important strategic leading indicator and the least commonly tracked. Take the cohort of customers your strategy is explicitly designed for and compare their activation rate, retention rate, and usage depth against every other customer cohort. If your strategy is working, target customers should show meaningfully better outcomes than non-target customers.

If target customers are not performing better than average, there are two possibilities: the strategy is correct but the product has not yet solved their problem well enough to show up in the data, or the strategy is wrong about which customers find the most value. Either requires investigation before the lagging indicators confirm the problem two quarters later.

Problem resolution rate: are customers achieving the specific outcome the strategy targets?

This requires defining the specific outcome the strategy is designed to produce and measuring whether customers reach it. The outcome is usually not "used the product" but something more specific: "created a cross-project view without a meeting," "approved a budget without a spreadsheet," "completed onboarding in under five minutes." If this is not measured, you cannot know whether the strategy's central premise is true.

Tracking this requires instrumenting the specific workflow the strategy identifies as central, not just overall product usage. Teams that do this consistently find that the gap between "used the product" and "achieved the strategic outcome" is larger than they expected and reveals where the product needs to improve to deliver on the strategy's promise.

Signal quality: is customer feedback becoming more specific and strategic?

This is a qualitative leading indicator, but it is worth tracking. When a strategy is working with its intended customers, the feedback from those customers tends to become more specific over time. Instead of "this product is useful," you hear "we rely on this for X and need it to do Y next." The specificity of feedback from target customers is an indicator that they have integrated the product deeply enough to have strategic opinions about it.

When you are not hearing specific, constructive feedback from the customers your strategy targets, one of two things is true: they are not using the product deeply enough to have strategic opinions, or they have already decided not to invest in it further and are about to churn without telling you.

Win rate in the strategic segment

If the strategy is working, sales win rates in the target segment should be higher than in other segments. A product team that does not track win rates by customer segment does not know whether their strategy is producing a competitive advantage in the market they have chosen to compete in. This data requires coordination with sales and revenue operations, but it is one of the most direct measures of whether the strategic differentiation claim is validated by actual purchasing decisions.

Expansion revenue from target customers

Expansion revenue from customers who fit the strategic target is the leading indicator for whether the strategy produces lasting commercial value. Customers who find the product strategically valuable expand their usage and spend over time. Customers who find it useful but not strategically central do not. Tracking NRR (net revenue retention) specifically for the target customer cohort, rather than overall NRR, reveals whether the strategic position is producing the expected commercial flywheel.

Lagging indicators to track and how long to wait

Lagging indicators for strategy appear on a longer horizon than health metrics. The most important:

Market share in the target segment. Measured annually at minimum, quarterly if data is available. A strategy that is working should produce growing market share in the specific segment the strategy targets. This requires knowing the size of the relevant segment (through analyst data, customer surveys, or sales pipeline analysis) and tracking penetration over time.

Customer lifetime value by cohort. A strategy that creates genuine differentiation should produce higher LTV for target customers than for non-target customers. Tracking this quarterly by cohort and vintage reveals whether the strategic position is deepening over time or remaining flat.

NPS from target customers vs general NPS. Overall NPS is a health metric. NPS specifically from target customers is a strategy metric. If target customers are not significantly more satisfied than average customers, the strategy's differentiation claim is not yet validated in customer experience.

Churn rate trends in target segment. Absolute churn rate is a health metric. The trend in churn rate for target customers over four or more quarters is a strategy metric. A working strategy should produce declining churn in the target segment as the product becomes more deeply integrated into those customers' workflows over time.

The signals that strategy is going wrong before the data confirms it

These are the early warning patterns that precede the lagging indicator deterioration that makes strategy failure obvious:

Target customers are using the product differently than the strategy anticipated. When customers in the strategic target segment are using the product primarily for a purpose the strategy did not identify as central, the strategy's premise is wrong. The product is valuable for something, but not for the reason the strategy is based on. This usually appears first in qualitative customer interviews before showing up in product analytics.

Sales is winning in the wrong segments. When pipeline analysis shows high win rates outside the target segment and low win rates inside it, the market is telling you that the strategic differentiation claim is not resonating with the intended target. This can indicate a positioning problem, a product problem, or a strategy problem. Distinguishing between them requires customer research, but ignoring this signal leads to a product optimised for the segment it is accidentally winning rather than the segment the strategy targets.

Competitive displacement is moving in the wrong direction. If win/loss data shows the product winning against its strategic targets but losing more frequently to a specific competitor that was not the primary threat, a competitor is executing a strategy that is producing better differentiation in the target segment. This is the most important early warning signal and the one that requires the fastest strategic response.

The strategic differentiator is not mentioned in customer testimonials. When customers are happy to recommend the product but their reasons are not related to the strategic differentiator, the product is delivering value through a different mechanism than the strategy claims. This is not necessarily a problem if the unintended value is commercially significant, but it means the strategy needs to be updated to reflect what is actually working rather than what was originally intended.

How to run a quarterly strategy review that produces answers, not reports

Most quarterly strategy reviews are retrospectives on what was shipped. A strategy review that produces a useful output answers the four measurement questions above with current data.

The agenda that works:

The review starts with the strategic questions, not the health metrics. Begin with: are we winning with our target customers at a higher rate than everyone else? What does the cohort divergence data show? What did win/loss data in the target segment look like this quarter?

Bring three specific pieces of qualitative evidence: two customer stories from target customers that illustrate whether the strategic problem is being solved, and one story from a target customer who churned or did not expand, including their stated reason.

The health metrics section is second, not first. Review them in the context of the strategic indicators: did the cohorts that are strategic priorities perform better or worse than average? Where did the gap widen or narrow?

The review ends with the strategic decision: is the strategy still correct, does it need adjustment, or does it need to be changed? This decision should be made and documented, not deferred to the next planning cycle.

What to document:

The most important output of a quarterly strategy review is not a slide deck. It is a written record of the strategic hypothesis going into the quarter, what the data showed, what the team concluded, and what changed or did not change as a result. This record is what enables a CPO to answer the board question "has your strategy been working?" with evidence rather than confidence.

Squad AI tracks goal performance continuously across quarters, meaning the strategic hypothesis and the signal data that tests it are maintained in the same system. When a quarterly review arrives, the comparison between intended and actual is available without a manual data collection exercise.

Frequently asked questions

How do you know if a product strategy is working?
A product strategy is working when the customers it is designed for are performing measurably better on the outcomes the strategy identifies as central, when win rates in the target segment are higher than in other segments, and when expansion revenue from target customers is growing over time. These are different from overall health metrics and require tracking at the cohort level by strategic segment rather than across all customers.

What is the difference between product health metrics and product strategy metrics?
Product health metrics measure whether the product is performing well overall: daily active users, retention, revenue, NPS. Product strategy metrics measure whether the specific direction chosen is creating a defensible competitive position with the intended customer type: cohort divergence between target and non-target customers, win rates in the strategic segment, problem resolution rates for the specific outcome the strategy targets, and the trend in churn rate for target customers over multiple quarters.

How long does it take for a product strategy to show results?
Strategy typically takes six to eighteen months to produce measurable results in lagging indicators like market share, customer lifetime value, and overall retention. Leading indicators like cohort divergence and win rates in target segments should show movement within two to three quarters. If there is no movement in leading indicators after two quarters, the strategy either needs adjustment or the measurement is tracking the wrong metrics.

What is a North Star metric and is it a strategy metric or a health metric?
A North Star metric is designed to be both: a single number that captures the core value the product delivers, which serves as a leading indicator for long-term business health. In practice, North Star metrics often drift toward becoming health metrics because teams measure a proxy for value delivery rather than value delivery itself. The most useful North Stars are the ones where every point of improvement in the metric demonstrably predicts better lagging outcomes for the strategic target customer, not for all customers broadly.

What should a quarterly product strategy review cover?
A quarterly strategy review should answer four questions: Are we winning with the customers the strategy is designed for at a higher rate than everyone else? Are those customers achieving the specific outcome the strategy identifies as central? Is the differentiation the strategy relies on producing a measurable advantage in win rates and expansion revenue? Is the strategic position becoming more defensible over time, shown in improving cohort metrics by tenure? The review should document the strategic hypothesis going in, what the data showed, and what the conclusion is. Health metrics are context, not the primary subject.

How do you measure product-market fit for a specific strategic segment?
Segment your NPS or retention data by the specific customer type your strategy targets. A product that has achieved product-market fit in its strategic segment will show meaningfully higher retention and NPS in that cohort than in the broader customer base. Sean Ellis's PMF question ("how would you feel if you could no longer use this product?") applied specifically to the strategic target customer provides a qualitative signal. Measuring the percentage of target customers who answer "very disappointed" at 40% or above is the original Ellis benchmark for PMF in that segment.

Sources: Richard Rumelt, Good Strategy/Bad Strategy (2011); Sean Ellis PMF Survey methodology; Reforge Product Strategy frameworks; McKinsey State of Product Management 2024; Amplitude leading and lagging indicators guide (July 2026); Herbig.co Leading and Lagging Indicators for Product OKRs. Last updated: August 2026 · meetsquad.ai