North star metric

This concept sits within saas growth. Use the definition above to align terminology before comparing reports or planning work.

A SaaS example

A collaboration product may track teams completing a meaningful shared workflow, then pair that measure with retention, reliability and unit economics.

This is an illustrative scenario, not a reported result from a customer study. The point is to show the meaning of the term and the decision it affects.

The mistake to avoid

A metric that can rise while customers receive less value encourages activity without progress.

Put the definition to work

Define the event carefully, test its relationship with retained value and keep financial, quality and customer-harm guardrails visible.

When adding the term to a brief or dashboard, write down the scope and the evidence the team will use. Assign an owner for the definition so it does not change quietly between reporting periods. If two teams use the same label differently, resolve that difference before combining their numbers or handing work between them.

Related reading

• How to Build a SaaS Growth Model
• Growth Loops for SaaS
• SaaS Growth Strategies That Actually Compound
• B2B SaaS Growth

Browse the full glossary for adjacent definitions and the resource library for working materials.

Apply primary product outcome in a working review

Start by explaining the term without repeating its label. Then point to an observable example and a counterexample. If it is a metric, write the unit, numerator, denominator and time window. If it is a role, process or strategy, identify the responsibility or decision that distinguishes it from adjacent terms. This prevents a shared word from concealing different operating assumptions.

For this topic, involve the experiment owner and the analyst responsible for design integrity and work from hypothesis, assignment rules, metric definition and decision record. The relevant unit is the prespecified eligible user or account cohort. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

Check the design before interpreting a result. Assignment, exclusions, outcome timing and stopping rules can change the meaning of an apparently precise statistic. Separate practical effect from statistical evidence and keep guardrails beside the primary outcome.

Two situations that can change the interpretation

When the activation event is too easy to complete

A first login may be necessary, but it does not establish that a team created a usable project or resolved a support ticket.

Use this check: Compare the event with an observable customer outcome and later appropriate use. Do not select an event solely because it has the strongest correlation in a small sample.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When the experiment backlog ignores the main constraint

Changing a button color is unlikely to fix a workflow that requires an unavailable integration before any value can be reached.

Use this check: Map the current customer path and identify where suitable users fail to progress. A large drop-off is not automatically the best target if the users are intentionally ineligible.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

A higher signup rate is not automatically a better activation path if the removed step helped users reach a useful workflow. Review the complete sequence and the relevant customer outcome. A bundled product change can be evaluated as a bundle without claiming to isolate every component.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.