How to launch a quarterly OKR cycle

Launching a quarterly OKR cycle means setting up the steering mechanism that should carry the organization toward its goals for the quarter. You pick a few priorities, make them visible to everyone, track them at regular intervals, then make trade-offs along the way.

This page is a get-started manual. It assumes the underlying decision has already been made, which the guide Setting up OKRs in an SMB or scale-up covers, and it sits within the broader logic of Structuring your company to stay agile. The aim here is simple: to run a quarterly OKR cycle from start to finish without it running out of steam after three weeks.

Why run a quarterly cycle

The quarter is the natural unit of time for OKRs: long enough for a meaningful change to happen on the way to the annual strategic goals, and short enough that the assumptions you made when defining the objectives are still true by the end of the period, whether they concern the market, the teams, the technology, or business priorities.

The quarterly rhythm serves the annual objectives, which are often highly strategic and therefore hard to read day to day, which is exactly why it helps to translate them into more concrete goals over three months. It also keeps the intended trajectory visible and turns the steps into something achievable over spans of time a human can actually grasp.

The quarterly cycle drives this by forcing regular pivot points. Every three months, you take the priorities again, measure what has moved, and learn from what didn't work. It's a way of serving the strategic horizon: the long-term direction stays, but it breaks down into steps short enough to remain steerable.

What to prepare before the quarter

An OKR cycle begins before the quarter itself. The best launches start several weeks ahead, with a framing phase at the leadership level. That's where you reset the company's priorities for the period, decide on the level of ambition, and make sure the framework will be announced early enough for teams to absorb it, set their own objectives, and identify the initiatives that will get them there.

The level of ambition is worth setting out explicitly at this stage. Whether an objective is committed, and therefore expected to reach 100%, or aspirational, with a deliberately high target, you won't steer it the same way. Saying so in advance avoids the end-of-cycle misunderstanding where a deliberately high target is experienced as a failure.

It's also the moment to identify dependencies between teams. An objective that relies on another team's contribution without that team knowing is already a weakened objective. Making these links visible before launch does cost a sync meeting or two, but ignoring them costs a quarter.

Building the quarter's OKRs

Building has to stay simple: a few objectives, a few key results, a clean logic. Keep it simple: the intern who glances up from their phone mid-meeting should be able to grasp the strategy at a glance.

Building flows down from the company's strategic priorities to team OKRs, then, where it makes sense, to a few individual OKRs. The most common mistake is to set too many. Doerr recommends sticking to three to five objectives per cycle, with at most five key results each, precisely so that focus stays real. An overloaded cycle isn't more ambitious; it's just more diluted.

The rule that makes the biggest difference fits in one sentence: the objective describes what you want to accomplish, the key result describes how you'll know you got there. A key result must therefore be measurable, time-bound, and verifiable, and describe an observable outcome rather than an activity. "Analyze," "support," or "take part in" describe work, not an effect. Keep "outcome vs output" in mind: what counts is what moves, not what gets done.

Launching the cycle

The launch is a moment of alignment for the whole organization. You communicate first at the company level, so everyone sees the overall priorities, then at the team level, then, where relevant, at the individual level. At each tier, sharing the OKRs is a chance to clarify, answer questions, and sometimes negotiate, between a manager and a report, what is realistic and what isn't.

Visibility matters as much as content. OKRs filed away in a document no one reopens produce nothing. Made visible, shared, and recalled, they become a shared language of priorities, and coordination stops being a meetings problem and becomes a shared-objectives one.

Tracking through the quarter

This is where cycles live or die: an OKR with no regular follow-up fails within six weeks on average.

The right operating cadence looks like this:

• a weekly update from the owners of the key results and initiatives
• a weekly read of the dashboards by the leadership team
• a biweekly progress review by the leadership team to arbitrate priorities, and more often if risks come up.

A common misunderstanding is to think you have to "score" OKRs every week. You don't. Weekly tracking isn't there to judge, but to hold the course and correct early. A simple confidence score, which says whether the organization is on track or not, is more than enough to trigger the right conversations. Those conversations often find their best home in the manager-report 1:1, where progress on an objective connects to a person's actual workload and concrete obstacles.

Handling gaps along the way

An OKR cycle isn't set in stone. If a priority changes, if a dependency turns out to be unmanageable, or if an objective becomes unrealistic, you can and should re-arbitrate its priority. Once again, the point is to keep the focus on what matters for creating change. Stubbornly pushing every objective into the green is pointless and counterproductive when some are no longer relevant or demand too much effort for the result they would bring (which is exactly why you shouldn't tie compensation to OKR attainment).

A few situations come up regularly and call for de-prioritizing objectives and KRs:

• the unanticipated dependency (an objective made impossible to hold without another team's action)
• resources that turn out to be unavailable (a hire that never lands, and so on)
• the discovery of a blocker that prevents delivery (a major technical issue, a legal constraint, and the like)
• the emergence of a new strategic priority

In each of these cases, adjusting isn't an admission of weakness, it's the sign that the cycle is doing its job: surfacing early what you couldn't see at the outset.

Closing the quarter

The end of a cycle isn't just about computing an attainment rate. It's a time for learning. Each KR has reached its final score, and each objective its overall score; now it's time to dig into the "why":

• which KRs contributed most to the result
• which teams were the most prolific
• which initiatives actually moved the needle

But also, and at least as important, what the "cycle hygiene" was, in other words the quality of the follow-up on the cycle's progress, which is also the most reliable predictor of a cycle's success.

Don't turn this close into a report card; the goal is always to improve the system for the next quarter. That doesn't rule out highlighting individual or team wins, but the focus stays on improving the system.

A good retrospective produces two or three concrete lessons that you feed back into the following cycle: a sharper objective, a better-framed dependency, a more sustainable follow-up rhythm.

Launching the next cycle

The value of OKRs doesn't come solely from one successful quarter, but also from the sequence: each cycle builds on the lessons of the last and prepares the next. This repetition turns the method into an organizational habit and brings organizations lasting performance.

The point, in the end, is to make the ritual simple and engaging enough that you want to do it again. A cycle that's too heavy gets abandoned; a lean cycle, tied to the 1:1 and the operating cadence, holds. At Serendly, we help teams do exactly that: prepare, launch, and track their OKR cycles without letting them fade, by connecting them to the managerial conversations that keep them alive.