OKR Examples · 9 min read
Growth OKRs: Real Examples Across the Full Funnel
Growth teams have an advantage over most other functions when writing OKRs: everything they do is measurable. The challenge is the opposite — there are too many metrics, every experiment produces data, and it's easy to confuse "running experiments" with "driving growth." Good growth OKRs pick the right metric to move, set an ambitious but grounded target, and resist the temptation to measure the experiment count instead of the outcome.
Published May 2026 · OKIAR Editorial
Acquisition OKRs
KR1: Organic share of new user signups: 18% → 42%.
KR2: Referral-sourced signups: 0 → 340 in Q3 (first quarter with referral program live).
KR3: Paid CAC: $312 → under $180 (through better landing page conversion and targeting).
"Build acquisition channels that don't require ad spend" is a genuine strategic objective — it's not just "grow signups." It describes a change in the business model of acquisition that has long-term compounding effects. KR1, KR2, and KR3 all measure progress toward that specific goal, not just top-of-funnel volume.
Activation OKRs
KR1: Day-7 activation rate (users reaching "aha moment" milestone): 23% → 48%.
KR2: Users who invite ≥1 teammate within first 7 days: 4% → 17%.
KR3: In-product NPS at Day-7: 22 → 38.
Retention OKRs
KR1: Week-6 retention (cohort-based): 31% → 49%.
KR2: "Returning after dormancy" re-engagement rate: 6% → 18% (triggered by re-engagement campaign).
KR3: Users with ≥3 "power user" behaviors in first 30 days: 8% → 24%.
"Power user behaviors" needs to be defined in advance. The growth team should identify 2–4 specific in-product actions that highly retained users do in their first 30 days (using data from retained vs churned cohorts). Then the OKR measures whether new cohorts are hitting those behaviors — not whether they're "active" in a generic sense.
Referral and virality OKRs
KR1: Viral coefficient (invites sent per user × invite acceptance rate): 0.04 → 0.28.
KR2: % of new signups from referral: 3% → 19%.
KR3: "Invite teammate" as the action taken most often by users who invited ≥3 people: track and surface to product team.
Monetization OKRs
KR1: Free-to-paid conversion rate: 3.1% → 8.4%.
KR2: Average time from signup to first payment: 34 days → 19 days.
KR3: Revenue from self-serve upgrades (no sales involvement): $0 → $48k in Q3.
Experiment velocity OKRs
KR1: A/B tests shipped per month: 2.1 → 6.
KR2: Experiment cycle time (idea → result): 21 days → 9 days.
KR3: % of experiments with pre-registered hypothesis and success metric: 40% → 100%.
KR3 is the quality guardrail. Moving fast on experiments is valuable only if the experiments are valid. Pre-registering hypotheses prevents the p-hacking trap — where teams define success metrics after seeing results. If your experiment velocity doubles but you're running invalid experiments, you're moving faster toward wrong conclusions.
The north star vs OKR question
Growth teams often have a north star metric — the single number that reflects product value (weekly active users, transactions, messages sent). The north star is useful for alignment, but it's a poor OKR on its own because moving it requires moving multiple upstream metrics simultaneously.
The better approach: use the north star as the Objective (directionally), and write KRs for the specific levers you're pulling this quarter. If the north star is "weekly active users," your Q3 OKR might be "increase activation rate (the biggest lever we've identified) from 23% to 48%." The north star gives direction; the KR gives focus.
Run growth OKRs in Okiar — voice check-ins, AI projections, team health signals, free during beta.
Okiar is free during beta. Voice check-ins, AI projections, team health — live in minutes.
Start free →