How to Write OKRs: Step-by-Step Guide With Examples (2026)
Learn how to write effective OKRs step by step. Includes the planning-first formula, common mistakes to avoid, and real examples for startups and growing teams.
Loach Team
Product Team
Writing OKRs sounds simple. An Objective. A few Key Results. Done.
But most teams end up with OKRs that are either too vague to act on, too easy to be motivating, or so disconnected from daily work that nobody looks at them after the kickoff meeting.
This guide covers the full process: how to write objectives, how to write key results, how to validate them before the quarter starts, and — critically — how to connect them to what your team actually works on each week.
The Formula
Every OKR follows the same structure:
We will [Objective] as measured by [Key Result 1], [Key Result 2], [Key Result 3].
Example:
We will establish a repeatable sales motion as measured by closing 20 new SMB customers, reducing average sales cycle to under 30 days, and achieving 3x pipeline coverage by end of quarter.
If you can fill in that template clearly, you have the foundation of a good OKR. If you struggle to complete the sentence, the OKR is not ready.
Part 1: Writing Good Objectives
An Objective is a qualitative, inspiring statement of where you want to go this quarter.
The three tests for a good Objective
1. Is it directional? "Grow the business" is not an objective. "Establish product-market fit in the SMB segment" is.
2. Is it achievable this quarter? "Become the market leader" is a multi-year goal. "Become the preferred tool for OKR-adopting startups in the DACH region" is a quarter.
3. Does it motivate your team? Read the objective aloud in your kickoff meeting. Does it create energy? If it sounds like corporate filler, rewrite it.
Objective examples
| Weak | Strong |
|---|---|
| Improve customer satisfaction | Make customers love our onboarding experience |
| Grow revenue | Build a sales machine that hits €120k ARR this quarter |
| Fix product issues | Ship a product your best customers rave about |
| Hire people | Build the founding team that takes us to Series A |
How many Objectives per quarter?
- New to OKRs: 1–2 objectives
- One or two cycles in: 2–3 objectives
- Experienced teams: 3–5 objectives maximum
More than 5 objectives means everything is a priority — which means nothing is.
Part 2: Writing Good Key Results
Key Results are the measurable outcomes that tell you whether you achieved your Objective. They are not tasks.
The difference between Key Results and tasks
| Key Result | Task |
|---|---|
| Increase NPS from 32 to 50 | Send NPS survey to all customers |
| Reduce churn from 5% to 3% | Implement cancellation flow with offboarding |
| Close 20 new customers | Make 200 cold calls |
Key Results describe outcomes. Tasks describe actions. Both matter, but they belong in different places.
The three tests for a good Key Result
1. Is it measurable? "Improve customer success" is not measurable. "Increase customer NPS from 32 to 50" is.
2. Does achieving it prove the Objective was met? If all your Key Results hit 100%, would you confidently say the Objective was achieved? If not, you are missing something.
3. Is it a stretch? A good Key Result should require real effort. If your team thinks it is already done, it is not a key result — it is a baseline. Aim for ~70% confidence of hitting it.
Key Result examples by type
Growth / revenue:
- Grow MRR from €25,000 to €40,000
- Close 15 new enterprise accounts (ACV > €12,000)
- Increase trial-to-paid conversion from 18% to 28%
Product / retention:
- Reduce monthly churn from 6% to under 3%
- Increase feature activation rate from 40% to 65% within 30 days of signup
- Ship 3 features rated 4+ stars by beta users
Marketing / awareness:
- Grow organic traffic from 3,000 to 6,000 monthly sessions
- Generate 80 inbound leads from content
- Achieve 500+ LinkedIn followers among target persona (startup founders)
Team / operations:
- Increase team NPS from 55 to 70
- Reduce average time-to-hire from 6 weeks to 3 weeks
- Complete all 4 quarterly OKR reviews on schedule
How many Key Results per Objective?
2–4 is the sweet spot. Fewer than 2 and you risk gaming the metric. More than 4 and the Objective becomes unwieldy.
Part 3: The Planning Test (Most Teams Skip This)
Here is where most OKR guides stop. But writing good OKRs is only half the job. The other half is making sure your team can actually execute on them.
The Planning Gap
The most common reason OKRs fail is not bad goal-setting — it is the absence of weekly planning. Teams set OKRs at kickoff and never translate them into concrete weekly work. By week three, the OKRs are collecting dust.
Before finalising any OKR, run the planning test:
"What would we need to work on in week 1 to make progress on this Key Result?"
If you cannot answer clearly, the OKR is not ready. Either the Key Result is too abstract, or you do not yet understand the path to achieving it.
Running the decomposition
For each Key Result, break it down:
- Monthly milestones: What does 30%, 60%, and 90% progress look like at end of each month?
- Week 1 priorities: What specific actions need to happen in the first week?
- Ownership: Who owns each priority?
Example:
Key Result: Grow organic traffic from 3,000 to 6,000 monthly sessions
| Month | Milestone | Week 1 priorities |
|---|---|---|
| Month 1 | 4,000 sessions | Publish 2 SEO articles, fix 5 technical issues |
| Month 2 | 5,000 sessions | Publish 3 articles, build 2 backlinks |
| Month 3 | 6,000 sessions | Publish 2 articles, optimise top 5 ranking pages |
This decomposition is what turns OKRs from aspirational statements into a real plan.
Part 4: Common Mistakes
Mistake 1: Writing activities as Key Results
Wrong: "Conduct 10 customer interviews" Right: "Validate 3 customer pain points with statistical significance across 20+ interviews"
The first is a task. The second is an outcome.
Mistake 2: Setting OKRs that are already done
If a Key Result is 80% achieved at the start of the quarter, it is not a stretch goal — it is a baseline. Either raise the bar or replace it.
Mistake 3: Too many OKRs
Five teams each with 4 objectives and 3 key results = 60 things the company is tracking. Nobody can hold 60 priorities in their head. Consolidate ruthlessly.
Mistake 4: Setting OKRs top-down without team input
OKRs work when teams feel ownership. If leaders hand down fully-formed OKRs without discussion, the team has compliance — not commitment. Run a collaborative kickoff.
Mistake 5: Never reviewing them
OKRs set in January should not be reviewed for the first time in March. Weekly check-ins catch drift early and keep OKRs alive as a planning tool rather than a reporting exercise.
Part 5: The Weekly Rhythm
Once OKRs are written and decomposed, the job is to maintain a weekly rhythm:
- Monday planning (10 minutes): Review this week's priorities from the decomposition. Adjust if circumstances changed.
- Weekly check-in (5 minutes per person): What did I accomplish? What is my focus this week? What is blocking me?
- Mid-quarter review: Are we on track? Do any OKRs need adjustment?
- End-of-quarter scoring: Score each Key Result 0.0–1.0. Reflect on what worked and what did not.
The weekly rhythm is what separates teams that hit their OKRs from teams that just have them.
FAQs
Q: Should OKRs be top-down or bottom-up?
Both. Company-level OKRs set direction top-down. Team-level OKRs are written bottom-up within that context. Good OKRs are a negotiation between leadership and teams, not a dictation.
Q: Can Key Results be binary (yes/no)?
Yes, but use them sparingly. "Launch feature X by end of quarter" is a valid binary Key Result. But numerical KRs are generally better because you can track progress over the quarter rather than waiting for a pass/fail at the end.
Q: How long should writing OKRs take?
A well-run OKR kickoff for a team of 5–10 takes 2–3 hours including decomposition. If it takes more than half a day, you are over-engineering it. If it takes 30 minutes, you are under-investing.
Q: Do all teams need their own OKRs?
Not necessarily. For startups under 15 people, one set of company OKRs with clear ownership at the key result level often works better than separate team OKRs. Add team-level OKRs when teams have genuinely different priorities.
Conclusion
Writing good OKRs is a skill that improves with each cycle. Your first quarter will not be perfect — and that is fine. The goal is to establish the habit of connecting quarterly goals to weekly work.
The writing is the easy part. The planning — breaking down key results into weekly priorities — is where execution lives.
Related resources:
- OKR Examples — 25+ examples for every team type
- OKR Template Generator — Generate tailored OKR templates instantly
- OKR Health Checker — Validate your OKRs before the quarter starts
- Why OKRs Fail — And how to avoid the most common traps
Ready to turn your OKRs into a weekly plan? Get started with Loach free →