Tasks / Metrics & Experimentation

Draft OKRs

Can the model turn a team's wish list into a few outcome-based OKRs that add up to the company's goals?

Task type v1.1 · 2 tasksLast changed 6 Oct 2026 · ChangelogDifficulty

What AI gets right here, and what you’ll still have to catch

From 18 graded outputs by 9 models. 50% were usable with at most a quick edit.

Reliably right

  1. Builds the key results on the data100% pass
    Key results 2 and 3 are built directly on the first-week joining data and time-to-shared-note data, with baselines from the brief and targets.
    GPT-6.1 Sol · API · Eleven key results and a bonus
  2. Respects explicit constraints99% pass
    The output is a memo to Grace Mensah, within the 1,100-word limit, and includes the requested diagnosis and team OKRs with baselines and targets.
    GPT-6 Astra · ChatGPT · A great quarter, on paper
  3. Produces the required deliverable99% pass
    The memo is complete, in the right form for the CPO, and a PM could act on it with only light edits.
    GPT-6 Astra · ChatGPT · A great quarter, on paper

Where it slips

  1. Flags the bonus link47% pass
    Mentions bonus multipliers only to justify outcome KRs; does not name the risk of safe targets or suggest decoupling OKR scores from bonuses.
    Haiku 5.5 · API · Eleven key results and a bonus
  2. Avoids unsupported claims67% pass
    Presents 'the gap is correlation' and 'the safe play is to pick easy KRs' as facts without labeling them as hypotheses.
    Sonnet 5.5 · API · Eleven key results and a bonus
  3. Identifies material uncertainty68% pass
    The output does not name any specific unknowns that could change the OKRs or how they would be resolved.
    GPT-6 Luna · API · Eleven key results and a bonus

How it’s graded

Each check is built on how world-class product and growth leaders do this work, as they’ve described it on Lenny’s Podcast, and names the leader it comes from.

  1. Key results are outcomes, not output

    Is every key result a measurable change in customer or business behaviour, rather than something the team will ship or do?

    Passes when Every key result names a metric with a baseline and a target; shipping work appears only as initiatives that serve them.

  2. Focuses on the big rock

    Does the output cut the goals down to the few that matter most, rather than covering everything the team could do?

    Passes when Few objectives, each with a small number of key results, and says what was dropped and why.

  3. Shows how the goals add up

    Does the output show how each team-level key result contributes to the company-level goals, and flag any that don't?

    Passes when Every key result is linked to a company goal, with the reasoning or data that connects them, and any that serve no company goal are flagged or cut.

Plus our standard checks

Uses the supplied evidence correctly · Addresses the actual decision · Respects explicit constraints · Identifies material uncertainty · Avoids unsupported claims · Produces the required deliverable · and 2 written for each task, which you’ll see in the tasks below.

The tasks

Read the brief, then compare up to three outputs, each with the LLM judge’s verdict on every check. Highlights mark what a PM had to fix.

The brief

You're a Staff PM at Pathwise, working for the CPO, Grace Mensah. Last quarter's OKR scorecard is below, along with the company goal it was meant to serve. Grace wants a memo of no more than 1,100 words: what last quarter's OKRs actually tell us (not just the scores), and next quarter's OKRs for the Learner app, Admin and Growth teams, each with baselines and targets, that add up to the company goal.\n\nThe files are attached.

What the model was given5 items: About Pathwise, company_okr_q3.md, okr_scorecard_q3.csv (team_label is the type each team gave its key result), metric_dictionary.md, churn_reasons_q3.md
About PathwiseOnline learning for companies: courses employees take, and tools for the HR and L&D teams who buy it. Sold per seat on annual contracts.
company_okr_q3.md7 lines · Download
# Company OKR, Q3 (set by the CEO)

Objective: grow by keeping and expanding the customers we have.
- Net revenue retention: from 103% to 108%. Actual: 102%.
- Quarterly logo churn: from 3.1% to 2.5%. Actual: 3.4%.

Q3 average key result score across product teams: 0.81. The all-hands slide said "a great quarter".
okr_scorecard_q3.csv (team_label is the type each team gave its key result)team,objective,key_result,team_label,baseline,target,actual,score Content,Best course library in L&D,Publish 40 new courses,output,0,40,41,1.00 Content,Best course library in L&D,Course completion rate,outcome,41,55,58,1.00 Content,Best course library in L&D,Translate top 20 courses into 3 languages,output,0,60,60,1.00 Learner app,Learning people love,Ship mobile offline mode,output,0,1,1,1.00 Learner app,Learning people love,Weekly active learners per seat,outcome,0.31,0.4,0.29,0.00 Learner app,Learning people love,Ship streaks and badges,output,0,1,1,1.00 Learner app,Learning people love,App store rating,outcome,4.2,4.6,4.5,0.75 Admin,Admins get value fast,Launch 3 HRIS integrations,outcome,0,3,3,1.00 Admin,Admins get value fast,Days from contract to first learner,outcome,34,14,31,0.15 Admin,Admins get value fast,Ship new reporting dashboard,output,0,1,1,1.00 Growth,Expand inside accounts,Seats added in existing accounts,outcome,9200,14000,8100,0.00 Growth,Expand inside accounts,Run 12 expansion experiments,output,0,12,13,1.00 Growth,Expand inside accounts,Launch in-app upgrade prompts,output,0,1,1,1.00 Platform,Reliable at scale,Uptime,outcome,99.5,99.9,99.93,1.00 Platform,Reliable at scale,Migrate to new video CDN,output,0,1,1,1.00 Platform,Reliable at scale,Close 150 bugs,output,0,150,162,1.00
metric_dictionary.md5 lines · Download
# Metric dictionary (excerpt)

- Course completion rate: share of course enrolments marked complete. Until 31 July "complete" meant every module finished. From 1 August it means 80% of modules finished (changed so completion matches the certificate rule).
- Weekly active learners per seat: learners who start or continue a course in a week, divided by paid seats.
- Days from contract to first learner: calendar days from contract signature to the first learner starting a course.
churn_reasons_q3.md8 lines · Download
# Why accounts left in Q3 (exit interviews, 38 accounts)

- "Our people didn't use it": 17
- Budget cut: 9
- Moved to the LMS that came with our HR system: 7
- Content didn't fit our industry: 5

…
What a strong answer doesThe answer key the graders mark against

Reads the scorecard for what it is: the average is 0.81, but every output key result scored 1.00 (things shipped) while outcome key results averaged about 0.48, and the company missed both goals (NRR 102% against 108%, churn 3.4% against 2.5%). Two scores flatter: 'Launch 3 HRIS integrations' is labelled an outcome but is output, and course completion only 'beat' its target because completion was redefined on 1 August (all modules to 80%), so the result can't be compared with its baseline. The outcome key results that matter for churn moved backwards or barely (weekly active learners per seat 0.31 to 0.29; days to first learner 34 to 31; seats added 8,100 against 9,200). Builds next quarter's OKRs on the churn evidence: low usage is the top exit reason, and accounts reaching a first learner within 14 days churn at a third of the rate. So Admin owns days from contract to first learner (from 31), Learner app owns weekly active learners per seat (from 0.29), Growth owns seats added in existing accounts or net expansion, each with a baseline from the files and a target, with shipping work as initiatives. Notes the completion metric needs restating on one definition before anyone uses it.

Critical failures (cap the score at 40)
  • Describes last quarter as a success on the strength of the 0.81 average
Task

Staff-level · v1.1

The outputs

9 setups answered this brief.

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:

  1. Admin must compress onboarding under the 14-day threshold and get seats assigned, cutting early structural churn.
  2. 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.
  3. 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

  1. Freeze the Metric Dictionary: No metric definition may change mid-quarter without CPO sign-off and a retroactive restatement of the baseline.
  2. 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.
  3. 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

Needs more than a quick edit7 of 11 checks passed

The proposed baselines for new metrics are unsupported, requiring the user to re-check evidence and source real data before using the OKRs.

Output

MEMORANDUM

TO: Grace Mensah, Chief Product Officer FROM: Staff Product Manager DATE: October 3, 2024 SUBJECT: Q3 OKR Post-Mortem & Proposed Q4 Product OKRs

*

1. The Disconnect: What Q3 OKRs Actually Tell Us

At our recent all-hands, a product OKR score of 0.81 was celebrated as a “great quarter.” In reality, Q3 was a business failure: * Net Revenue Retention (NRR) dropped from 103% to 102% (Target: 108%). * Quarterly Logo Churn rose from 3.1% to 3.4% (Target: 2.5%).

The 0.81 score is a vanity metric masking acute operational disconnects across four distinct areas:

``` [Output Orientation: 9/16 KRs] ──> Shipped features, missed business outcomes [Metric Manipulation] ──> Completion rate rose via relaxed definition (100% -> 80%) [Activation Breakdown] ──> 31 days to 1st learner (Goal: 14) fuels 45% of churn [Premature Expansion] ──> Pushed upgrade prompts while seat activity fell to 29% ```

#### A. Feature Delivery Was Confused with Value Creation Nine of our 16 Key Results were binary outputs (shipping features or running counts). Teams scored 1.0 on outputs—shipping offline mode, streaks, dashboards, upgrade prompts, and integrations—while customer-facing outcomes collapsed: * Learner App scored 1.0 on features, yet Weekly Active Learners per seat fell from 0.31 to 0.29 (Target: 0.40). * Growth scored 1.0 on experiments and upgrade prompts, yet Seats added in existing accounts fell from 9,200 to 8,100 (Target: 14,000). * Admin delivered 3 HRIS integrations (misclassified as an “outcome”), but the actual outcome—Days from contract to first learner—only improved from 34 to 31 days (Target: 14).

#### B. Vanity Gains and Metric Redefinition Content claimed a 1.0 score by driving Course Completion Rate from 41% to 58% (Target: 55%). However, this was largely engineered by lowering the completion threshold on August 1 from 100% of modules to 80%. Artificially inflating course completions obscured stagnant baseline learner demand.

#### C. Product Neglect Directly Fed Q3 Exit Drivers Our exit interviews across 38 churned accounts reveal direct causation with our product failures: 1. "Our people didn’t use it" (17 accounts / 45%): Directly caused by dropping learner engagement (0.29 weekly active learners per seat). Gamification (streaks/badges) failed to solve core utility. 2. "Moved to HR system’s LMS" (7 accounts / 18%): While we launched 3 HRIS integrations, we treated them as tick-box deliverables rather than driving customer activation. 3. Budget cuts (9 accounts / 24%): When CFOs review seat utilization below 30%, unused seats are cut at renewal. 4. Onboarding Lag: Accounts reaching first learner within 14 days churn at one-third the rate of slower accounts. By taking 31 days to activate, Admin is losing accounts before they even start.

---

2. Strategic Narrative for Q4

We cannot expand accounts that are not using the product. To move NRR to 106% and logo churn down to 2.6%, the product strategy must execute in strict sequence across the account lifecycle:

``` [Admin: Days 1–14] [Learner App: Days 15–365] [Growth: Renewal & Expansion] Compress onboarding to <14d ──> Drive habitual weekly usage ──> Monetize 80%+ utilized accounts (Reduces churn by 66%) (Eliminates "nobody used it") (Reverses NRR contraction) ```

  1. Admin (Time-to-Value): Compress onboarding to under 14 days using automated HRIS provisioning to unlock the 66% churn reduction.
  2. Learner App (Habitual Engagement): Drive weekly active learners per seat from 0.29 to 0.40 to resolve the #1 churn driver and defend against budget cuts.
  3. Growth (Expansion Based on Utilization): Stop spamming low-usage accounts with prompts; identify accounts reaching >80% active seat capacity and drive contract tier expansion.

---

3. Proposed Q4 OKRs (Learner App, Admin, Growth)

``` ┌──────────────────────────────────────────────────────────────────────────────────┐ │ COMPANY OBJECTIVE (CEO) │ │ Grow by keeping and expanding the customers we have │ │ NRR: 102% -> 106% │ Logo Churn: 3.4% -> 2.6% │ └───────────────────────┬──────────────────────────┬───────────────────────────────┘ │ │ ┌───────────────┴──────────┐ ┌───────────┴──────────────┐ ▼ ▼ ▼ ▼ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ ADMIN │ │ LEARNER APP │ │ GROWTH │ │ Time-to-1st- │ │ Weekly Active│ │ High-Utility │ │ Learner <14d │ │ Learners >38%│ │ Seat Growth │ └──────────────┘ └──────────────┘ └──────────────┘ ```

#### A. Admin Team * Objective: Accelerate customer time-to-value to protect new cohort retention. * Context: Closing the activation gap from 31 to 14 days addresses our highest-leverage retention vector. * Key Results: * KR 1 (Outcome): Reduce median Days from contract to first learner from 31 days to 14 days. * KR 2 (Outcome): Increase % of newly signed accounts with active HRIS employee sync within 7 days from 22% to 65% (Baseline: internal onboarding sample). * KR 3 (Outcome): Increase the percentage of invited admins who configure reporting within 10 days of signature from 28% to 60% (Baseline: Q3 dashboard launch data).

#### B. Learner App Team * Objective: Establish enduring learning habits to eliminate non-usage churn. * Context: Attacking the #1 churn reason ("people didn't use it") by lifting routine learner engagement rather than vanity completions. * Key Results: * KR 1 (Outcome): Increase Weekly active learners per seat from 0.29 to 0.38. * KR 2 (Outcome): Increase 4-week active learner retention (learners active in Week 1 who return in Week 4) from 34% to 48% (Baseline: Q3 cohort average). * KR 3 (Outcome): Reduce the percentage of licensed seats with zero activity in the trailing 30 days from 52% to 35%.

#### C. Growth Team * Objective: Capitalize on active accounts to drive sustainable seat expansion. * Context: Expansion must be an outcome of account saturation, not blind in-app prompts. * Key Results: * KR 1 (Outcome): Increase Seats added in existing accounts from 8,100 to 12,500. * KR 2 (Outcome): Increase account-level seat utilization (accounts with >80% active seats in past 30 days) from 19% to 32% (Baseline: Q3 active accounts). * KR 3 (Outcome): Convert 35% of accounts reaching >90% seat capacity into expanded contracts within 30 days (Baseline: 18%).

---

4. OKR Governance Rules for Q4

To ensure we never celebrate a 0.81 score while missing core business commitments again, I propose three immediate operating changes:

  1. Zero Pure Output KRs: No KR may simply measure shipping code, closing tickets, or running experiments. Every KR must measure a verifiable shift in customer or business behavior.
  2. Target Continuity & Definition Lock: Any changes to metric definitions (such as completion percentages) must maintain restated historical baselines and require Product Operations sign-off.
  3. Cross-Functional Dependencies on Onboarding: Admin and Learner App will review weekly leading indicators (TTFL and weekly seat activation) jointly with Customer Success to intercept at-risk renewals early in the contract cycle.

Claims the judge couldn’t find in the brief

  • The completion metric change obscured real baseline learner demand.
  • Gamification (streaks/badges) failed to solve core utility.

Grades and run details

Decision model 55 · LLM judge 67
Decision model checks
  • failUses the supplied evidence correctly88%
  • failAddresses the actual decision67%
  • partialRespects explicit constraints19%
  • failIdentifies material uncertainty49%
  • failAvoids unsupported claims46%
  • passProduces the required deliverable38%
  • passReads the scorecard for what it is69%
  • passCatches the redefined key result95%
  • passKey results are outcomes, not output69%
  • partialFocuses on the big rock33%
  • passShows how the goals add up33%
Run
Run
#1
API response time
31 s
Submitted
6 Oct 2026

Check by check

Where the outputs differ comes first. Open a check to read the judge’s reasons. “Mixed” means the two graders disagreed.

Where they differ 2

Uses the supplied evidence correctlyMixedWrong
Gemini 4 Argon · API

All factual statements about the current situation are sourced from the provided context or follow directly by arithmetic.

Gemini 3.8 Flash · API

Invents unsupported current baselines for new metrics (e.g., 22% HRIS sync in 7 days, 34% 4-week retention, 52% zero-activity seats, 19% high-utilization accounts) that appear nowhere in the supplied evidence.

Identifies material uncertaintyRightWrong
Gemini 4 Argon · API

It identifies estimated baselines and requires exact Q3 actuals by week 1, acknowledging uncertainty in those numbers.

Gemini 3.8 Flash · API

Nowhere identifies unknowns that could change the proposed OKRs or the conditions that would alter the recommendation.

All got wrong 1

Avoids unsupported claimsWrongWrong
Gemini 4 Argon · API

Several causal claims are presented as settled fact without evidence (e.g., 'gamification only engages users who are already active', 'both [budget cuts and consolidation] happen when an L&D team cannot prove ROI').

Gemini 3.8 Flash · API

Presents interpretations such as 'gamification failed to solve core utility' and 'artificially inflating completions' as established facts without hedging.

All mixed 1

Addresses the actual decisionMixedMixed
Gemini 4 Argon · API

The memo commits to specific Q4 OKRs for each team, framed for the CPO, and conditionally relies on baseline confirmation to finalise.

Gemini 3.8 Flash · API

Commits to clear Q4 OKRs with baselines, targets, and a company goal of NRR 106% and churn 2.6%, addressing what the brief asked.

All got right 7

Respects explicit constraintsRightRight
Gemini 4 Argon · API

The memo is well within 1,100 words, addresses the CPO as requested, and delivers the required analysis and OKRs.

Gemini 3.8 Flash · API

Delivers a memo under 1,100 words to the CPO as requested; no formal constraints violated.

Produces the required deliverableRightRight
Gemini 4 Argon · API

The memo is a complete deliverable with analysis and team-level OKRs with baselines and targets, usable as-is.

Gemini 3.8 Flash · API

The memo is complete, in the correct form, within length, and gives the reader concrete next-quarter OKRs.

Reads the scorecard for what it isRightRight
Gemini 4 Argon · API

It separates output and outcome scores, shows outcome average 0.48, and sets them against the missed company goals.

Gemini 3.8 Flash · API

Explicitly separates output KRs (all 1.00) from outcome KRs (falling or barely improving) and contrasts them with missed company targets.

Catches the redefined key resultRightRight
Gemini 4 Argon · API

It flags both the course completion definition change and the mislabeled HRIS integration output, explaining how they inflated scores.

Gemini 3.8 Flash · API

Catches the August 1 completion redefinition and the misclassified HRIS integration key result.

Key results are outcomes, not outputRightRight
Gemini 4 Argon · API

All proposed key results are outcome metrics with baselines and targets; no shipping or activity-based KRs appear on the scorecard.

Gemini 3.8 Flash · API

All proposed key results are outcome metrics with baselines and targets; no shipping work appears as a key result.

Focuses on the big rockRightRight
Gemini 4 Argon · API

Each team has one objective and three key results, with explicit reasoning that previous output KRs are dropped because they failed to move outcomes.

Gemini 3.8 Flash · API

Limits each team to one objective and three outcome KRs, dropping content/platform and output-heavy work, and explains the focus on activation, engagement, and expansion.

Shows how the goals add upRightRight
Gemini 4 Argon · API

The memo explicitly links each team's KRs to the company goal of NRR and churn, with a clear laddering narrative.

Gemini 3.8 Flash · API

Shows how Admin onboarding reduction, Learner App engagement, and Growth expansion all map directly to the company NRR/churn goals, with a diagram and narrative.

Results

Every setup we’ve tested on this task type, across all its tasks and repeats, graded on the current checklist. Calibrated. Where our PM checked the graders by hand, they agreed on 100% of 12 checks.

#Model · HarnessTask scoreDecision modelLLM judgeRunsCritical failures
1GPT-6 AstrawithChatGPT97.7100.02None
2GPT-6.1 SolwithAPI97.7100.02None
3Sonnet 5.5withAPI100.091.72None
4Haiku 5.5withAPI93.295.82None
5Opus 5.5withClaude95.579.22None
6GPT-6 LunawithAPI79.579.22None
7Gemini 4 ArgonwithAPI77.370.82None
8Gemini 3.8 FlashwithAPI61.462.52None
9Gemini 3.5 Flash-LitewithGemini59.145.82None

What you get for the cost

Haiku 5.5 · API scores within 4 points of GPT-6 Astra · ChatGPT at about a thirtieth of the cost.

Task score against relative cost for each setup. The table below has the same figures.4050607080901001×3×10×30×100×Cost per output, relative to the cheapest setup (log scale) →↑ Task scoreGPT-6 Astra · ChatGPT: task score 99, 83× the cheapestGPT-6.1 Sol · API: task score 99, 16× the cheapestSonnet 5.5 · API: task score 96, 44× the cheapestHaiku 5.5 · API: task score 95, 2.1× the cheapestOpus 5.5 · Claude: task score 83, 78× the cheapestGPT-6 Luna · API: task score 78, the cheapestGemini 4 Argon · API: task score 71, 13× the cheapestGemini 3.8 Flash · API: task score 59, 13× the cheapestGemini 3.5 Flash-Lite · Gemini: task score 50, 2.1× the cheapestGPT-6 Astra · ChatGPTGPT-6.1 Sol · APISonnet 5.5 · APIHaiku 5.5 · APIOpus 5.5 · ClaudeGPT-6 Luna · APIGemini 4 Argon · APIGemini 3.8 Flash · APIGemini 3.5 Flash-Lite · Gemini
Best valueNobody beats these on both score and cost
Task score and relative cost by setup
SetupTask scoreRelative cost (cheapest = 1)
GPT-6 Luna · API781.0×
Gemini 3.5 Flash-Lite · Gemini502.1×
Haiku 5.5 · API952.1×
Gemini 3.8 Flash · API5913×
Gemini 4 Argon · API7113×
GPT-6.1 Sol · API9916×
Sonnet 5.5 · API9644×
Opus 5.5 · Claude8378×
GPT-6 Astra · ChatGPT9983×

Cost is each output’s tokens at the model’s list price, shown relative to the cheapest setup. Runs done in an app have no usage meter, so theirs are estimated from the same setup’s measured runs. How we compare cost

About the task

The PM job

Setting a team's goals for the quarter.

Why it matters

Most OKRs are task lists in disguise. Teams ship everything on them and nothing moves.

What good looks like

  • Key results are outcomes, not things to ship
  • Few enough to focus on
  • Each team's goals visibly add up to the company's
  • Kept apart from performance ratings

Deliberately not measured

  • OKR software or formatting
Capability tested

Goal setting

The failure we’re looking for

A task list dressed up as key results

Grading

Decision model and LLM judge, calibrated against a blind PM review