// framework core

Key Result

A Key Result is a measurable outcome (1–4 per Objective, average 2) that tells you whether you're progressing. Preferred formula: [Increase/Decrease] [Metric] from X to Y.

The best Key Results use fast-moving metrics that matter, informed by a metric tree. When targets can't be set yet, use a baseline Key Result; when direct metrics are too slow, use Proxy Metrics or see Slow-Moving Metrics. Avoid Task-Based Key Results. Stretch goals are labelled as Aspirational Targets, and each KR deserves a narrative. See also Target Setting. When you lack the insight to set a Key Result at all, do the discovery first, via Dual Track Discovery, not discovery KRs.

WORKED EXAMPLE

Weak: "Launch the new onboarding flow." That is a task; launching proves nothing changed for users.
Real: "Increase Day-7 activation rate from 31% to 45%." A baseline, a target, and a metric that only moves if the work actually worked.

How many Key Results per Objective? +

Two to four. One is usually too narrow a definition of success; five means the Objective is trying to be a department plan.

What if we cannot measure the outcome yet? +

Then you need discovery before targets, not a made-up number. Run the learning work first, and use a leading indicator or a defensible proxy while the real metric matures.

From the ZOKRI OKR Handbook, the methodology we install and maintain.

// connected concepts
Objective → Task-Based Key Results → Aspirational Targets → Explore all 122 notes →
// put it to work

Reading about method is not the same as running it. We install this system and build the capability that stays.

Stress-test your OKRs with the free AI Coach →