OKR Purpose: Drive Change Toward a New Desired State

The defining purpose of the OKR (Objectives and Key Results) framework is to drive change toward a new desired state. This single sentence captures what separates OKRs from other management and measurement tools: OKRs are not designed to monitor the ongoing health of existing operations, track historical performance, or report on business-as-usual activity. They are designed to move an organisation, a team, or an individual from where it currently is to somewhere meaningfully better — and to do so within a defined, time-bounded period.

This change-oriented purpose is embedded in the structure of every OKR unit. The Objective names the desired state — a future condition that does not yet exist but is worth pursuing. The Key Results define what measurable evidence will confirm that the desired state has been reached. Together, they create a complete change management instrument: a direction, a destination, and a verification standard. Without the change orientation, an Objective becomes a status description and Key Results become routine reporting metrics — tools for measuring where you are, not tools for getting somewhere new.

Understanding OKRs as change instruments — rather than measurement instruments — resolves the most common sources of confusion in OKR implementation. It explains why OKRs should be challenging rather than comfortable: a target that represents no meaningful departure from the current state is not driving change, it is ratifying continuity. It explains why OKRs should be time-bound: change without a deadline is aspiration without accountability. And it explains why OKRs should be reset each cycle: once the desired state has been reached, it becomes the new baseline from which the next cycle of change begins.

Change Orientation vs. Monitoring Orientation

The change purpose of OKRs is most clearly understood in contrast to the monitoring purpose of KPIs. KPIs (Key Performance Indicators) exist to answer the question: “Are we performing at the level we should be?” They track ongoing processes, operational health, and business performance against established benchmarks. They are continuous, persistent, and backward-looking — they confirm what has already happened. OKRs exist to answer a different question: “Are we making progress toward a new and better state?” They are episodic, time-limited, and forward-looking — they drive what is about to happen.

Dimension	OKR (Change Instrument)	KPI (Monitoring Instrument)
Core Question	Are we moving toward a new desired state?	Are we performing at the expected level?
Orientation	Forward-looking — defines future destination	Backward-looking — confirms past performance
Time Horizon	Bounded — quarterly or annual cycle, then reset	Continuous — tracked indefinitely
Baseline Relationship	Explicitly departs from current baseline toward a new target	Measured against a stable historical benchmark
Success Condition	Desired state reached; OKR retired or replaced with a new change goal	Metric stays within acceptable range; no endpoint
Relationship to Each Other	OKR Key Results often use KPI metrics as the measurement vehicle for change	KPIs provide the data that OKRs target for improvement

What “Desired State” Means in Practice

The phrase “desired state” in the OKR purpose statement is deliberate and precise. A desired state is not a task completed, a project delivered, or a process run — it is a condition of the world that is meaningfully different from the condition that exists today. It describes a changed reality: customers who are more satisfied, a product that is more widely adopted, a team that is more capable, a market position that is more competitive. The desired state is the answer to the question: “If this OKR succeeds, what will be true that is not true today?”

Articulating the desired state clearly is the most important act in OKR design. Organisations that skip this step — that write objectives as project descriptions or Key Results as task lists — lose the change orientation entirely. “Launch the new customer portal” describes an activity. “Reduce average customer support resolution time from 72 hours to 8 hours” describes a desired state. The first tells a team what to build; the second tells a team what to achieve. The distinction determines whether the OKR drives genuine change or merely generates activity.

Desired State Test — Ask: "What will be TRUE that is not true today?"

Activity-framed (WRONG):
  Objective:    Complete the onboarding redesign project
  Key Result:   Launch new onboarding flow by end of Q2
  Key Result:   Conduct 10 user testing sessions
  → These describe outputs and tasks, not a changed state

Desired-state-framed (CORRECT):
  Objective:    Make it effortless for new customers to experience our product's value
  Key Result:   Reduce time-to-first-value from 14 days to 3 days
  Key Result:   Increase day-30 activation rate from 38% to 65%
  Key Result:   Achieve onboarding CSAT score of ≥4.6/5.0
  → These describe a measurably different future condition

Types of Change OKRs Drive

The change that OKRs drive can take several distinct forms depending on the strategic context, the level of the organisation setting the OKR, and the time horizon involved. Recognising which type of change an OKR is designed to produce helps set appropriate ambition levels, select the right Key Results, and calibrate realistic expectations for the pace of progress within a single quarter or annual cycle.

Change Type	Description	Example Objective	Typical OKR Type
Performance Improvement	Moving an existing metric from its current level to a significantly better level	“Dramatically improve customer retention in our SMB segment”	Committed or aspirational
Capability Building	Developing a new organisational, team, or individual capability that does not yet exist	“Build a world-class data-driven sales culture”	Aspirational — multi-quarter journey
Market Expansion	Entering a new customer segment, geography, or product category	“Establish a meaningful presence in the enterprise security market“	Aspirational — high uncertainty
Problem Resolution	Eliminating a specific operational problem or failure mode	“Make product reliability a competitive advantage”	Committed — specific measurable target
Cultural or Behavioural Change	Shifting how people work, collaborate, or make decisions across the organisation	“Foster a culture where every team acts on customer feedback within 48 hours”	Aspirational — hard to measure directly

Why Change Requires Time-Bounding

The change purpose of OKRs is inseparable from the time-bounding discipline of the framework. A desired state without a deadline is a wish. The quarterly or annual OKR cycle creates the conditions under which genuine change becomes possible: a defined window of focused effort, a clear endpoint at which progress is assessed, and a structured transition into the next cycle of change. Time-bounding also creates the urgency that distinguishes OKR-driven organisations from those with perpetually deferred improvement goals. When a team commits to reaching a new desired state by the end of the quarter, the 90-day clock transforms aspiration into operational pressure — resources are allocated, priorities are set, and trade-off decisions are made in service of the defined change goal.

The quarterly cadence is not arbitrary. It is long enough to make meaningful progress on ambitious goals that require sustained effort, coordination, and investment. It is short enough to maintain a sense of urgency, catch misaligned efforts before they compound, and allow the organisation to course-correct before an entire year is lost pursuing a flawed hypothesis. The combination of ambition and time-bounding is what gives OKRs their characteristic tension — the productive discomfort of a challenging goal and an approaching deadline that, when managed well, drives the focused effort required to actually reach new and better places.

Change Purpose and the Stretch Goal Principle

The change purpose of OKRs directly explains why stretch goals are a structural feature of the framework rather than an optional stylistic choice. If the purpose of an OKR is to drive change toward a new desired state, then a target that merely continues the existing trajectory — a 5% improvement when the historical rate is 4% — is not driving meaningful change. It is extrapolating from the status quo. Stretch goals force a qualitative departure: they demand that teams think and act differently, because incremental improvements to existing approaches will not be sufficient to reach the target. This is the mechanism by which OKRs produce innovation and transformation rather than merely optimised continuity.

Google’s principle that a score of 0.7 is a strong outcome for an aspirational OKR reflects this logic: if the desired state is genuinely new and meaningfully ambitious, reaching 70% of the way there in a single quarter represents real change. The remaining 30% becomes the baseline from which the next cycle’s change goal begins. Over multiple cycles, this compounding of partial-but-meaningful progress toward successively more ambitious desired states is how organisations achieve transformation — not through a single heroic leap, but through a disciplined cadence of directed, measured change efforts.

OKR Purpose Across Organisational Levels

The change purpose of OKRs applies consistently across all levels of the organisational hierarchy, but the nature and scale of the desired state differs significantly by level. Company-level OKRs define strategic transformation — changes to market position, business model, or organisational capability that play out over years of compounding quarterly progress. Team-level OKRs define functional improvement — changes to process performance, product quality, or customer experience that can be meaningfully advanced within a quarter. Individual OKRs define personal development and contribution — changes to skill levels, working relationships, or specific deliverable quality that reflect individual growth and accountability.

Level	Scale of Desired State	Example Change Goal	Time to Full Realisation
Company / Corporate	Strategic — market position, business model, organisational capability	“Become the default infrastructure platform for mid-market financial services”	Multiple years of compounding quarterly OKRs
Department / Function	Functional — process excellence, team capability, customer experience dimension	“Make our customer success team the highest-rated in our competitive set”	2–4 quarters of focused effort
Team / Squad	Operational — specific product, process, or performance improvement	“Eliminate onboarding as a source of early churn”	1–2 quarters with clear milestones
Individual	Personal — skill development, relationship quality, specific contribution	“Become the go-to expert on enterprise security requirements within the sales team”	1 quarter to 1 year depending on depth

What Happens When OKR Purpose Is Lost

When organisations lose sight of the change purpose of OKRs, the framework degrades into a reporting system. The symptoms are consistent and recognisable: objectives are written as project descriptions or departmental mission statements rather than aspirational change goals; Key Results are populated with routine operational metrics that will be tracked regardless of whether an OKR exists; targets are set at or slightly above current performance to ensure high scores; and the OKR cycle becomes a quarterly administrative exercise in documenting business-as-usual rather than a mechanism for driving the organisation to genuinely new places.

This degradation is the most common failure mode in OKR adoption. It typically occurs when OKRs are introduced as a top-down compliance exercise rather than a bottom-up change commitment; when they are linked to performance reviews and compensation, creating an incentive to sandbagging targets; or when the organisation lacks the strategic clarity to articulate what it actually wants to change. Restoring the change purpose requires revisiting each OKR with the fundamental question: “If we hit these Key Results, what will be meaningfully different about our business, our customers’ experience, or our team’s capabilities that is not true today?” If the honest answer is “not much,” the OKR has lost its purpose and needs to be rewritten.

Related Terms

- OKR (Objectives and Key Results) — The goal-setting framework whose defining purpose is to drive change toward a new desired state; the Objective names the desired state, the Key Results verify its achievement
- KPI (Key Performance Indicator) — The complementary monitoring tool whose purpose is to track ongoing business health rather than drive change; OKRs use KPI metrics as measurement vehicles for change targets
- Desired State — The specific future condition an OKR is designed to achieve; a measurably different reality from the current baseline
- Stretch Goal — An aspirational target set beyond comfortable extrapolation of current performance; the mechanism by which OKRs force qualitatively different approaches rather than incremental optimisation
- Committed OKR — An OKR for which the desired state change is fully resourced and expected to be achieved (score 1.0); applies to operationally critical change goals

Aspirational OKR

SMART Framework — Goal-setting criteria (Specific, Measurable, Achievable, Relevant, Time-bound) that OKR Key Results should satisfy to properly define and verify the desired state change
North Star Metric — The single top-level metric representing an organisation’s core value creation; company-level OKRs typically target change in the conditions that drive the North Star Metric
Balanced Scorecard (BSC) — A strategic measurement framework that defines the ongoing performance standards OKRs are designed to improve; BSC metrics provide the before-state baseline from which OKR desired states depart
Goodhart’s Law — The principle that when a measure becomes a target it ceases to be a good measure; particularly relevant when OKRs are tied to compensation, which undermines the honest change orientation of the framework

Disclaimer

The information provided in this article is intended for educational and informational purposes only. Descriptions of the OKR framework’s purpose, design principles, and implementation guidance reflect widely published practitioner literature, publicly available resources, and general industry conventions as of the time of writing. The OKR methodology was developed by Andy Grove at Intel and popularised by John Doerr; references to their work are for educational purposes. Implementation approaches, cadences, and scoring conventions vary significantly across organisations, industries, and cultural contexts. 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 Purpose definition is complete. The article covers: the change orientation vs. monitoring orientation distinction, the meaning of “desired state” with a practical activity vs. desired-state framing example, types of change OKRs drive, why time-bounding is inseparable from the change purpose, the stretch goal principle and the 0.7 scoring logic, how the change purpose applies across organisational levels, and what failure looks like when the change purpose is lost.

Uninformed Investors