The Real Discipline Behind OKRs Is Deciding What Not to Do

Most leadership teams do not suffer from a shortage of goals. They suffer from an unwillingness or inability to prioritize and rank them. 

During planning, everything important gets added: growth, margin, talent, customer experience, technology, culture. The result is a plan that sounds ambitious and behaves like a list. John Doerr’s Measure What Matters offers Objectives and Key Results as a remedy. Its deeper value is not just defining and documenting goals. It is forcing choices leaders might otherwise postpone or avoid. 

In my work with leaders, this is where OKRs earn their keep. Used well, they expose ambiguity, sharpen management conversations, and make ownership visible. Used poorly, they produce a cleaner spreadsheet, but the same churn and confusion. 

An Objective Is a Choice, Not a Catalog 

The OKR formula is straightforward. Objectives define what the organization intends to achieve. Key Results define how progress toward those Objectives will be seen and measured. The hardest work, however, comes before the wording: What is most important and will receive focus disproportionate attention now? 

Limiting a team to three to five objectives is not a formatting rule. It is an operating constraint. A team with ten top priorities has not made strategy visible; it has distributed anxiety. 

Leaders resist narrowing because work outside the OKRs still matters. Customers, payroll, compliance, quality, and safety do not disappear. But OKRs are not an inventory of everything the business must do. They identify the few outcomes that most need coordinated effort and improvement to improve the business; normal business operations remain governed through established responsibilities and tactical metrics. 

Ask: If we add this objective, what will receive less time, money, or attention? If the answer is nothing, the plan is an additive wish list. Real focus has an opportunity cost. 

A Key Result Should Change the Management Conversation  

Weak Key Results describe activity: launch the program, meet with customers, install the system. Those actions may be necessary, but completing them does not prove that the objective advanced. 

Stronger Key Results specify an observable outcome within a defined period. Their value is not precision for its own sake. They allow a team to notice quickly when planned effort is not producing the intended effect and to intervene or change course while time remains. 

Measurement can also create false certainty. Some critical work will never yield a perfect number. Even then, the discipline forces better questions: What evidence would show the progress we need? Which leading indicators matter? What results would make us revisit the assumptions behind the objective? 

A quarterly review should be more than a red, yellow, or green score used to assign blame. It should focus the conversation:

Alignment Is Not Announced. It Is Built Through Ownership.  

A company can publish elegant OKRs and remain badly misaligned. Visibility helps, but a shared vocabulary is not the same as shared ownership. 

Cascading works when teams can see the relationship between their work and the enterprise objectives, and when responsibility is precise. Who owns the result? Who contributes? Who decides when priorities conflict? When will progress be reviewed? Without those answers, an OKR is a statement of hope. 

Driving goals into an organization’s DNA sounds compelling. The practice is more ordinary: maintain a regular cadence, keep commitments visible, discuss progress candidly, and stop work that no longer serves the priority. That is why frequent, ongoing performance conversations are much more useful than an annual or quarterly look backward. 

Executive behavior matters most. If leaders keep introducing side priorities and projects, teams learn that OKRs are optional. If every miss triggers punishment, people will write Key Results they can safely achieve. When leaders ask hard questions, adjust resources, and make tradeoffs visible, OKRs become visible and honest coordination and collaboration mechanisms. 

That is not micromanagement. It is management making priorities and consequences clear. 

The Question to Carry Into Your Next Planning Cycle  

The promise of Measure What Matters is not that a framework will do the thinking for us. It is that the framework makes difficult thinking and real prioritized choices harder to avoid. 

Before the next planning cycle, ask your leadership team: Which three outcomes would materially change the business? How will we know? What will we stop or slow down? Who owns each result? When will we have the first honest review? 

Then ask the question that matters most: Are our goals helping the organization choose, learn, and act, or are they simply giving everyone more to report?