Definition
A goal-setting framework popularized by Intel and Google. An Objective is a qualitative, inspiring goal; Key Results are 2-5 quantitative measures that define success for that objective. OKRs are typically set quarterly and cascaded across the organization. PMs use OKRs to communicate desired outcomes (not outputs), align teams, and create accountability without micromanaging how work gets done.
Why It Matters for Product Managers
Understanding okr is critical for product managers because it directly influences how teams prioritize work, measure progress, and deliver value to users. PMs use OKRs to communicate desired outcomes (not outputs), align teams, and create accountability without micromanaging how work gets done. Without a clear grasp of this concept, PMs risk making decisions based on assumptions rather than evidence, which can lead to wasted engineering effort and missed market opportunities.
How It Works in Practice
Teams typically implement this framework by following a structured process:
The goal is not to follow okr dogmatically but to use it as a thinking tool that brings structure to decisions that would otherwise rely on gut feel.
Common Pitfalls
Related Concepts
To build a more complete picture, explore these related concepts: North Star Framework, Empowered Teams, and Initiative Roadmap. Each connects to this term and together they form a toolkit that product managers draw on daily.