How to Define and Calculate a North Star Metric with Supporting Input Metrics

A North Star Metric is a single, customer-centric KPI that captures core product value and acts as a leading indicator of long-term business success, validated against seven specific criteria and supported by 3-5 actionable input metrics.

The phuryn/pm-skills repository provides a comprehensive framework for product managers to define, calculate, and implement a North Star Metric (NSM) within their organizations. According to the source code in pm-marketing-growth/skills/north-star-metric/SKILL.md, an NSM is not merely a revenue figure or collection of metrics, but the one metric that, when moved, pulls the entire business forward while satisfying strict validation criteria.

Understanding the North Star Metric Framework

A North Star Metric serves as the central compass for product teams, aligning everyone around the value delivered to customers. Unlike lagging indicators such as monthly revenue or vanity metrics like total downloads, the NSM must be customer-centric, quantitative, and actionable according to the repository's specification.

The framework distinguishes between three critical components:

1. The North Star Metric itself – the single top-line indicator
2. Input metrics – the levers that drive the NSM in the short term
3. Counter-metrics – guardrails that prevent gaming the metric (Goodhart's Law)

Step 1: Classify Your Business Game

Before selecting an NSM, identify which "business game" your product plays. The taxonomy in SKILL.md categorizes products into three archetypes that inform the shape of your metric:

Game	Measures	NSM Shape	Example Companies
Attention	Time or engagement users spend	Minutes spent, daily active users	Facebook, Spotify, TikTok
Transaction	Number/value of transactions	Transactions per month, gross merchandise value	Amazon, Uber, PayPal
Productivity	Efficiency gains for users	Tasks completed, projects shipped	Notion, Canva, Dropbox

Choosing the correct classification ensures your North Star Metric reflects the actual value exchange between user and product.

Step 2: Validate Against the Seven NSM Criteria

According to pm-marketing-growth/skills/north-star-metric/SKILL.md, every candidate metric must pass seven validation checks before becoming your NSM:

1. Easy to Understand – Stated in plain language without jargon
2. Customer-Centric – Reflects value delivered to the customer, not just revenue extracted
3. Sustainable Value – Ties to habits or long-term engagement patterns
4. Vision Alignment – Advances the company's stated mission
5. Quantitative – Measurable numerically with clear counting rules
6. Actionable – Teams can directly influence it through product, marketing, or operational changes
7. Leading Indicator – Changes predict future business performance (e.g., revenue growth)

A metric must score positively on all seven criteria to qualify as your North Star Metric.

Step 3: Define Your Input Metrics

Input metrics (also called supporting metrics) are the levers that move your NSM in the short term. The repository recommends selecting 3-5 input metrics that satisfy three characteristics:

• Easier to move than the NSM itself, providing quick feedback loops
• Directly causal to the NSM, with clear hypothesis chains
• MECE (mutually exclusive, collectively exhaustive), ensuring the full set explains NSM movement

Typical input categories include activation/onboarding completion rates, feature usage frequency, conversion rates between product stages, and retention drivers.

Step 4: Build the Metrics Constellation

Combine your NSM and input metrics into a visual or tabular "constellation" that shows causal relationships and ownership. The pm-marketing-growth/commands/north-star.md file provides a ready-to-use markdown skeleton for this documentation.

The constellation should clearly map:

• Which team owns each input metric
• How each input mathematically or logically drives the NSM
• Current baselines and target values for each lever

Step 5: Validate and Iterate

Implementation requires continuous validation:

• Run the validation table (criterion ✓/✗) for your NSM quarterly
• Review input metrics for completeness and ownership accuracy
• Add counter-metrics to guard against unintended optimization (e.g., "support tickets per active user" prevents sacrificing quality for engagement)
• Re-evaluate annually or when the business model shifts significantly

Implementation Examples

Using the North Star Command

The repository includes a slash command for interactive NSM definition. Invoke it with:

/north-star B2B SaaS for team collaboration

The command workflow defined in pm-marketing-growth/commands/north-star.md executes four steps:

1. Asks clarifying questions about product value, business model, and current metrics
2. Classifies the business game (likely Productivity for collaboration tools)
3. Proposes 2-3 NSM candidates, scoring them against the seven criteria
4. Generates a markdown framework ready for editing and sharing

Markdown Output Template

The command outputs a structured template that you can paste directly into documentation repositories:

## North Star Framework: Team Collaboration SaaS

**Business Game**: Productivity

### North Star Metric

**Metric**: Weekly Active Teams (WAT)  
**Definition**: Number of distinct teams that generate at least one collaborative event per week.  
**Why this metric**: Directly reflects product-driven teamwork value, predicts revenue growth, and is team-owned.  

### Validation

| Criterion                | Pass? | Notes |
|--------------------------|-------|-------|
| Easy to Understand       | Y     | Everyone knows "active team". |
| Customer-Centric         | Y     | Measures real collaborative value. |
| Sustainable Value        | Y     | Teams tend to stay once they adopt. |
| Vision Alignment         | Y     | Supports mission to enable better teamwork. |
| Quantitative             | Y     | Countable weekly. |
| Actionable               | Y     | Product, onboarding, and support can improve it. |
| Leading Indicator        | Y     | Correlates with ARR growth. |

### Input Metrics

| Input Metric               | Drives North Star By | Owner      | Current | Target |
|----------------------------|----------------------|------------|---------|--------|
| Team onboarding completion | Faster adoption      | Product    | 45%     | 80%    |
| Feature usage depth        | Higher collaboration | Engineering| 3.2 avg | 5 avg  |
| Support response time      | Improves satisfaction| Support    | 4h      | <2h    |

### Counter-Metrics

| Metric                    | Protects Against                    |
|---------------------------|-------------------------------------|
| Support tickets per active team | Over-optimizing WAT at expense of quality |

Adding Counter-Metrics

To generate suggested counter-metrics for a marketplace product:

north-star-metric "Define NSM for a marketplace connecting freelancers with clients"

This invocation returns the NSM definition plus recommended counter-metrics such as "dispute rate per transaction" or "time to first match," preventing the team from optimizing for transaction volume at the expense of user experience.

Summary

• A North Star Metric is a single, customer-centric KPI that passes seven validation criteria (easy to understand, customer-centric, sustainable value, vision alignment, quantitative, actionable, and leading indicator) as defined in pm-marketing-growth/skills/north-star-metric/SKILL.md.
• Classify your business into Attention, Transaction, or Productivity games to determine the appropriate metric shape.
• Support your NSM with 3-5 input metrics that are easier to move, causally connected, and MECE (mutually exclusive, collectively exhaustive).
• Use the /north-star command from pm-marketing-growth/commands/north-star.md to generate interactive workflows and markdown documentation templates.
• Protect against metric gaming by implementing counter-metrics and re-evaluating the framework annually or upon business model changes.

Frequently Asked Questions

What is the difference between a North Star Metric and a KPI?

A KPI measures business performance, often focusing on revenue or efficiency, while a North Star Metric specifically measures customer value delivery and acts as a leading indicator of future business success. According to the phuryn/pm-skills repository, an NSM must be customer-centric and satisfy seven validation criteria that standard KPIs often lack.

How many input metrics should support a North Star Metric?

The framework recommends 3-5 input metrics that are easier to move than the NSM itself, directly causal to the North Star, and MECE (mutually exclusive, collectively exhaustive). This constraint ensures focus while providing sufficient coverage to explain NSM movements through the product constellation.

Can revenue be a North Star Metric?

No, revenue is explicitly excluded from being a North Star Metric in the SKILL.md specification. While revenue is crucial for business survival, it is a lagging indicator rather than a leading one, and it reflects value captured rather than value delivered to customers. The NSM must predict future revenue through customer value creation.

How often should we re-evaluate our North Star Metric?

The repository recommends annual re-evaluation or immediate review when the business model changes significantly. Additionally, teams should run the validation table against the seven criteria quarterly to ensure the metric remains aligned with the company's vision and customer value proposition.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}