02 - North Star And KPI Framework

North Star Metric (NSM)

  • NSM name: Learners On-Track After 8 Weeks (LOT8)

  • Why this reflects delivered customer value: Families buy for visible progress and confidence gains within a practical timeframe.

  • Formula: Count of paid learners with >=75% attendance and positive reading growth signal by week 8.

Industry Context: Choosing a North Star Metric

Duolingo initially tracked lessons completed as their primary success metric. It failed as a north star because it did not predict 6-month retention — a user could complete many lessons during a free trial and then disappear. They switched to DAU/MAU ratio, which forced every product decision to answer a sharper question: does this bring people back tomorrow, not just today?

Khan Academy made an analogous choice. They measure minutes of active learning per student per day instead of content-completion rate because completion measures breadth, not depth. A student who repeats a session three times to mastery should score higher than one who skips through it once. The metric they chose captured what the learning outcome actually required.

Airbnb settled on nights booked — not revenue, not listings created — as their north star. The reasoning: nights booked is the value exchange the marketplace creates, and it remains a meaningful signal before and after the company is monetized. Tracking revenue too early would have optimized for price rather than match quality.

ABC’s north star, Learners On-Track After 8 Weeks (LOT8), follows the same logic. It is a behavior metric, not a revenue metric, because habit formation and visible progress must be established before subscription retention can be managed. A family does not renew because the product charged them — they renew because the child improved.

Visual Dashboard (Agile + PMBOK)

LOT8 Ramp Chart (PMBOK Performance Baseline)

Alert line Baseline Q+1 Q+2 120 350 LOT8 0

Agile release planning view with PMBOK-style threshold control: the red dashed line marks the minimum acceptable outcome trajectory before corrective action is triggered.

KPI Domain Balance (Control Dashboard Mix)

Growth Activation Retention Reliability Economics 31% 29% 33% 28% 30%

A balanced PM scorecard prevents local optimization. This chart keeps Agile sprint delivery tied to PMBOK control domains (scope, schedule, quality, risk, and value).

KPI Tree

Growth

  • Visitor to free-session booking: 12-month target >=8%.

  • Free-session to paid conversion: 12-month target >=30%.

  • Customer acquisition cost (CAC): 12-month target <=$450 per enrolled learner.

Activation

  • Time to first value: <=72 hours from enrollment to first paid session.

  • Activation completion rate: >=85% of new learners complete first 2 weeks at >=75% attendance.

  • Onboarding drop-off points: booking completion, payment step, first tutor match acceptance.

Retention And Expansion

  • Gross revenue retention (GRR): >=88% by first annualized cohort.

  • Net revenue retention (NRR): >=102% by end of year 1.

  • Expansion monthly recurring revenue: >=$20,000 by Q1 2027 (upgrades, longer-term plans, group add-ons).

Product Reliability

  • Service availability (SLO): 99.9% monthly.

  • P95 latency: <=400 ms for learner and tutor workflow interactions.

  • Incident rate and MTTR: <=2 Sev-2 incidents/quarter, MTTR <=45 minutes.

Unit Economics

  • ARR: $1,200,000 by Q1 2027 run rate.

  • Gross margin: >=65%.

  • CAC payback period: <=6 months.

Baselines And Targets

KPI

Baseline

Q+1 Target

Q+2 Target

Alert Threshold

Owner

LOT8 (count learners on-track by week 8)

0

120

350

<70% of target for 2 weeks

PM

Free-session booking rate

0%

6%

8%

<5%

Growth

Free-session to paid conversion

0%

25%

30%

<20%

Growth

Time to first paid session (hours, median)

N/A

<=96

<=72

>120

Ops

Attendance adherence (%)

0%

70%

75%

<65%

Student Success

Tutor continuity (%)

0%

80%

85%

<75%

Tutor Ops

Month-3 retention (%)

N/A

70%

75%

<65%

Success

Availability (monthly)

N/A

99.7%

99.9%

<99.5%

Engineering

P95 latency

N/A

<=500 ms

<=400 ms

>550 ms

Engineering

Tooling Examples For KPI Governance

  • Azure DevOps Dashboards: pin LOT8, booking conversion, attendance, and retention widgets with alert-state coloring for threshold breaches.

  • Jira + Atlassian Analytics: build a KPI scorecard view and auto-open follow-up issues when alert thresholds are missed for two consecutive weeks.

  • GitHub Actions + Issues: run scheduled KPI threshold checks from warehouse exports and open owner-tagged issues for corrective action.

  • Jama Connect / IBM DOORS Next: store KPI-linked requirement baselines at each gate to preserve metric-definition consistency across releases.

Data Instrumentation Requirements

  • Event taxonomy approved: Required before MVP pilot start.

  • Critical events tracked end to end: free_session_booked, intake_completed, payment_success, tutor_match_confirmed, session_started, session_completed, attendance_missed, weekly_progress_shared, plan_upgraded, plan_cancelled.

  • Dashboard owner assigned: Product Ops lead.

  • Metric definitions documented: Single source of truth in analytics dictionary with monthly audit.

Governance

  • Weekly KPI review in product leadership.

  • Monthly KPI reconciliation with Finance.

  • Quarterly KPI resets linked to roadmap outcomes.

  • Any KPI below alert threshold for 2 consecutive weeks triggers a corrective action owner and recovery plan.