The CEO’s First 90 Days With OKRs: What You Own and What You Delegate

Most OKR rollouts don’t die in the drafting workshop. They die around week six, when the CEO stops showing up to check-ins and the organization quietly concludes the whole thing was optional.

I see this pattern often in my work at the OKR Institute. [EDITOR: insert one anonymized client example here, two or three sentences, real details only.] More training for teams rarely fixes it. What fixes it is a clear answer, before launch, to one question: which parts of the rollout do you hold yourself as CEO, and which parts do you hand over?

This post gives you that split, role by role, followed by a 90-day plan you can put in your calendar. If you want a refresher on what OKRs are, read that first. For the full process view, our OKR implementation guide covers the phases in detail. This article is about you.

Why implementing OKRs as a CEO can’t be fully delegated

OKRs are a prioritization tool before they are a goal-setting tool. Every company objective you commit to means something else won’t get people or budget this quarter. Only the CEO can make that trade-off hold across departments.

The team at WhatMatters, John Doerr’s OKR platform, argues that leadership has to be fully on board and that setting the strategic priorities behind company OKRs is leadership’s job (WhatMatters). I’d add one thing. Being on board isn’t a statement in a launch email. It’s attendance.

Your people won’t study the memo. They’ll notice whether you show up to the monthly review and whether a red key result gets a decision or a lecture. Those signals shape the culture faster than any workshop.

The opposite mistake is just as common. A CEO who writes every team’s key results gets compliance and a long list of activities dressed up as outcomes. So the job is narrower than most founders expect, and harder to do consistently.

The role split: CEO, OKR champion and managers

We’ve written before about the full set of roles in the OKR system. For a first rollout, four of them matter. Here’s who holds what.

Role	Owns	Does not do
Генеральный директор	The reason for OKRs, company objectives, the stop list, the monthly and quarterly reviews, the rules (including no link to bonuses)	Write team key results, chase updates, administer the tool
OKR champion	Cycle calendar, templates, quality checks on drafts, check-in facilitation, coaching managers, reporting progress to the CEO	Decide company priorities, own any team’s key results
Managers	Drafting team OKRs with their team, the weekly check-in, escalating blockers they can’t solve	Copy company OKRs down one level and call it alignment
Team members	Proposing key results, updating confidence each week, naming blockers early	Wait to be told what their key results are

What you own as CEO

1. The reason. One paragraph: why OKRs, why now, and what will be different in a year if this works. If you can’t write it, you’re not ready to launch.
2. Company objectives. Draft them with your leadership team and keep the list short. Each key result should describe an outcome, not an activity. Google’s re:Work guide flags verbs like “help” or “analyze” as a sign you’re describing work rather than results.
3. The stop list. Name the projects that lose resources because of the new objectives. Teams believe priorities when something visible stops.
4. The top of the cadence. You chair the monthly leadership review and the quarterly review. Those two meetings are where trade-offs get made, so you can’t skip them.
5. The rules. Keep OKRs separate from compensation. Once key results drive bonuses, people start setting targets they know they’ll hit.
6. The champion’s mandate. Appoint the champion, give them authority to schedule and challenge, and agree in writing how much of their week this takes.

If you want a sharper list of the strategic questions to settle first, see our post on the questions

management should ask перед внедрением OKR.

What you delegate to the OKR champion

The champion owns the process. They don’t own the goals. That distinction keeps them out of the “OKR police” trap, where one person ends up responsible for everyone else’s numbers.

Pick someone respected across departments with direct access to you. A junior coordinator can run a calendar, but they won’t be able to tell a department head that their key result is a task list. Get them trained before launch. Our OKR Practitioner certification was built for exactly this role. Larger organizations that plan to scale OKRs company-wide often add a Chief OKR Officer, trained through our Chief OKR Officer course.

Hand the champion these jobs in full:

• the cycle calendar and every deadline in it
• templates and the tool setup (a spreadsheet is fine for a pilot)
• a quality check on every draft before it reaches you
• facilitating check-ins until managers can run them alone
• a one-page progress summary before each leadership review

What managers carry

Gallup estimates that managers account for at least 70% of the variance in employee engagement across business units (Gallup). OKRs travel through the same channel. If managers treat them as paperwork, so will their teams.

Managers translate company objectives into team outcomes and draft OKRs with their team, not for it. They run a short weekly check-in, ideally inside a meeting that already exists, so OKRs don’t add a new calendar slot. And they bring blockers upward instead of absorbing them. Our Курс OKR-лидерства focuses on this shift in how managers lead.

Your first 90 days with OKRs, phase by phase

The plan below assumes one quarterly cycle with a pilot group. Start with your leadership team plus one or two departments. A company-wide launch in quarter one usually spreads the champion too thin to coach anyone properly.

Days 1 to 30: decide and design

• Week 1. Write the reason paragraph. Appoint the champion. Choose the pilot group. If you’re unsure where your organization stands, the free OKR maturity assessment takes under 15 minutes.
• Week 2. Run a leadership session to draft company objectives and the stop list. Expect disagreement here. That’s the point of the session.
• Weeks 3 and 4. The champion gets trained and builds the cycle calendar and templates. You sign off the calendar and announce the launch yourself, in person or on video.

You own: the reason, the objectives, the stop list, the announcement. You delegate: logistics, templates, training, tool choice.

Days 31 to 60: launch and build the rhythm

• Week 5. Teams draft their OKRs with their managers. The champion checks quality. You review for alignment with company objectives only. Leave the wording alone.
• Week 6. Weekly check-ins start. Fifteen minutes per team is enough to cover what moved and what’s blocked, with an updated confidence score per key result.
• Week 8. First monthly leadership review, chaired by you. Every red key result leaves the room with a decision, whether that means more resources, a different approach, a lower target or dropping it.

You own: the alignment review and the monthly review. You delegate: draft quality, check-in facilitation, reminders and the progress summary.

This is the phase where most CEOs drift away. Block the review dates in your calendar during week 1, before anything else claims them.

Days 61 to 90: review, learn, hand over

• Week 10. Mid-course check. Adjust or drop key results that lost relevance. Changing an OKR mid-quarter is allowed if you say why.
• Week 12. Quarterly review and retrospective. Score every key result and ask what blocked progress. With stretch goals, Google’s re:Work guide treats around 70% achievement as success. A team that scores 100% everywhere probably aimed low.
• Week 13. Decide what changes in cycle two: which teams join, what the champion stops doing, which managers are ready to run check-ins without help.

You own: the quarterly review and the scale decision. You also tell the organization what it learned. You delegate: scoring logistics, the retrospective format, template updates and onboarding the next teams.

Don’t expect a mature system after one cycle. Our implementation guide puts full adoption in a mid-sized organization at two to three quarters, with the first cycle mostly a learning phase. The Цикл «от команды до воздействия» describes how the weekly, monthly and quarterly rhythms connect once the pilot is over.

Signs you’re doing the champion’s job

• You’re rewording key results in team drafts.
• Managers send updates to you directly instead of logging them in the check-in.
• The champion waits for your approval before scheduling anything.
• You’re the one chasing late updates on a Friday afternoon.

The reverse also happens. If you haven’t attended a review since launch, or teams can’t explain why the company objectives were chosen, you’ve delegated the parts that were yours.

Where 90-day rollout coaching fits

You can run all of this without outside help. Plenty of companies do. What a coach changes is the speed of the learning loop: someone who has seen the same week-six slump in other organizations can name it before it costs you the cycle.

At the OKR Institute we package this as the 90-Day Execution Sprint. You get a scored diagnosis of where execution breaks down by week two, and weekly check-ins run from week six. In week twelve you chair the quarterly review with us in the room. Executive time is capped at five days across the quarter. From quarter two, two certified internal coaches run the rhythm and we step back. You can see how this played out at Maybank, Telkom Indonesia and others in our тематические исследования.

Часто задаваемые вопросы

How much time does implementing OKRs take a CEO?

Most of it lands in the first month, when you write the reason and run the leadership session. After that, plan for the monthly and quarterly reviews plus short questions about key results in your regular one-on-ones.

Who should be the OKR champion?

A respected operator with direct access to the CEO and enough standing to challenge department heads. It doesn’t have to be HR or strategy. Train the person before launch.

Should the CEO have personal OKRs?

In the first cycle, the company OKRs are effectively yours. A separate personal set tends to split your attention. Revisit it in cycle two or three.

Should OKRs be tied to bonuses?

No. When key results affect pay, teams set targets they’re sure to hit, and the stretch disappears.

How long before OKRs show results?

Expect the first cycle to be a learning phase. Full adoption in a mid-sized organization usually takes two to three quarters.

Start your first cycle with a plan

If you’re about to launch OKRs and want a second pair of eyes on your 90-day plan, book a call with our team. We’ll tell you honestly whether you need coaching or just a sharper role split.

Похожие курсы

Недавние Посты

Теги

1ТП5ТОКР

#OKR AI agents

#trends 2026