The time horizon of an OKR is not a scheduling detail — it is a core design feature that determines whether the framework drives genuine change or dissolves into an indefinitely deferred aspiration. OKRs operate on two interlocking time horizons: a quarterly cycle that drives focused near-term execution, and an annual cycle that maintains strategic continuity and longer-horizon direction. Together, these two rhythms create a nested temporal structure in which ambitious annual goals are broken into a series of quarterly change commitments, each building on the progress of the last, compounding toward a strategic destination over the course of a full year or multiple years.
The quarterly cadence — typically 90 days — is the operational heartbeat of the OKR system. It is short enough to create urgency and maintain the team’s sense that the deadline is real and approaching, and long enough to allow meaningful progress on goals that require coordination, investment, and sustained effort. Annual OKRs, by contrast, set the strategic direction and the longer-horizon desired state that quarterly OKRs are designed to progressively achieve. A well-structured OKR system is one in which the annual objectives give the year its strategic shape, and each quarter’s OKRs represent the most important change the organisation can make in the next 90 days to advance toward that annual destination.
The reset at the end of each cycle is as important as the time horizon itself. A reset is not a rollover: it is a deliberate act of closing one change cycle, assessing what was achieved, learning from what was not, and beginning a new cycle with freshly chosen goals calibrated to the current state of the organisation and its strategy. This reset discipline is what prevents OKRs from becoming stale, prevents teams from coasting on inherited objectives that no longer reflect current priorities, and ensures that the framework remains a living change instrument rather than an annual planning document that slowly loses relevance as the year progresses.
The Two OKR Time Horizons
Most organisations operating mature OKR systems maintain two simultaneous time horizons: annual OKRs that define the strategic destination for the full year, and quarterly OKRs that define the focused change commitments for each 90-day period. These two horizons are not separate goal-setting exercises — they are nested layers of the same goal architecture. Annual OKRs provide the context and direction; quarterly OKRs provide the urgency and precision. Every quarterly OKR should be answerable by the question: “Why is this the most important thing to work on this quarter in service of our annual objectives?”
| Time Horizon | Typical Duration | Primary Purpose | Number of OKRs | Primary Audience |
|---|---|---|---|---|
|
Annual OKR
|
12 months (January – December or fiscal year)
|
Strategic direction; longer-horizon desired state; context for quarterly planning
|
3–5 company-level objectives
|
Board, C-suite, all employees (for alignment)
|
|
Quarterly OKR
|
~90 days (Q1–Q4)
|
Focused execution; near-term change commitment; progress toward annual goals
|
2–5 objectives per team or individual
|
Teams, departments, individuals
|
Why 90 Days: The Logic of the Quarterly Cadence
The quarterly cadence is not an arbitrary convention — it reflects a carefully considered balance between competing requirements. Ninety days is sufficient time to make meaningful, measurable progress on an ambitious change goal that requires cross-functional coordination, product development, customer engagement, or organisational capability building. It is also short enough that teams cannot defer action: with only 13 weeks in the cycle, a team that spends the first four weeks in planning and the last two in retrospective review has only seven active execution weeks — a constraint that forces prioritisation and discourages perfectionism in favour of progressive, measurable progress.
Longer time horizons — semi-annual or annual execution cycles — remove this urgency and allow the slow accumulation of deferred action that characterises traditional annual planning failures. When an organisation sets a goal for the full year without quarterly checkpoints, the natural human tendency is to treat the first half of the year as available for preparation and the second half as execution time — a pattern that compresses the actual change effort into the final quarter and produces rushed, low-quality results. The quarterly cadence eliminates this compression by making every quarter a complete change cycle with its own commitment, execution, and assessment rhythm.
Quarterly OKR Calendar Structure:
WEEK 1–2: Planning
Draft objectives for the quarter
Align Key Results to annual OKR direction
Cascade to team and individual level
Confirm ownership and resource allocation
WEEK 3–10: Execution
Weekly confidence check-ins (score each KR: 0.0–1.0)
Identify at-risk Key Results early
Adjust tactics (not targets) in response to findings
Mid-quarter review at Week 6–7 for formal progress assessment
WEEK 11–12: Grading and Retrospective
Score each Key Result with evidence
Calculate overall Objective scores
Document what worked, what didn't, and why
Begin inputs to next quarter's planning session
WEEK 13: Transition
Reset — new objectives drafted
Lessons from current quarter incorporated
Annual OKR progress assessed; Q+1 direction confirmed
Annual OKRs: Strategic Continuity Across Quarters
Annual OKRs serve a different function from quarterly OKRs. Where quarterly OKRs create urgency and focus, annual OKRs create continuity and direction. They are the strategic anchors that prevent the organisation from being pulled in a new direction by every quarterly priority shift, competitive development, or internal initiative that seems important in the moment. A company with clearly defined annual OKRs can evaluate every proposed quarterly priority against a simple question: does this advance our annual objectives? If the answer is no, the quarterly OKR competes with the strategy rather than serving it.
Annual OKRs are typically set at the company and senior leadership level, and they are designed to describe the desired state the organisation wants to reach by the end of the year. They are more directional and less granularly specific than quarterly OKRs — they define the strategic destination, not the precise quarterly milestones. Those milestones are determined during each quarterly planning cycle, when the team asks: given where we are now and what we learned last quarter, what is the most impactful 90-day advance we can make toward this annual objective?
| Annual OKR Characteristic | Description |
|---|---|
|
Strategic scope
|
Covers the full strategic direction for the year; describes a meaningful transformation in market position, capability, or performance
|
|
Directional rather than prescriptive
|
Defines the destination without specifying the exact quarterly path; the path is determined cycle by cycle
|
|
Set by senior leadership
|
Company-level annual OKRs are owned by the CEO and executive team; they set the context within which quarterly OKRs are designed
|
|
Reviewed quarterly
|
Annual OKRs are formally reviewed at the end of each quarter to assess cumulative progress and recalibrate the remaining quarters
|
|
Carries across all four quarters
|
Each quarterly OKR cycle should produce measurable advancement on the annual OKR; progress compounds across the year
|
The Reset: What It Is and Why It Matters
The cycle reset is one of the most disciplinarily important and most frequently mishandled aspects of OKR implementation. A reset is the formal act of closing one OKR cycle, assessing its outcomes, and deliberately choosing new or updated OKRs for the next cycle. It is not the automatic continuation of existing objectives, the mechanical rolling forward of unachieved Key Results, or the minor tweaking of last quarter’s targets. It is a structured transition that requires active judgment: what did we achieve, what did we learn, what has changed in our environment, and what is therefore the most important change to drive in the next 90 days?
The reset serves several critical functions simultaneously. First, it closes the accountability loop: every OKR cycle ends with a scored assessment that is honest about what was and was not achieved, creating a record of execution quality that informs future ambition-setting. Second, it creates the opportunity for strategic recalibration: circumstances change within a quarter — competitive moves, market shifts, product discoveries, customer feedback — and the reset is the moment when those changes are formally incorporated into the next cycle’s priorities rather than ignored in favour of inertia. Third, it prevents objective staleness: an objective that was highly relevant in Q1 may be substantially less important by Q3 if progress has already been made or if the strategic context has shifted. The reset forces a fresh assessment of relevance rather than allowing the organisation to coast on inherited priorities.
| Reset Activity | Purpose | Output |
|---|---|---|
|
Grade all Key Results (0.0–1.0)
|
Create an honest, evidence-based record of what was achieved
|
Scored OKR set for the closed quarter
|
|
Retrospective discussion
|
Understand why results were or were not achieved; separate execution quality from target ambition quality
|
Documented lessons and root causes
|
|
Annual OKR progress review
|
Assess cumulative progress toward annual objectives; determine whether annual targets remain appropriate
|
Updated annual OKR confidence score and remaining-year plan
|
|
Environmental scan
|
Identify changes in competitive landscape, customer needs, or internal capabilities that should influence next-quarter priorities
|
Strategic context update for planning session
|
|
Next-quarter OKR drafting
|
Design new objectives and Key Results that reflect current state, lessons learned, and highest-priority next change goals
|
Draft OKR set for next quarter, ready for alignment and finalisation
|
Rolling Over vs. Resetting: A Critical Distinction
The single most common time-horizon mistake in OKR implementation is rolling over — copying last quarter’s unachieved OKRs into the next quarter without deliberate reassessment. Rolling over feels efficient: the objectives already exist, the Key Results are already defined, and the team is already familiar with them. In practice, rollover is a signal that the OKR system has stopped functioning as a change driver and has become an administrative process. It indicates that either the targets were set too ambitiously to be reached in a single quarter without a multi-quarter plan, that the team does not have a structured reset process, or — most damagingly — that the objectives were never genuinely change-oriented to begin with and therefore cannot be completed regardless of how many quarters they are rolled over.
The appropriate alternative to rolling over is deliberate continuation: if a multi-quarter change initiative requires more than one 90-day cycle to reach its desired state, each quarter should have its own freshly designed OKR that represents the most important next step in that initiative. The Key Results change each quarter to reflect the current stage of the journey rather than repeating the same targets quarter after quarter. This distinction — between rolling over unchanged OKRs and deliberately staging a multi-quarter initiative through freshly designed quarterly OKRs — is the difference between an organisation that is making measured progress through planned change and one that is perpetually falling short of recycled targets.
Rollover (WRONG) vs. Staged Continuation (CORRECT):
Annual Objective: Become the market leader in enterprise customer satisfaction
ROLLOVER APPROACH (wrong):
Q1 Key Result: Increase NPS from 38 to 65 → Score: 0.4 (reached 50)
Q2 Key Result: Increase NPS from 38 to 65 → Same KR copied; no learning applied
Q3 Key Result: Increase NPS from 38 to 65 → Same KR again; demoralising
STAGED CONTINUATION APPROACH (correct):
Q1 Key Result: Increase NPS from 38 to 50 → Score: 1.0 (achieved)
Identify top 3 root causes of detractor scores
Q2 Key Result: Increase NPS from 50 to 58 → Building on Q1 baseline
Resolve top 2 root causes identified in Q1
Q3 Key Result: Increase NPS from 58 to 65 → Final push toward annual target
Achieve NPS above all identified competitors
OKR Time Horizon vs. Other Goal-Setting Frameworks
The quarterly-plus-annual time horizon of OKRs is a deliberate departure from the annual-only cadence of traditional management frameworks such as MBO (Management by Objectives) and the annual budgeting and performance review cycle. The slower cadence of annual-only frameworks means that misaligned efforts, flawed assumptions, and poor execution are discovered only after a full year has elapsed — by which point the cost of correction is high and the window for impact has largely closed. OKRs compress this feedback loop from 12 months to 90 days, multiplying by four the number of opportunities to assess progress, learn from failures, and recalibrate direction within a single year.
| Framework | Primary Cadence | Reset Frequency | Feedback Loop Length | Misalignment Detection Speed |
|---|---|---|---|---|
|
OKR
|
Quarterly + Annual
|
Every 90 days
|
90 days
|
Fast — issues caught within the quarter
|
|
MBO (Management by Objectives)
|
Annual
|
Once per year
|
12 months
|
Slow — issues discovered at year-end review
|
|
Balanced Scorecard (BSC)
|
Annual strategy; quarterly review
|
Annual strategy reset; quarterly metric review
|
Quarterly for metrics; annual for strategy
|
Medium — metrics reviewed quarterly but strategy annual
|
|
Agile Sprint Goals
|
2–4 weeks
|
Every sprint
|
2–4 weeks
|
Very fast — suited to product development, not strategy
|
|
Annual Budget / Business Plan
|
Annual
|
Once per year
|
12 months
|
Very slow — budget variances reported but rarely actioned
|
Time Horizon and Organisational Level
The appropriate balance between annual and quarterly OKRs varies by organisational level. Company and senior leadership OKRs tend to carry more annual-horizon objectives because strategic change at that level requires sustained multi-quarter effort and the stability of consistent direction. Team and individual OKRs tend to be predominantly quarterly because the work is more specific, the feedback loops are faster, and the connection between action and measurable outcome is more direct. This difference in time-horizon emphasis by level is not a contradiction in the framework — it is a reflection of the different change cycles that operate at different levels of an organisation.
| Organisational Level | Dominant Time Horizon | Rationale |
|---|---|---|
|
Board / CEO
|
Annual (3–5 year vision informs annual)
|
Strategic transformation requires sustained multi-year direction; annual OKRs provide stability
|
|
Executive / C-Suite
|
Annual + Quarterly
|
Annual strategic ownership; quarterly execution accountability on company-level priorities
|
|
Department / Function Head
|
Quarterly (aligned to annual)
|
Functional delivery is primarily quarterly; annual gives direction, quarterly drives action
|
|
Team / Squad
|
Quarterly
|
Team execution is fastest-moving; 90-day cycles match the rhythm of product and operational work
|
|
Individual Contributor
|
Quarterly
|
Individual contribution and development goals benefit from frequent check-ins and reset opportunities
|
Time Horizon and Investor Context
For investors and board members evaluating an organisation’s execution capability, the discipline of the OKR time horizon and reset cadence is a meaningful quality signal. An organisation that can demonstrate a consistent history of quarterly OKR cycles — with honest grading, documented retrospectives, and evidence of learning applied to subsequent cycles — is demonstrating execution maturity that goes beyond the ability to set goals. It is showing that the organisation can close the loop between intent and outcome repeatedly, at speed, and with sufficient self-awareness to improve its approach each cycle. This compounding execution capability is one of the most durable competitive advantages a management team can develop, and its presence or absence is visible in the time-horizon discipline of the OKR system.
Related Terms
- OKR (Objectives and Key Results) — The goal-setting framework that uses quarterly and annual time horizons as core structural features; the time horizon is inseparable from the framework’s change-driving purpose
- OKR Purpose — To drive change toward a new desired state; the time horizon provides the deadline discipline that transforms aspiration into accountable commitment
- OKR Cycle — The complete planning–execution–grading–retrospective–reset sequence that repeats on a quarterly cadence; the foundational rhythm of the OKR operating system
- Committed OKR — A change goal for which full achievement (score 1.0) is expected within the time horizon; resources are fully allocated and the deadline is firm
- Aspirational OKR — A stretch change goal for which a score of 0.6–0.7 within the time horizon is considered strong; designed to push the organisation beyond comfortable extrapolation
- Reset — The deliberate act of closing a completed OKR cycle, grading outcomes, learning from results, and choosing new OKRs for the next cycle; prevents rollover and maintains the framework’s change orientation
- Rollover — The failure mode of copying unachieved OKRs from one cycle to the next without reassessment; a sign that the OKR system has become administrative rather than change-driving
- OKR Scoring — The 0.0–1.0 assessment of Key Result achievement conducted at the end of each cycle as part of the reset process; provides the evidence base for retrospective learning
- MBO (Management by Objectives) — The predecessor framework to OKRs; operates on an annual-only cadence, producing a feedback loop four times slower than the quarterly OKR cycle
- SMART Framework — Goal-setting criteria that OKR Key Results should satisfy; the Time-bound criterion directly corresponds to the OKR time horizon discipline
- Balanced Scorecard (BSC) — A strategic measurement framework that operates on an annual strategy horizon with quarterly metric reviews; complementary to OKRs, which drive the focused quarterly changes that improve BSC metric performance
Disclaimer
The information provided in this article is intended for educational and informational purposes only. Descriptions of OKR time horizon conventions, planning cadences, and reset methodologies reflect widely published practitioner literature, publicly available resources, and general industry conventions as of the time of writing. Specific cadence structures, the balance between annual and quarterly OKRs, and reset processes vary significantly across organisations, industries, and cultural contexts. References to specific organisations and practitioners are for educational purposes only. Nothing in this article constitutes management consulting, strategic advisory, legal, financial, or professional advice. Readers should conduct independent research and consult qualified professionals before implementing goal-setting frameworks within their organisations. Uninformed Investors makes no representation as to the accuracy, completeness, or timeliness of the information contained herein.
OKR Time Horizon definition is complete. The article covers: the logic of the 90-day quarterly cadence, the role of annual OKRs as strategic anchors, a full quarterly calendar structure, the reset process and its five activities, the critical distinction between rolling over and staged continuation with a worked code example, comparison of OKR time horizon against MBO, BSC, Agile, and annual budgeting, time horizon differences by organisational level, and investor context.