North Star Metrics in 2026: The Founder's Guide to Picking the Right One
Most teams pick a North Star that's easy to count and hard to act on. A practical framework for choosing a metric that drives real outcomes and reflects delivered value.
TL;DR
- Your North Star should represent delivered value, not activity — it measures the outcome users pay for
- Good North Stars are: outcome-based, measurable weekly, hard to fake, connected to revenue
- Avoid vanity metrics (signups, page views) — they don’t predict business health
- Pair North Star with supporting metrics: activation rate and retention
- You can (and should) change your North Star as you learn what value users actually pay for
- The metric should be sensitive to product improvements — if it doesn’t move when you ship, it’s wrong
What Is a North Star Metric?
A North Star metric is the single measure that best captures the core value your product delivers to customers.
North Star vs. Other Metrics
| Metric Type | Purpose | Example |
|---|---|---|
| North Star | Primary measure of delivered value | Weekly active customers completing [core action] |
| Input metrics | Things you can directly influence | Signups, feature adoption |
| Output metrics | Business results | Revenue, profit |
| Health metrics | System reliability | Uptime, error rates |
Why One Metric?
| Benefit | Explanation |
|---|---|
| Focus | Team knows what matters most |
| Alignment | Departments optimize together |
| Simplicity | Easy to communicate and remember |
| Accountability | Clear ownership and progress |
The Selection Criteria
A good North Star metric passes these tests:
Test 1: Outcome-Based
Ask: Does this measure value delivered, or just activity?
| Outcome-Based (Good) | Activity-Based (Bad) |
|---|---|
| Workflows completed | Logins |
| Revenue generated for customer | Time in app |
| Problems solved | Features used |
| Transactions processed | Page views |
Test 2: Measurable Weekly
Ask: Can we see meaningful movement every 1-2 weeks?
| Weekly-Measurable (Good) | Too Slow (Bad) |
|---|---|
| Weekly active users | Annual contract value |
| Completed workflows/week | Lifetime value |
| Transactions/week | Yearly retention |
If your metric only shows signal quarterly, you can’t iterate fast enough.
Test 3: Hard to Fake
Ask: Could we game this without actually improving the product?
| Hard to Fake (Good) | Easily Gamed (Bad) |
|---|---|
| Revenue from returning customers | Total signups |
| Completed transactions | Sessions started |
| Net Promoter Score | Email opens |
| Successful outcomes | Features clicked |
Test 4: Connected to Revenue
Ask: If this metric goes up, does revenue follow?
The North Star should be a leading indicator of business health. If the metric improves but revenue doesn’t follow, you’re measuring the wrong thing.
Test 5: Sensitive to Product Improvements
Ask: When we ship something good, does this metric move?
If your metric is too stable, you can’t tell if your work matters. It should respond to meaningful product changes within 2-4 weeks.
The Metric Hierarchy
Your North Star sits atop a hierarchy of supporting metrics.
The Three-Layer Model
North Star Metric
(Delivered value)
↓
Supporting Metrics
(Activation, Retention, Engagement)
↓
Input Metrics
(Things you can change weekly)
Layer 1: North Star
The outcome that matters most. One metric.
Layer 2: Supporting Metrics
| Metric | Role |
|---|---|
| Activation rate | Are new users getting value? |
| Retention | Are users coming back? |
| Engagement frequency | How often do users get value? |
These diagnose North Star movement. If North Star drops, which supporting metric explains it?
Layer 3: Input Metrics
Things you can directly influence:
| Input Metric | How It Feeds Supporting Metrics |
|---|---|
| Onboarding completion | → Activation |
| Feature discovery | → Engagement |
| Email open rate | → Retention |
| Load time | → Activation + Engagement |
North Star Examples by Product Type
SaaS Products
| Product Type | North Star | Why |
|---|---|---|
| Project management | Weekly active projects with activity | Active projects = value delivered |
| CRM | Deals progressed/week | Pipeline movement = sales value |
| Analytics | Reports viewed/week | Reports = insights delivered |
| Developer tools | Successful builds/week | Builds = development enabled |
Marketplaces
| Product Type | North Star | Why |
|---|---|---|
| E-commerce | Transactions completed | Purchases = marketplace value |
| Ride-sharing | Rides completed | Rides = transportation delivered |
| Freelance | Projects delivered | Delivery = work enabled |
Consumer Products
| Product Type | North Star | Why |
|---|---|---|
| Social | Content shared | Sharing = connection enabled |
| Entertainment | Hours watched | Watching = entertainment delivered |
| Fitness | Workouts completed | Workouts = fitness progress |
AI Products
| Product Type | North Star | Why |
|---|---|---|
| AI assistant | Tasks successfully completed | Completions = work done |
| Content generation | Outputs used | Usage = value delivered |
| Automation | Workflows processed | Processing = time saved |
Common Mistakes
Mistake 1: Vanity Metrics
| Vanity Metric | Why It Fails | Better Alternative |
|---|---|---|
| Total signups | Dead accounts count | Activated users |
| Page views | Doesn’t indicate value | Workflows completed |
| Downloads | May never open app | Weekly active users |
| Registered users | May have churned | Monthly active paying |
Mistake 2: Output Instead of Leading Indicator
| Output Metric | Why It’s Too Late | Leading Alternative |
|---|---|---|
| Revenue | Lags by months | Active customers |
| Churn rate | Already lost them | Engagement decline |
| LTV | Takes forever to measure | Activation rate |
Mistake 3: Composite Metrics
| Composite | Why It’s Confusing | Simpler Alternative |
|---|---|---|
| ”Health score” | Which component moved? | One primary metric |
| ”Engagement index” | Hard to act on | Specific behavior count |
Mistake 4: Wrong Granularity
| Too Broad | Why It’s Weak | Right Size |
|---|---|---|
| ”Users” | Includes inactive | ”Weekly active users doing X" |
| "Revenue” | Includes one-time | ”Recurring revenue” |
How to Find Your North Star
Step 1: Define the Core Value
Ask: What does a customer pay for? What outcome do they expect?
| Product | Core Value |
|---|---|
| Slack | Team communication |
| Stripe | Payments processed |
| Figma | Designs created |
| Notion | Knowledge organized |
Step 2: Identify the Key Action
Ask: What action represents delivering that value?
| Core Value | Key Action |
|---|---|
| Team communication | Messages sent in channels |
| Payments processed | Successful transactions |
| Designs created | Files with collaborators |
| Knowledge organized | Docs created and shared |
Step 3: Add Time Qualifier
Weekly or monthly frequency:
| Key Action | North Star |
|---|---|
| Messages sent | Weekly teams with 2+ users messaging |
| Successful transactions | Weekly transaction volume |
| Files with collaborators | Weekly shared design sessions |
| Docs created | Weekly docs with team edits |
Step 4: Validate
Check against criteria:
- Outcome-based?
- Measurable weekly?
- Hard to fake?
- Connected to revenue?
- Sensitive to improvements?
Operationalizing Your North Star
Make It Visible
| Practice | Implementation |
|---|---|
| Dashboard | North Star on main screen |
| Weekly email | Trend to all hands |
| Meeting opener | Start standup with metric |
| Slack channel | Automated daily update |
Review Cadence
| Frequency | Focus |
|---|---|
| Daily | Anomaly detection |
| Weekly | Trend analysis |
| Monthly | Deep dive |
| Quarterly | Strategy review |
Connecting to Work
Every initiative should answer: “How does this improve the North Star?”
| Initiative | North Star Connection |
|---|---|
| New feature | +5% activation → +2% North Star |
| Performance fix | -50% load time → +1% engagement → +0.5% North Star |
| Pricing change | +10% upgrades → +3% paying customers |
When to Change Your North Star
Your North Star should evolve as you learn.
Valid Reasons to Change
| Trigger | Example |
|---|---|
| Product-market fit shift | Discovered users value different outcome |
| Business model change | Moved from usage to subscription |
| Stage evolution | From growth to retention focus |
| Segment clarification | Learned who your real customers are |
How to Change
- Identify the new candidate based on what you’ve learned
- Run both metrics in parallel for 4-8 weeks
- Validate new metric predicts revenue better
- Communicate the change with rationale
- Update dashboards and goals
When NOT to Change
| Bad Reason | Why It’s Wrong |
|---|---|
| Metric isn’t moving | Fix the product, not the metric |
| Hard to improve | That’s the point — it requires real work |
| Looks bad | Changing to hide problems doesn’t help |
| Someone suggested something else | Needs rigorous validation |
Supporting Metrics Deep Dive
Activation
Definition: The moment a new user first experiences your core value.
| Product | Activation Event |
|---|---|
| Slack | Sent first message in a channel |
| Dropbox | Uploaded file from 2nd device |
| Zoom | Completed first call with 2+ participants |
Why it matters: Activation predicts retention. Users who activate stick around.
Retention
Definition: Users coming back to get value repeatedly.
| Retention Type | Measurement |
|---|---|
| Day 1 | % who return next day |
| Day 7 | % who return in week 2 |
| Day 30 | % who return in month 2 |
| Week-over-week | % active this week who were active last week |
Why it matters: Retention compounds. 1% improvement in weekly retention dramatically affects long-term metrics.
Engagement Frequency
Definition: How often users get value.
| Low Frequency | High Frequency |
|---|---|
| Monthly tax software | Daily messaging |
| Annual insurance | Weekly project management |
Match expectations to your product’s natural frequency.
Implementation Checklist
Defining:
- Identify core value delivered
- Find key action that represents value
- Add time qualifier (weekly/monthly)
- Validate against five criteria
Operationalizing:
- Build tracking instrumentation
- Create primary dashboard
- Set up weekly reporting
- Connect to initiative planning
Supporting:
- Define activation metric
- Set up retention cohorts
- Identify input metrics
- Create diagnostic dashboard
Maintaining:
- Schedule quarterly reviews
- Document change criteria
- Track correlation with revenue
FAQ
Can I change my North Star?
Yes. Change when you learn what value users actually pay for. But change deliberately with validation, not because the current metric is hard to improve.
What if my North Star has multiple components?
Pick the most important one as THE North Star. Others become supporting metrics. Composite metrics confuse more than they clarify.
How do I get the team aligned?
- Explain why this metric matters
- Show how it connects to revenue
- Make it visible everywhere
- Tie initiatives to metric impact
- Celebrate metric improvements
What if my product has multiple user types?
| Option | When to Use |
|---|---|
| Unified metric | One outcome serves all users |
| Segment metrics | Different value for different users (temporary) |
| Primary segment | Focus on most valuable segment |
How do I know if my North Star is working?
| Signal | Meaning |
|---|---|
| Metric moves when you ship | Sensitive to improvements ✓ |
| Revenue follows metric | Connected to business ✓ |
| Team knows the number | Visible and understood ✓ |
| Initiatives tie to it | Driving decisions ✓ |
Sources & Further Reading
Interested in our research?
We share our work openly. If you'd like to collaborate or discuss ideas — we'd love to hear from you.
Get in Touch