The strategic compass

In Lesson 1, we established that a product cannot grow without a flat retention curve. But once you have that core group of loyal users, a new problem emerges: chaos.

In most growing companies, different departments pull in different directions:

• Marketing is obsessed with acquisition volume
• Sales is chasing quarterly revenue targets
• Product is focused on shipping new features
• Engineering is trying to pay down technical debt

On the surface, everyone is working hard. Underneath, the teams are working against each other. Marketing might be bringing in users who do not fit the product. Sales might be promising features that are not on the roadmap just to close a deal.

Without a shared definition of success, "winning" for one team often means "losing" for another. The North Star Framework solves this by giving everyone a single number to align around.

The North Star Metric (NSM) is not just another KPI. It is a way to manage a product by identifying a single metric that captures the core value your product delivers to customers.

To qualify as a North Star, a metric must meet three criteria:

1. It measures customer value: it captures the moment the customer gets what they came for
2. It represents product strategy: it reflects your unique approach to the market
3. It is a leading indicator of revenue: it does not track what you earned yesterday — it predicts what you will earn tomorrow

Why can't revenue be your North Star? Revenue is a lagging indicator. It tells you about the success of past decisions. If your revenue drops today, the damage was likely done months ago through poor retention or lack of product value.

You might ask: "If revenue pays the bills, why not just focus on that?" Because focusing on revenue encourages short-term fixes — more ads, worse contracts. The North Star ensures that when the business earns money, the customer is also getting value.

Now the question becomes: how do you find the right metric? The answer depends on what kind of product you are building.

Not all products provide value in the same way. Before choosing a metric, you need to understand which "game" your product is playing. The game determines what "engagement" means for your business.

Game 1: the Attention Game

• Goal: maximize the time users spend in your product
• Value exchange: entertainment or information
• Examples: Netflix, Facebook, TikTok

Game 2: the Transaction Game

• Goal: help customers make purchase decisions with confidence
• Value exchange: finding and buying the right item efficiently
• Examples: Amazon, eBay, Instacart

Game 3: the Productivity Game

• Goal: provide a reliable way to complete a task or workflow
• Value exchange: efficiency and "jobs done"
• Examples: Miro, Salesforce, Slack, Adobe Creative Cloud

Knowing which game you play narrows down the type of metric you need. But a single North Star is still too "big" for a team of engineers or marketers to influence directly. It needs to be broken down.

A North Star like "Total items received" (Instacart) is clear at the company level, but an engineer working on the search bar cannot move that number directly. To make the North Star actionable, it gets broken down into four input dimensions:

How many users are performing the action? This relates to acquisition and retention.

• Spotify example: number of premium subscribers

How much are they engaging? This measures the intensity of the value.

• Spotify example: number of hours spent listening per session

How often do they come back? This tracks the habit loop.

• Spotify example: number of sessions per user per week

How fast or successfully do they complete the action?

• Instacart example: percentage of orders delivered within the promised window

These four dimensions turn a single ambitious metric into something every squad can own. But how does this play out in practice? Consider how one of the companies that teaches this framework had to change its own metric.

Metrics are not set in stone. As a company's strategy evolves, its North Star must follow.

• Strategy: help analysts get answers faster than using SQL
• North Star: Total Weekly Queries
• The flaw: this did not measure if the queries were actually useful. An analyst could run 100 queries that no one else saw.

• Strategy: enable "data democracy" where everyone in a company uses data to make decisions
• North Star: Weekly Learning Users (WLU)
• Definition: the number of users who shared a chart or insight that was viewed by 2 or more people
• Why it works: it measures value (learning), strategy (sharing/democracy), and leads to revenue (sticky, organization-wide use)

The shift from "queries run" to "insights shared" changed how every team at Amplitude prioritized their work. The same principle applies to your organization: the metric shapes the behavior.

But even a well-chosen North Star is useless if teams cannot connect their daily work to it. That is where the hierarchy of bets comes in.

The framework connects your product roadmap directly to your metrics. Every feature and experiment maps to a specific level:

Example: improving "breadth" for a delivery app

• Input metric: number of users placing their first order
• Opportunity: high friction in the credit card entry screen
• Intervention: implement Apple Pay to reduce friction

What if your intervention moves a metric, but the North Star stays flat? This means one of two things: either the intervention was not big enough, or the link between that input and the North Star is weaker than you assumed. Both are useful signals.

So the framework makes sense in theory. How do you get a real team to adopt it?

You cannot announce a metric from the CEO's office and expect teams to follow it. The North Star works when teams help build it — because they understand the reasoning behind it.

Step-by-step workshop strategy:

1. Define the product vision: what is the measurable world you want to create? (e.g., "All the world's music in your pocket")
2. Identify the critical event: what is the one action that signifies value? Not a signup, but a "successful search" or "item received"
3. Draft candidate North Stars: use the three games to brainstorm options
4. Run the checklist test:
5. Does it represent value?
6. Is it actionable?
7. Is it easy to explain? (a "punchy" name matters)
8. Build the constellation: define the breadth, depth, and frequency metrics

Once the North Star is defined, a natural question follows: does this replace our existing OKR system?

A common question is: "Do North Stars replace OKRs?" The answer is no. They complement each other:

• NSM is the model: it defines how your product grows. It is stable for 1–3 years.
• OKRs are the engine: they define specific targets for the next 3 months to push the NSM inputs forward.

Think of it this way: the North Star is the destination on the map. The OKRs are the milestones you hit during the current quarter to ensure you are moving toward that destination.

The North Star Framework is not just about numbers — it is about alignment. It connects a developer's daily work to a customer's experience and, ultimately, to the company's revenue.

When teams share a decision-making compass, they do not need approval for every small move. They can act independently because they know what matters.

In Lesson 3, we will shift our focus from the "what" (metrics) to the "how" (psychology) — exploring the Hook Model in depth to understand how to design the product interactions that actually move these metrics.