Articles

A Single North Star vs. Value Creation KPIs

For a data-driven SaaS team, choosing one North-Star Metric (NSM) feels like strapping a compass to the product. But as your product matures, your needs get more complicated:

Products become modular.

  • Feature sets multiply: idea backlog, dependency mapping, capacity planning, AI suggestions, etc.
  • One metric rarely “lights up” every module with equal sensitivity.

Customers hire you for different Jobs-to-be-Done.

Nothing is more frustrating than trying to connect an add-on release, which might solve an important job for only 10% of the customer base, to an uptick in a global North Star metric. Even if the business case for your add-on is solid and it truly achieves cross-sell success, it might not move the North Star needle.

Specialized teams need clean feedback loops.

Onboarding, integrations, workflow analytics, billing: each squad wants to see its impact without waiting for an aggregate number to wiggle.

Under such pressures, an NSM might be directionally inspiring, yet not represent the complete picture. Great for board decks, unhelpful for roadmap prioritization, and definitely not reflecting all key jobs.

North Star example

Take a familiar SaaS most of us use: a product roadmapping tool. What might its north star be? Maybe:

Team Roadmap Views Published per Month

Great for overall adoption, and it measures the core value of the product. But what about the Feature Requests module? The strategic module with OKRs and business models? Could they achieve great things (including nice cross-sell monetization) without a significant uptick in this metric?

Enter the value-creation KPI set

Clayton Christensen’s The Innovator’s Solution explains that industries evolve from monolithic to modular once basic needs are over-served. Your measurement system should mirror that evolution.

For a modular, later-stage product roadmapping tool, a handful of metrics gives sharper, more actionable insight:

  • Activation rate: % of new accounts that create and publish their first roadmap within 7 days
  • Help in decision-making: average number of roadmap items linked to feature requests, or to goals and customer segments
  • Team roadmaps published per month: to still capture the core value
  • Integration penetration: % of active accounts with at least one two-way sync enabled (for instance, Jira)
  • Seat expansion velocity: net new paid seats per paying account per quarter, owned by teams who want to reach new personas for revenue expansion

Use several of these at any one time. The point is coverage, not a metrics zoo.

Here is a high-level explanation of what value creation is, in a simplified model.

Why several beat one in mature SaaS

Instant ownership loops. When decision-making help dips, the relevant squad knows it’s their fire drill.

Granularity without noise. You curate only the metrics that move enterprise value, surfacing issues before they escalate. This changes the entire strategic conversation in the PM team: does this new feature move the needle on the related KPI?

Organizational fit. A maturing SaaS is a system of systems; separate KPIs respect that design and highlight which module drives or drags value. Once you know how to measure value, what else can build on the same conclusions? Think of your Product Adoption Score (PAS), for instance.

Better storytelling. Execs hear a crisp narrative (“Activation is getting faster; Integration Penetration is flat”) instead of debating what one blended number means.

Pro tips for selecting KPIs

  • Make sure they don’t duplicate each other: measure one Job-to-be-Done with just one metric.
  • Go for coverage: don’t leave important jobs unmeasured.
  • Assign personal ownership: usually the product leaders in a larger organization, or individual PMs in smaller startups.
  • Decide whether to include overall growth (total customers or adoption) or to simplify by discounting it (averages), and apply the same rule everywhere. One is closer to a North Star for a module or squad; the other is more granular and tied tightly to the product.

For example,

% of new accounts that create and publish their first roadmap within 7 days

becomes

Total number of new accounts that create and publish their first roadmap within 7 days

The latter includes your ability to drive new business and makes it more relevant for the wider team and executives. It measures total value created for customers vs. the ability to create value.

TL;DR

  • Use an NSM for focus; use a KPI set for action.
  • 3–10 value-creation KPIs give each squad a lever it can actually pull.
  • Modular SaaS products demand modular measurement.
  • Tie each KPI to a Job-to-be-Done so the metric reflects real customer value, not internal vanity.
  • Know how you will react and break down further when each KPI goes up or down.
  • KPIs
  • North Star
  • Value Creation

Working through this in your own team? I help companies and individual PMs put these ideas into practice.

Book a call