10 OKR Rules You Can Safely Break
OKRs started as a simple idea from Andy Grove at Intel, laid out in his book High Output Management: decide what matters, and measure whether you're getting there. Over the decades, a lot of rules got bolted on top of that simple idea, some useful, many not. If you're new to OKRs and feel overwhelmed by all the "you must" statements floating around online, here are ten you can safely ignore.
1. You Must Grade at 0.7
The idea that a good Key Result score lands around 0.7 comes from Google's specific culture of deliberately ambitious "moonshot" goals, a practice John Doerr documents in Measure What Matters. Most organizations don't operate that way, and don't need to. If your team consistently hits 1.0, that's fine, as long as your targets were genuinely meaningful and not sandbagged.
2. Every Team Must Have 3 to 5 OKRs
This is a reasonable default, not a law. A small team might do well with a single focused Objective for a quarter. What matters more than the exact count is whether the team can actually hold all of them in their head. If they can list their OKRs from memory, you're probably fine.
3. OKRs Must Never Change Mid-Cycle
Rigid adherence to a locked quarter sounds disciplined, but it can also mean chasing a target everyone already knows is wrong. If the market shifts or a Key Result turns out to be poorly designed, adjust it. The goal is a useful plan, not a monument to the plan you made 6 weeks ago.
4. Objectives Must Be Qualitative and Key Results Purely Quantitative
This is a helpful starting guideline, not a strict boundary. Some Objectives read perfectly well with a number attached, and some Key Results are better expressed as a clear milestone than a raw metric. Don't force awkward phrasing just to satisfy a textbook definition.
5. Individual OKRs Are Mandatory
Many organizations get real value from OKRs at the company and team level and skip individual OKRs entirely, folding personal goals into regular performance conversations instead. Individual OKRs can work well, but they aren't a required layer of the framework. We cover this trade-off in more depth in our post on individual OKRs.
6. You Need a Dedicated OKR Champion or Committee
Useful at large organizations, unnecessary overhead at small ones. A team of twenty people doesn't need a governance committee to run OKRs. It needs a simple process and a tool that doesn't get in the way.
7. All Key Results Must Be Weighted Equally, or Must Be Weighted at All
Weighting can help when some Key Results clearly matter more than others, but it's optional complexity. Plenty of teams run OKRs successfully without ever assigning weights.
8. Every Objective Needs Exactly One Owner
Single ownership is a good default for accountability, but cross-functional Objectives sometimes genuinely need shared ownership across two teams. Force a single name onto it and you often just create a title without real accountability.
9. Check-ins Must Happen Weekly, No Exceptions
Weekly works well for fast-moving teams. Slower-moving initiatives, or smaller organizations, sometimes do better with a biweekly rhythm. What matters is consistency, not the specific interval. This is worth pairing with our thoughts on finding the right OKR cadence.
10. You Must Use the Exact Google Format
Google's version of OKRs is one implementation of a much older idea rooted in management by objectives and Andy Grove's work at Intel. It's a good reference point, not scripture. Adapt the format to fit how your organization actually communicates.
The Real Rule
If a rule is helping your team focus and stay honest about progress, keep it. If it's adding friction without adding clarity, drop it. That flexibility is exactly what Easy OKR is built around: a lightweight structure that adapts to how your team actually works, instead of forcing your team to adapt to the tool.