Files
pm-claude-skills/examples/samples/okr-builder.md
T
2026-06-19 09:31:45 +00:00

5.4 KiB
Raw Permalink Blame History

skill, title, input, source
skill title input source
okr-builder Okr Builder Company objective: become the default analytics tool for startups. For the product team, next quarter. We care about activation, retention, and word-of-mouth growth. generated by claude-sonnet-4-6

Q2 2025 OKRs — Product Team

North Star assumed from context: Startups that reach "activated" status and stay retained long enough to refer others. All OKRs ladder to becoming the default analytics tool for startups.


Objective 1: Make the first hour with our product undeniably valuable for every new startup

Why this matters: Startups evaluate tools fast and ruthlessly. If we don't deliver a clear "aha moment" in the first session, we lose them before retention is even possible — and word-of-mouth never starts.

# Key Result Baseline Target Measurement Method
KR1 New user activation rate (reaching "aha moment" milestone) increases Baseline needed ⚠️ +25pp above baseline Product analytics event tracking
KR2 Percentage of new signups who complete a meaningful analysis within their first session Baseline needed ⚠️ 55% of new signups Session-level event funnel
KR3 Time-to-first-insight for new users decreases Baseline needed ⚠️ Reduce by 40% Median time from signup to first chart/report event

Owner: Head of Product / Onboarding Squad Check-in cadence: Weekly


Objective 2: Turn activated users into loyal, long-term users who build workflows around us

Why this matters: Activation without retention is a leaky bucket. For startups to call us their "default" tool, using us needs to become habitual — not occasional.

# Key Result Baseline Target Measurement Method
KR1 30-day retention for activated users increases Baseline needed ⚠️ 45% 30-day retention Cohort retention report
KR2 Weekly active usage rate among retained users (using product 3+ days/week) increases Baseline needed ⚠️ 35% of retained users DAU/WAU ratio in product analytics
KR3 Involuntary churn due to friction (support-flagged product issues) decreases Baseline needed ⚠️ Reduce by 30% Support ticket tagging + churn reason attribution

Owner: Head of Product / Retention Squad Check-in cadence: Weekly


Objective 3: Make our users the engine of our growth in the startup ecosystem

Why this matters: The fastest path to becoming the default analytics tool for startups is peer recommendation — founders trust other founders more than any marketing channel. We need to engineer the conditions for word-of-mouth, not hope it happens.

# Key Result Baseline Target Measurement Method
KR1 Net Promoter Score among activated startup users increases Baseline needed ⚠️ NPS reaches 45+ Quarterly NPS survey (Delighted or equivalent)
KR2 Percentage of new signups attributing discovery to peer referral or word-of-mouth increases Baseline needed ⚠️ 30% of new signups Attribution survey at signup
KR3 Number of startups that share a public link, embed, or export created from our product Baseline needed ⚠️ 20% of activated users share at least once Share/export event tracking

Owner: Head of Product / Growth Squad Check-in cadence: Weekly


⚠️ Health Check — Baseline Data Gaps

Every KR above is flagged because no baselines were provided. Before this OKR set is finalized, the team must pull current-state numbers for each metric. OKRs without baselines cannot be scored at quarter end.

Recommended action before Q2 kickoff:

KR Data Source to Pull Baseline From
Activation rate Product analytics (Mixpanel, Amplitude, or equivalent)
First-session analysis completion Event funnel in product analytics tool
Time-to-first-insight Median time between signup event and first output event
30-day retention Cohort table in product analytics
Weekly active usage rate DAU/WAU calculation
Involuntary churn (friction) Support ticket audit, last 60 days
NPS Run a one-time survey this week if no historical data exists
Word-of-mouth attribution Add attribution question to signup flow immediately
Public share rate Instrument share/export events if not already tracked

Anti-Pattern Audit

Before submitting these OKRs, confirm none of the following slipped through:

  • No output-based KRs — none of these say "launch X" or "ship Y"
  • No binary KRs — every KR is scorable on a 0.01.0 scale
  • No vanity metrics — downloads, pageviews, and raw signups intentionally excluded
  • Baselines flagged — all gaps explicitly called out above
  • Max 3 KRs per objective — all objectives within limit
  • Connected to North Star — all three objectives ladder to "default analytics tool for startups"

Scoring Guide

At the end of Q2, score each KR from 0.0 to 1.0:

Score Meaning
0.71.0 Excellent. 0.7 is the sweet spot — if every KR scores 1.0, targets weren't ambitious enough
0.40.6 Progress made, but missed the target — understand why
0.00.3 Missed — hold a retrospective before setting Q3 OKRs

Reminder: These OKRs are not a performance review. A team that scores 0.7 across the board has had a great quarter. Hitting 1.0 on everything means next quarter's targets need to be harder.