Needs more than a quick edit8 of 11 checks passed
The unsupported causal claims (e.g., about gamification and budget cut causes) would need verification or rewriting before a PM could use it without re-checking evidence or reasoning.
Output
MEMO To: Grace Mensah, CPO From: Staff PM Date: Start of Q4 Subject: Q3 OKR Post-Mortem and Proposed Q4 Product OKRs
1. What Q3’s OKRs Actually Tell Us
At the all-hands, we celebrated a 0.81 average OKR score while the company failed its only two goals: Net Revenue Retention (NRR) dropped from 103% to 102% (target: 108%), and logo churn rose from 3.1% to 3.4% (target: 2.5%).
We achieved high team scores while losing customers because our OKR system rewards shipping features over changing customer behavior.
Outputs disguised as outcomes inflated our score. Ten of our 16 KRs were binary tasks (shipping features, running experiments, closing bugs). The Admin team even mislabeled "Launch 3 HRIS integrations" as an outcome. All 10 output KRs scored 1.00. If we strip out outputs and look only at true outcomes, our average score drops to 0.48. If we further remove technical uptime, the score for customer-behavior outcomes is 0.38.
The commercial outcomes we actually needed to move went backward. * Learner Engagement (0.00): Weekly active learners per seat (WAL/seat) fell from 0.31 to 0.29. Over 70% of paid seats sit unused each week. * Onboarding Speed (0.15): Days from contract to first learner barely budged from 34 to 31 days (target: 14). * Account Expansion (0.00): Seats added in existing accounts fell from 9,200 to 8,100 (target: 14,000).
Our three outcome wins were disconnected from retention: 1. Course completion rate (41% to 58%, score 1.00): This was largely a mirage. On August 1, we lowered the definition of "complete" from 100% of modules finished to 80% to match our certificate rule. We moved the goalposts mid-quarter and claimed a win. 2. App store rating (4.2 to 4.5, score 0.75): A vanity metric. It takes a tiny fraction of happy users to rate an app, which masks the fact that overall weekly usage shrank. 3. Uptime (99.93%, score 1.00): Good hygiene from Platform, but high availability doesn’t stop churn if nobody logs in.
Our outputs failed to move the outcomes they sat next to. * Admin shipped 3 HRIS integrations, yet time-to-first-learner stayed stuck at a month. Shipping an integration means nothing if admins don't adopt it during onboarding. * Learner shipped offline mode, streaks, and badges, yet weekly active usage dropped. Gamification only engages users who are already active; it doesn't get dormant seats in the door. * Growth ran 13 experiments and shipped upgrade prompts, yet added fewer seats than in Q2. You cannot prompt an admin to buy more seats when 71% of the seats they already pay for are gathering dust.
The Root Cause of Q3 Churn Exit interviews from 38 churned accounts make the causal chain clear: * 45% left because "our people didn't use it" (17/38). Another 24% (9/38) cited budget cuts, and 18% (7/38) consolidated into their HR system’s bundled LMS—both of which happen when an L&D team cannot prove ROI on Pathwise usage. * Crucially, accounts that reached their first learner within 14 days churned at a third of the rate of the rest. Right now, our average account takes 31 days—meaning the majority of new cohorts start life in the high-churn danger zone.
---
2. How Q4 OKRs Add Up to the Company Goal
To hit 108% NRR and 2.5% logo churn, Product must fix the sequence of value creation for an annual seat-based business:
- Admin must compress onboarding under the 14-day threshold and get seats assigned, cutting early structural churn.
- Learner must turn assigned seats into active weekly learners—both to stop the #1 churn reason ("people didn't use it") and to eat up seat capacity.
- Growth must convert high seat utilization into mid-contract seat expansion and give L&D buyers the ROI proof they need to defend their budget at renewal.
---
3. Proposed Q4 OKRs (Learner, Admin, Growth)
Every KR below is a measurable customer behavior or business outcome. No roadmaps, features, or experiment counts are permitted on the scorecard.
#### Admin Team Role in Company OKR: Cut logo churn by getting accounts past the 14-day survival mark and driving seat provisioning.
Objective: Get every new account to fast, broad adoption. * KR 1: Reduce average days from contract signature to first learner from 31 days to 14 days. * KR 2: Increase the share of new accounts reaching their first active learner within 14 days from 28% (est. Q3 baseline) to 75%. (Note: Admin to confirm exact Q3 percentage in week 1). * KR 3: Increase average seat assignment rate (paid seats assigned to a named employee via HRIS or invite) within 30 days of contract from 52% (est. baseline) to 85%.
#### Learner App Team Role in Company OKR: Eliminate the #1 churn driver ("people didn't use it") by activating dormant seats and building a weekly learning habit.
Objective: Turn paid seats into weekly active learners. * KR 1: Increase Weekly Active Learners per paid seat (WAL/seat) from 0.29 to 0.42. * KR 2: Increase 30-day assigned-seat activation rate (share of newly assigned seats that start at least one course within 30 days) from 45% (est. baseline) to 70%. * KR 3: Increase course completion rate—held strictly to the constant 80%-module definition—from 58% to 68%.
#### Growth Team Role in Company OKR: Drive NRR from 102% to 108% by expanding capacity-constrained accounts and arming buyers to prevent renewal down-sell.
Objective: Expand high-usage accounts and lock in renewals. * KR 1: Increase quarterly seats added in existing accounts from 8,100 to 14,500 (sized to make up the Q3 shortfall and hit 108% NRR). * KR 2: Increase the quarterly seat-expansion conversion rate among "at-capacity" accounts (accounts with >80% of paid seats assigned and active) from 12% (est. baseline) to 28%. * KR 3: Reduce gross revenue contraction from seat reductions at renewal from 4.5% (est. Q3 baseline) to 2.0% of renewable ARR (e.g., by proving ROI via the new reporting dashboard before renewal conversations).
---
4. Guardrails for Q4 Execution
- Freeze the Metric Dictionary: No metric definition may change mid-quarter without CPO sign-off and a retroactive restatement of the baseline.
- Track Outputs in Sprint Reviews, Not OKRs: Shipping features, running 12 experiments, or launching integrations are how we try to move KRs. If an experiment ships and the metric doesn’t move, the score is 0.00—which tells us in week 4 to pivot our approach before the quarter is lost.
- Confirm Baselines by Friday: Where Q3 tracking didn't capture cohort rates (Admin KR2/KR3, Learner KR2, Growth KR2/KR3), Data and PM leads will pull exact Q3 actuals by Friday so our baselines are locked before Q4 kickoff.
Grades and run details
Decision model 77 · LLM judge 83
Decision model checks
- failUses the supplied evidence correctly76%
- failAddresses the actual decision20%
- passRespects explicit constraints28%
- passIdentifies material uncertainty54%
- partialAvoids unsupported claims43%
- passProduces the required deliverable74%
- passReads the scorecard for what it is100%
- passCatches the redefined key result98%
- passKey results are outcomes, not output97%
- passFocuses on the big rock49%
- passShows how the goals add up62%
Run
- Run
- #1
- API response time
- 22 s
- Submitted
- 13 Oct 2026