Operating Cadence
The Operating Cadence Behind Real OKRs
OKRs are misunderstood as a planning system. They're actually a focus mechanism — and the difference is in the operating cadence around them. The six-step framework, the seven failure modes, and how RGM runs OKRs in client engagements.
OKRs are not a planning system. They are a focus system.
Most teams adopt OKRs and then complain that they don't work. The complaint is almost always self-inflicted.
OKRs implemented as a quarterly planning ritual — write objectives in January, file them in a wiki, dust them off in March, declare them complete in April — produce no operating value. OKRs implemented as a continuous focus mechanism — written with care, socialized aggressively, reviewed weekly, post-mortemed honestly — produce strategic discipline other planning frameworks can't match.
The Reforge six-step framework[1] is built around this distinction. The mechanics matter less than the cadence. The cadence matters less than the discipline of treating OKRs as a loop, not a document.
What OKRs actually are
OKRs have two components, both load-bearing.
The Objective is a qualitative statement of what you want to accomplish in the time window. Good objectives are ambitious, time-bound, and outcome-oriented. They describe a state of the world that will be true if you succeed. Bad objectives are vague, perpetual, or activity-oriented.
"Improve marketing" is bad. "Establish RGM as the most-cited growth marketing brand in B2B SaaS by end of Q3" is good.
The Key Results are numerical expressions of progress toward the objective. Good key results are measurable, time-bound, and outcome-oriented. They aren't activities. They aren't metrics for their own sake. They are observable changes in the world that would not occur unless you made progress.
An objective without key results is a goal with no scoreboard. Key results without an objective are a metric stack with no narrative.
Step 1 — Draft outcome-oriented OKRs
The hardest step. Most teams write activity-oriented OKRs: "Launch the new landing page." "Run 10 webinars." "Ship feature X." These are tasks. They confuse motion with progress.
Outcome-oriented OKRs describe what changes in the world if the activities succeed. "Lift MQL volume from $200/MQL to $120/MQL while holding MQL→SQL conversion at 38%." That's an outcome. The activity is downstream.
Reforge's discipline:[1] 1–4 objectives per cycle, 2–4 key results per objective. More diffuses focus. A list of 8 key results is a status report disguised as a plan.
Step 2 — Run on a quarterly cadence
Reforge's recommended cadence[1] is quarterly review and revision. Annual is too coarse. Monthly is too granular. Quarterly fits human attention spans and business reality.
The quarterly process: in the last week of the prior quarter, review progress, retire completed OKRs, evolve still-active ones, and draft new ones. The team enters the new quarter with a complete OKR set on day one.
The mistake teams make: writing OKRs during week 2. By the time they're finalized, week 4 starts, and you've lost 30% of the cycle to planning.
Step 3 — Share, align, socialize
An OKR that lives in a single document and is read once is operationally inert. Socialization is what makes OKRs influence behavior.
Reforge prescribes:[1] write OKRs with input from your team, not in isolation. Cross-functional peer alignment happens before they're finalized. The team expected to deliver has a hand in defining.
Beyond the writing team, OKRs need socialization up the chain, across the chain, and down the chain. Structured kickoff meetings. Interlocks with adjacent teams. Written narrative explaining the choices.
Socialization is not "share the wiki link in Slack."
Step 4 — Launch the OKRs
Launching means more than publishing. It means setting up the reporting cadence, the dashboard, the standup ritual, and the decision-making structure that will use the OKRs during the quarter.
Concretely: a single dashboard showing current state of every key result. Weekly check-ins (15 minutes per OKR is enough). A clear escalation path when an OKR is materially off-track.
Step 5 — Reinforce and review
Mid-quarter discipline separates OKR-fluent teams from OKR-cosmetic teams.
Reinforcement means visible attention from leadership. If your CEO references the OKRs in every all-hands; if your team lead opens every weekly meeting with the OKR dashboard; if OKRs are the explicit basis for prioritization conversations — they're alive.
If none of that happens, the OKRs are dead by week 6.
Review means honest weekly assessment. Off-track key results need flagging, not hiding. The point isn't to make everything look green. The point is to detect off-track work early enough to fix it.
Step 6 — Conduct quarterly post-mortems
End-of-quarter, the team runs a structured retrospective. Three questions:
- Did we hit the key results?
- Did hitting (or missing) them move the objective?
- What did we learn about how we plan, predict, and execute?
The third question is the most important. OKR post-mortems are training data for the team's product intuition.[1] Over time, a team that takes post-mortems seriously gets dramatically better at predicting what's achievable and what unexpectedly breaks. A team that skips them never accumulates that intuition.
Seven common OKR failure modes
Sandbagging. Setting key results so low they're certain to be hit. 100% completion rates and zero strategic value.
Activity disguised as outcome. "Ship 4 landing page tests" is activity. "Lift CVR from 2.4% to 3.6%" is outcome.
Too many OKRs. 12 objectives means no priorities — just a list.
OKR fatigue. When OKRs become a tax instead of a tool, the team disengages.
No socialization. Adjacent teams don't know your OKRs, so their work doesn't ladder up.
No post-mortem. Cycle restarts as if nothing happened. The team never learns.
Tied to comp. Once OKRs become the basis for compensation, teams immediately sandbag.
RGM experts say
The most common cause of OKR failure we see: leadership using OKRs to measure individual performance. Once OKRs become the basis for compensation or promotion, teams sandbag. Sandbagged OKRs produce 100% completion rates and zero strategic value.
The fix: separate OKRs from individual performance evaluation. OKRs are aspirational strategic targets. Hitting 70% counts as success. 100% counts as having set the bar too low. Tie compensation to other things — quality of contribution, scope of impact, judgment — not to whether the OKR hit 1.0.
Sources & further reading
- Reforge. How to Set OKRs: 6 Steps. reforge.com/blog/okr-guide
- Doerr, J. (2018). Measure What Matters. Portfolio. (Canonical popular reference on OKRs.)
- Grove, A. (1983). High Output Management. (Original methodology development.)
- Castro, F. (2018). The Beginner's Guide to OKR. (Practical implementation patterns.)
- RGM operator notes — composite of client engagements 2022–2026.