Draft OKRs

Onboarding squad OKRs, next quarter (draft for Friday)

Objective: Make Fieldnote the place new teams get started.

• KR1: Raise the share of new teams still active in week 4 from 34% to 40%. (Company KR, shared with leadership.)
• KR2: Raise the share of new teams with three or more members joining in week one from 29% to 50%.
• KR3: Cut the median time from sign-up to the first note opened by a second member from 3 days to 1 day.
• Guardrail: Zero open P1 bugs at quarter end, with no new P1s in onboarding flows.

Delivery plan (tracked, not scored): - Invite flow redesign and onboarding emails first, since they target KR2 and KR3. - Onboarding checklist next, then the five templates. - Ten user interviews with teams that stalled after sign-up, to learn why people didn't invite others. - Dark mode, AI summaries, and the four help articles are paused. If leadership has committed to any of them, let's discuss before Friday.

---

Note to the squad

Hi all. I reworked the draft before it goes to leadership. Here's what changed and why.

1. One objective, tied to the company goal. The draft had three objectives, and several items (dark mode, AI summaries) didn't connect to the week-4 number. Everything now points at one goal: new teams getting started.

2. We're targeting the lever the data points to. Teams with three or more people joining in week one stay active at 58% in week 4. Everyone else stays at 21%. Only 29% of new teams get there today. Getting more teams to that threshold is the biggest lever we can see. It's correlation, though, not proof. Teams that invite friends early may already be more committed. The invite flow work is our test of whether the link is causal, so we'll watch it closely.

3. Outcomes over outputs. Since bonus multipliers now depend on the OKR score, I want the score to measure whether we moved the number, not whether we shipped things. A "ship 5 templates" KR scores 100% even if nobody uses the templates. The delivery plan still shows what we're building, and it has no bearing on the score.

4. Fewer KRs. Ten KRs across three objectives meant spreading five engineers and a designer very thin. Three KRs plus a guardrail give us a clear focus.

5. Bugs stay in as a guardrail. I cut "fix 50 bugs" because a count rewards small fixes over important ones. Zero P1s is the real bar: we shouldn't trade quality for onboarding speed.

6. Targets I'd like your pushback on. The 50% figure for KR2 is my estimate of what would move week-4 activity toward 40%, based on the 58% and 21% split. If the link is weaker than it looks, that target may be wrong, and I'd rather find out in week three than week twelve. Likewise, the one-day target in KR3 is a judgment call. Tell me if the invite flow can't realistically get there.

Thanks for the work so far. The draft's raw material was solid. It just needed one thread running through it. Let's review progress at week six, and I'll bring any changes to the team first.

Here is the revised OKR draft along with the team note.

*

Proposed Q3 OKRs: Onboarding Squad

Objective 1: Accelerate new teams to their first collaborative moment * KR 1: Increase the share of new teams with 3+ members in Week 1 from 29% to 45%. * KR 2: Reduce median time from team creation to first collaborative note opened from 3 days to <24 hours. * KR 3: Contribute directly to the company goal by lifting new team Week 4 retention from 34% to 40%.

Objective 2: Deliver a seamless, zero-friction first-run experience * KR 1: Maintain zero open P1 bugs across the sign-up, invite, and first-note flows throughout the quarter. * KR 2: Increase invite-flow conversion (invites sent per new team) by 25%.

*

Note to the Squad

Team,

Thanks for pulling the initial draft together! Ahead of our review with leadership this Friday, I’ve refocused our OKRs. Here is what changed and why:

#### 1. We shifted from outputs to outcomes Shipping checklists, templates, and emails are solutions, not goals. If we ship all four and retention doesn’t budge, we haven’t succeeded. By framing our KRs around moving specific user behaviors (e.g., getting teams to collaborate faster), we give ourselves the flexibility to iterate, drop what isn’t working, and double down on what does.

#### 2. We’re anchoring on our biggest retention lever Our company goal is lifting Week 4 retention from 34% to 40%. Our data shows an undeniable path to get there: * Teams with 3+ members in Week 1 retain at 58% (vs. 21% for everyone else). * Currently, only 29% of teams hit that milestone. * It takes 3 full days for a teammate to open their first shared note.

Our primary job this quarter is simple: get teammates into the workspace and collaborating on day one. Every template, invite prompt, or checklist we build should serve that specific loop.

#### 3. We cut scope to protect our focus (and our bonuses) Now that HR ties our bonus multipliers directly to squad OKR completion, our OKRs must be focused, measurable, and within our sphere of influence: * Dropped AI summaries and Dark Mode: Both are cool features, but neither solves the core first-week team activation problem. They dilute our engineering capacity. * Dropped NPS (31 to 40): NPS is a lagging, noisy metric influenced by the entire product (pricing, bugs elsewhere, feature gaps), not just onboarding. * Refined bug targets: Fixing an arbitrary "50 bugs" incentivizes fixing trivial issues. Instead, we’re committing to zero critical bugs in our core onboarding and invitation paths.

Let’s chat through any questions at standup tomorrow so we’re fully aligned before Friday!

Q3 Onboarding Squad OKRs (Revised)

Objective: Get new teams collaborating in Fieldnote during their first week.

• KR1: Increase the share of new teams with 3+ members in their first week from 29% to 45%.
• KR2: Reduce the median time from sign-up to a teammate opening a shared note from 3 days to under 24 hours.
• KR3: Increase Week 4 retention for new sign-up cohorts from 34% to 40%.

(Note: Previously listed features like the invite flow redesign, templates, and onboarding emails will now live on our roadmap as the bets we’ll place to hit these numbers).

*

Note to the Squad: What I changed and why

Hey team, thanks for pulling the draft together. Before we send this to leadership on Friday, I’ve made some big cuts and reframed our goals. Because HR is tying our bonus multipliers directly to our OKR score this year, it’s critical that we set ourselves up to win with goals we actually control and can realistically hit.

Here is the thinking behind the changes:

1. One focused Objective tied to company math Leadership’s only goal this quarter is moving Week 4 retention from 34% to 40%. Look at our data: teams with 3+ members in week one retain at 58%, vs. 21% for everyone else. Right now, only 29% of teams hit that 3-member mark. By mathematical average, if we just move the needle on that 3-member metric from 29% to ~45%, we will single-handedly hit the company’s 40% retention target. Furthermore, since Fieldnote charges at 6+ members, getting teams to 3+ in week one is the best thing we can do for the business.

2. Moving from outputs to outcomes Our draft KRs (checklists, templates, invite flow, emails) were a task list. If we ship all four and retention stays at 34%, leadership won’t view the quarter as a success. By making the KRs about behavior (inviting teammates and sharing a first note quickly), we give ourselves the freedom to experiment. We’ll still build the invite redesign and templates, but if they work early, we don't have to build the rest. If they don’t work, we can pivot without failing our OKRs.

3. Protecting our bandwidth (and our bonuses) We are five engineers and one designer. The draft had us building dark mode, AI summaries, and four onboarding features, plus fixing 50 bugs. That’s way too much for one quarter. * Cut "Delight Users" (Obj 3): Dark mode and AI summaries are huge scope creeps for an onboarding team. Also, NPS is a lagging, company-wide metric—we shouldn’t tie our bonuses to a number that core product bugs or pricing changes can tank. User interviews and help articles are great, just as part of our weekly process. * Cut "Improve Quality" (Obj 2): Fixing 50 bugs incentivizes us to hunt for 50 tiny typos, while "zero P1s" is a baseline engineering standard, not a quarterly goal. We will keep squashing bugs in our normal sprint triage, especially anything breaking the sign-up or invite flows, without making it an OKR.

Let’s chat in standup tomorrow to make sure everyone feels good about these numbers before I send them up on Friday!