In Scrum, your focus is on executing the sprint backlog. You have a list of user stories and tasks, and the goal is to complete that work. This is an output-driven process: you produce code, features, and bug fixes. It's concrete and satisfying, but it doesn't always answer the most important question: did any of it matter?

This is where Objectives and Key Results, or OKRs, change the game. OKRs shift your focus from outputs (the 'what' you did) to outcomes (the 'why' it mattered). Instead of just shipping a new feature, you aim to change user behavior, improve a business metric, or achieve a strategic goal. An OKR isn't a to-do list; it's a framework for defining and tracking what you want to accomplish and how you'll measure success.

Every OKR has two core components: the Objective and the Key Results. They work together to create a clear, ambitious, and measurable goal.

The Objective is the qualitative, inspirational statement. It answers the question, "What do we want to achieve?" It should be memorable and motivating, something that rallies the team around a common purpose. Think of it as the destination you're trying to reach. It’s ambitious but not abstract; it’s a concrete direction for a specific period, usually a quarter.

Key Results, on the other hand, are the quantitative metrics that measure your progress toward the Objective. They answer the question, "How will we know if we’ve achieved our objective?" KRs are always numbers-based. They make the objective concrete and verifiable. You either hit the number, or you don’t. There’s no ambiguity.

This is the critical difference from a simple task list. A task is an activity, like "launch new login page." A Key Result is an outcome, like "Reduce login failures by 20%." The first is an output; the second is a measurable impact.

To maintain focus, a good rule of thumb is to limit yourself to three Objectives per quarter. Each Objective should then have about three Key Results. This "3x3" structure forces you to prioritize what's most important. If you have ten objectives, you really have no objective at all.

This constraint prevents you from spreading your resources too thin and ensures your team has a clear understanding of its top priorities. Let's look at an example.

OKRs are designed to be ambitious. They should push you and your team beyond what you think is possible. This is where the concept of stretch goals comes in. A standard practice is to consider achieving 70% of a Key Result as a success. If you're consistently hitting 100%, your OKRs aren't ambitious enough.

This creates a culture of striving for greatness without the fear of failure. It separates performance evaluation from goal achievement, encouraging teams to take risks. Some organizations even set "moonshots" – hugely ambitious goals that might have a low probability of success but would be revolutionary if achieved. For example, a moonshot might aim for a 10x improvement, while a more typical stretch goal aims for a 2x improvement.

Understanding this structure is the first step. By separating your inspirational goals from the hard data that proves them, you create a powerful system for driving meaningful progress.