Usable with a quick edit10 of 11 checks passed
The memo is complete, well-structured, and actionable; a PM could use it with minor edits to fill in baselines, which the memo already flags as needed.
Output
MEMO To: Hannah Iyer, CPO From: Staff PM Re: Aligning team OKRs to the company OKRs, and the process questions
Bottom line
Only Payroll's proposal is close to the company objective (keep and expand existing customers). Core HR and Integrations propose output goals (features and integrations shipped). Growth targets new logos, which move none of the CEO's three key results. I recommend one objective per team, no mechanical link between OKR scores and bonuses, and planning capped at two weeks.
The logic behind the changes
Applying the exit-survey shares to 14% annual churn gives roughly:
- Payroll errors/complexity: 5.3 points
- Price: 3.4 points
- Missing integrations: 2.7 points
- All-in-one competitor: 1.5 points
- Other: 1.1 points
Getting to 10% means removing about 4 points.
Payroll attach alone won't get there. Moving attach from 18% to 25% is about 180 more customers. Payroll customers churn at 8% against 16% for the rest, so even if the gap were entirely causal, attach is worth about 0.6 points of churn. Much of the gap is probably selection, because engaged customers adopt more. The same caution applies to the 6% churn among customers with three or more integrations.
Attach could also backfire. Payroll errors are the top exit reason, so pushing a flawed product onto more customers risks creating more of the churn we are trying to prevent.
The bulk of the churn reduction has to come from fixing Payroll quality and integration gaps. I suggest this split, as a planning assumption rather than a forecast:
| Exit pool | Owner | Target | Churn points |
|---|---|---|---|
| Payroll errors/complexity | Payroll | cut ~40% | ~2.1 |
| Missing integrations | Integrations | cut ~33% | ~0.9 |
| Price | Growth | cut ~15% | ~0.5 |
| All-in-one competitor | Core HR | cut ~33% | ~0.5 |
Together these come to about 4 points, which is 14% to 10%.
The exit data has limits. We have 212 responses against roughly 360 annual churners, and "payroll complexity" may include non-users who left for a payroll-capable competitor. Week one should confirm the cuts by segment.
Team by team
Payroll: keep most of it, tighten it. - Objective: Make payroll reliable enough that customers stay and others add it. - KR1: Payroll-error tickets per 1,000 pay runs down 40%. Normalise the metric. A raw ticket count will rise as attach grows, and it can also be gamed by making tickets harder to file. - KR2: Payroll-error/complexity-cited exits down about 40% (about 2 points of company churn). - KR3: Payroll attach from 18% to 25%, with a guardrail that churn among Payroll customers stays at or below 8%. Sequence the attach push so it leans on the error fixes, targeting segments with clean data first.
Integrations: change the unit of success. "Ship 12" measures output, and the number is arbitrary. The 19% of exits citing missing integrations tells us which ones matter. - Objective: Make Quarry the system customers can't easily unplug. - KR1: Share of customers with three or more integrations connected, up from [baseline needed] by an agreed number of points. - KR2: Integration-cited exits down about a third (about 0.9 points of churn). - Ship the integrations ranked by exit and lost-customer demand. That list is the initiative that serves the KRs, not a KR itself.
Growth: the biggest change. Point it at existing customers. New logos and trial conversion don't affect NRR, churn or attach. A 20% rise in new logos can even worsen churn if the new customers are poorly fit. - Objective: Grow revenue from customers we already have. - KR1: NRR from 101% to 108%. Growth owns the expansion motion, and the other teams contribute. - KR2: Price-cited exits down about 15% through packaging and bundling experiments (for example Core HR plus Payroll). Don't raise list prices this quarter, since price is already the second-largest exit reason. - KR3: Share of new customers with three or more integrations connected within 90 days (baseline to be set). This is a lifecycle problem, which is a growth skill. - Trial conversion (9%) stays on the dashboard with a floor, but it is not a KR. If you want new-logo growth kept as a goal, that is a conversation with the CEO, because it contradicts his objective.
Core HR: the weakest link to the company goal. "Best HR platform" can't be scored, and two of the three KRs are ship dates. I have no evidence that the org-chart redesign or custom fields v2 affect retention. They may be worth building, but they don't earn a KR slot without that link. - Objective: Make Core HR the reason customers don't need an all-in-one competitor. - KR1: All-in-one-cited exits down about a third (about 0.5 points of churn). - KR2: Share of customers whose employee data is complete enough to switch on Payroll, up from [baseline needed]. This makes Core HR a direct contributor to attach, and Core HR and Payroll should confirm the definition. - KR3: CSAT from 4.2 to 4.5, kept as a health metric. - Org chart and custom fields stay on the roadmap only if exit or customer data shows they close the competitor gap. Core HR should make that case in week one.
Process recommendations
1. Three objectives per team: decline, with a better answer to "covered." The company has one objective with three KRs. Four teams with three objectives each would create twelve objectives pulling in different directions, which is the problem this memo is fixing. It would also lengthen planning. I recommend one objective and two or three KRs per team. To address the CEO's concern about coverage, give each team a short health-metric list with floors, such as uptime, support SLAs and CSAT. Those get monitored without being goals. A team may request a second objective if it can show a distinct customer outcome that the company objective doesn't cover.
2. OKR scores setting PM bonuses: recommend against. Last year's average score of 0.95 means the goals weren't stretching or the scoring was generous. Either way, the scores carry little information. Tying pay to them would make this worse, because teams would sandbag, avoid ambitious outcomes and game the metrics (ticket counts being the obvious example). The revised KRs are outcome-based and only partly within a team's control, which makes mechanical payouts less fair still.
Instead: - Calibrate so a typical score is around 0.7, with explicit committed and stretch levels. - Use scores as one input to performance reviews, judged by the manager in context. - Revisit a compensation link after two quarters of calibrated scoring.
If the CFO needs something concrete, tie any variable pay to the three company-level KRs, not team scores. That gives a shared incentive to cooperate.
3. Planning took five of thirteen weeks (38% of the quarter): cap it at two. - The CEO fixes company OKRs at least two weeks before the quarter starts, so teams never plan in the dark. - Teams draft on a one-page template with one objective and no more than three KRs, each with a baseline, owner and target. - One 90-minute cross-team session reconciles overlaps, using the exit-reason allocation above as the starting point. - Planning overlaps the last two weeks of the prior quarter and ends with sign-off by day 5 of the new one. - Fewer objectives per team will itself shorten the cycle.
Decisions and next steps
- Approve the reframing in this memo, and take the Growth change to the CEO before teams redraft, since it is the one most likely to be contested.
- Ask Data for baselines this week: share of customers with three or more integrations, exit reasons by segment, and payroll tickets per pay run. Several KRs above can't be finalised without them.
- Ask each team to resubmit within one week.
- Take the bonus and three-objective positions to the CEO and CFO together, so we have one conversation rather than two.
Grades and run details
Decision model 86 · LLM judge 12 of 12 checks
Decision model checks
- failUses the supplied evidence correctly16%
- passAddresses the actual decision85%
- passRespects explicit constraints31%
- passIdentifies material uncertainty95%
- passAvoids unsupported claims52%
- partialProduces the required deliverable66%
- passAims the teams with the churn data100%
- passReads the 0.95 average for what it is99%
- passKey results are outcomes, not output60%
- passFocuses on the big rock99%
- passShows how the goals add up60%
Run
- Run
- #1
- API response time
- 67 s
- Submitted
- 5 Oct 2026