Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Frameworks

North Star Metric and OKRs

North star metrics and OKRs explained for marketing: choosing a north star and its inputs, writing objectives and key results, and cadence and scoring.
Frameworkbeginner9 min readUpdated

What a north star metric is

A north star metric is a count of value delivered, chosen so that when it rises the business is doing better for its customers and, with a lag, for itself. It is not revenue. Revenue is the consequence of value and arrives after it; a north star is chosen to lead revenue, so that a team watching it sees trouble or progress earlier than the finance report does. The kinds of metric that serve are counts of a core action completed: orders delivered, nights stayed, documents signed, teams that used the product this week.

The term is widely used across product and growth teams and no single origin is claimed for it here. What is claimed is the function. A north star gives every team the same answer to "what are we trying to move", which is the question that otherwise produces a dozen dashboards and no shared direction. The growth fundamentals hub places it at the centre of how growth teams organise their work.

What the metric makes visible is whether growth is real. Traffic, sign-ups and followers can all rise while the number of customers receiving value stays flat, and a north star exposes that gap immediately. What it hides is everything outside its definition: margin, cost of delivery, customer quality, and the long-term value (LTV) of the customers being counted. A north star is a focusing device, not a complete account of the business, and it needs guardrails beside it for the things it cannot see.

Choosing it and its inputs

The criteria below are tests, not a scoring sheet; a candidate metric that fails any of them is the wrong north star.

CriterionThe testPassesFails
Reflects customer valueDoes the number rise only when a customer got what they came for?Completed bookings; active teamsRegistrations; app opens
Leads revenueDoes it move before revenue does, in the same direction?Weekly active paying accountsMonthly revenue itself
Measurable nowCan it be counted today from existing data, by cohort?An event already trackedA survey score collected quarterly
Movable by teamsCan product, marketing and service each name an input they control?Orders deliveredShare price
Hard to gameCan it be inflated without creating value?Repeat usage of the core featureTime on site

Once chosen, the north star is decomposed into inputs: the handful of metrics that mathematically or causally feed it. The usual shape is breadth (how many customers), depth (how much each uses), frequency (how often) and efficiency (how quickly a new customer reaches value). Marketing's inputs sit mostly in breadth and efficiency: qualified new customers by channel, the activation rate of the people it brings, the conversion rate (CVR) of the journeys it owns. The decomposition is a tree, and the KPI tree framework covers the arithmetic between the levels; the KPI trees guide covers building one. The objectives and KPIs guide covers the chain from business goal to metric that the north star sits at the top of. A two-sided marketplace needs inputs from both sides beneath its north star, and the guide to measurement for marketplaces decomposes them into a KPI tree with the matched transaction as the shared outcome.

Writing OKRs

An OKR pairs an objective, a qualitative statement of what the team intends to achieve, with a few key results that say how anyone will know. Google's re:Work guide to setting goals with OKRs, the source cited on this page, describes objectives as ambitious and concrete, and key results as measurable and verifiable, so that at the end of the cycle a key result is either met or not with no room for argument. It also advises keeping the number of objectives and key results per team small and making them visible across the organisation.

For a marketing team, three rules follow. First, every objective should connect to a north star input: an objective about brand awareness that no input can be traced to is a wish. Second, key results are outcomes, not activities. "Launch the referral programme" is a task; "new customers from referral reach a stated share of the total" is a key result. The distinction is the one that keeps OKRs from becoming a project plan with a different heading. Third, each key result names its data source and its baseline at the moment it is written, so that the end-of-cycle grade is a reading rather than a negotiation.

Objectives are set per cycle, usually a quarter, inside the frame the annual planning guide describes: the annual plan fixes the north star and the year's priorities, and each quarter's OKRs are the slice of that plan the team commits to next. A team that writes OKRs without an annual frame tends to chase whatever was most visible in the last review.

Cadence and scoring

The cycle has three rhythms. Weekly, each key result is updated with its current reading and a confidence note, so that a result drifting off course is seen in week three rather than week twelve. Mid-cycle, the team checks whether any key result has become irrelevant because something changed, and either keeps it, rewrites it with the change noted, or drops it openly. At the end, each key result is graded.

The re:Work guide recommends grading on a simple scale from nothing achieved to fully achieved, and it makes the point that a team which consistently grades its key results in full has probably set them too low; ambitious key results are expected to fall short of full achievement some of the time. The guide treats grades as a learning tool, which is the reason to keep them separate from individual appraisal: a team whose pay depends on the grade will write safe key results, and safe key results teach nothing. When a team's key results are turned into objectives for each person, the tutorial on setting objectives for each marketer from the team plan keeps the same separation and writes anything one person cannot move alone as a shared result with named co-owners.

A practical refinement is to mark each key result as committed or aspirational when it is written. Committed results are expected in full and a miss triggers a review of what went wrong; aspirational results stretch the team and a partial grade is normal. Mixing the two without labelling them makes every grade ambiguous.

Worked set

Illustrative example — not a real result

A north star and one quarter of marketing OKRs for a staff-scheduling tool

A software company sells rota-planning tools to hospitality businesses. North star: weekly active scheduling teams, defined as teams that publish at least one rota in the week, currently 4,200. Inputs: new teams activated per week (120), trial-to-activation rate (38%), 12-week team retention (71%) and teams per account (1.6). Marketing owns the first two.

Objective for the quarter: make the trial the obvious next step for hospitality managers who find the product through search. Key results: (1) trials started from organic search rise from 310 to 450 a week; (2) trial-to-activation for search-sourced trials rises from 38% to 45%; (3) 60% of search-sourced trials arrive through the three cluster pages built this quarter, from a baseline of 22%.

End-of-quarter grades: KR1 reached 410 a week, graded 0.7. KR2 reached 41%, graded 0.4, with a note that the onboarding change shipped in week nine. KR3 reached 62%, graded 1.0 and flagged as set too low. The objective averages 0.7. The north star closed the quarter at 4,610 active teams, and the input the team moved most was activated teams per week, up from 120 to 141.

The set shows the shape: one objective, three key results that are readings rather than tasks, baselines recorded, grades that are honest about a late delivery and about a target that was too easy. It also shows the lag. The north star moved, but part of that movement came from retention, which marketing did not own.

Limits

A single metric invites tunnel vision. Teams optimise what is watched, and a north star watched hard enough will be moved in ways that do not create value: activation events triggered artificially, discounts that pull forward usage, acquisition of customers who inflate the count and churn. Guardrails, on cost, quality and retention, exist to catch this, and the framework does not supply them on its own. Where the north star keeps climbing while revenue stays flat, the guide to changing a north star metric helps decide whether the counting rule, an input or the metric itself has failed, and what to re-base if it is replaced.

The lag between marketing's work and the north star is real and often long. A quarter's OKRs may move an input cleanly while the north star barely responds, because retention or product changes dominate. The honest response is to grade the key results on the inputs and report the north star separately, rather than claiming or denying credit for the top-line movement.

OKRs degrade into task lists under pressure. The signs are key results phrased as deliverables, more key results than anyone can recite, and grades of full achievement across the board. Each is a sign that the process has become reporting rather than commitment. Keeping ongoing health measures in a separate KPI set helps, and the comparison of OKRs and KPIs shows where each kind of number belongs and how a KPI becomes a key result.

Marketing rarely controls its inputs alone. Activation depends on product, retention on service, and a marketing team graded on a shared input without influence over the other owners will either argue about attribution or quietly pick inputs it fully controls, which are usually the least important ones. Naming the shared ownership on the OKR itself is the only workable fix.

Finally, the re:Work guidance describes practice at a very large organisation. Small teams adapt it by shortening the cycle, keeping to one objective, and skipping the mid-cycle review when nothing has changed.

FrameworkReach for it when
KPI treeThe north star needs decomposing into the inputs each team owns
Measurement planThe inputs and key results need event definitions and a tracking specification
AARRRA product business needs its lifecycle stages defined before choosing which one is the north star
Experimentation loopA key result is to be moved through a sequence of tests rather than one initiative

When leadership asks for installs, the north star and OKRs for app installs shows how to keep install volume as a key result beside activation rather than as the north star.

Common mistakes

  • Revenue as the north star. It lags value and tells no team what to do differently this week.
  • Key results that are tasks. Shipping a campaign is work; the metric it was meant to move is the result.
  • No baseline at the time of writing. A key result without its starting reading is graded by memory.
  • Too many objectives. Priorities that cannot be recited are not priorities.
  • Grading tied to pay. It produces safe targets and full marks, and removes the information the grade was for.
  • Ignoring shared ownership. An input marketing cannot move alone needs its co-owner named on the OKR.
  • Changing the north star every cycle. A metric that moves with the planning calendar cannot show a trend, and teams stop trusting it.

Frequently asked questions

Is a north star metric the same as a KPI?

A KPI is any metric tied to an objective, and a business has many. The north star is one specific KPI chosen to represent customer value for the whole organisation, with the other KPIs arranged beneath it as inputs. Every north star is a KPI; most KPIs are not the north star.

Should marketing have its own north star?

Usually not, because the point of a north star is that every team shares it. Marketing instead owns the input metrics it can move, such as qualified new customers or activation from a given channel, and writes its OKRs against those. A marketing-only north star tends to drift back towards traffic or leads, which measure marketing activity rather than customer value.

How many OKRs should a marketing team run at once?

Few enough that each is reviewed every week and someone can recite them without looking. A team running a long list has written a task plan and labelled it OKRs. When everything is a priority, the framework no longer tells anyone what to drop.

Terms used on this page

Applied to an objective

Where this page is used

Part of these learning paths

Also related

Sources

  1. Guide: Set goals with OKRs — Google re:Work

Related