--- title: High-Leverage OKRs · The 6-Step Framework | RGM® url: https://realgrowthmatters.com/learn/frameworks/okr-guide/ updated: 2026-06-10 source_html: https://realgrowthmatters.com/learn/frameworks/okr-guide/ --- ## 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 that other planning frameworks can't match. Reforge's six-step OKR framework 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 are trying 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 are not activities. They are not metrics for their own sake. They are observable changes in the world that would not occur unless you made progress on the objective. An objective without key results is a goal with no scoreboard. Key results without an objective are a metric stack with no narrative. Together, they force a team to articulate both what success looks like and how it will know. ## Step 1 — Draft outcome-oriented OKRs The first and hardest step. Most teams write activity-oriented OKRs: "Launch the new landing page," "Run 10 webinars," "Ship feature X." These are tasks, not outcomes. They confuse motion with progress. Outcome-oriented OKRs describe what changes in the world if the activities succeed. "Increase qualified MQL volume from $200/MQL to $120/MQL while holding MQL→SQL conversion at 38%." That's an outcome. The activity (a new landing page, a series of webinars) is downstream — and if the activity doesn't move the outcome, it doesn't matter that it happened. The Reforge discipline is to limit the team to **1–4 objectives per cycle**. More than four diffuses focus and signals that the team hasn't actually prioritized. The same discipline applies to key results: 2–4 per objective. A key result list of 8 is not a list of key results; it's a status report disguised as a plan. ## Step 2 — Update OKRs quarterly Reforge's recommended cadence is quarterly review and revision. Annual OKRs are too coarse to act on; monthly OKRs are too granular to plan against. Quarterly is the cadence where the system actually fits human attention spans and business reality. The quarterly process is straightforward: in the last week of the prior quarter, the team reviews progress, retires completed OKRs, evolves still-active ones, and drafts new ones for the upcoming quarter. The team enters the new quarter with a complete OKR set on day one. The mistake teams make: writing OKRs during week 2 of the quarter. By the time they're finalized, week 4 starts, and the team has lost 30% of the cycle to planning. ## Step 3 — Share, align, and socialize An OKR that lives in a single document and is read once is operationally inert. The discipline of socialization is what makes OKRs actually influence behavior. The Reforge prescription: write OKRs with input from your team, not in isolation. Cross-functional peer alignment happens before the OKRs are finalized, not after. The team that's expected to deliver the outcome has a hand in defining the outcome. Beyond the writing team, OKRs need to be socialized: - Up the chain — to leadership and adjacent functional leaders who depend on this work. - Across the chain — to engineering, product, sales, customer success, and other groups whose work intersects. - Down the chain — to ICs whose individual goals should ladder up to the team OKRs. Socialization is not "share the wiki link in Slack." It's structured conversations: a kickoff meeting where the OKRs are presented, an interlock with adjacent teams, a written narrative explaining the reasoning behind the choices. Without socialization, OKRs become invisible to anyone outside the team that wrote them. ## 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 that shows current state of every key result. A weekly check-in cadence (15 minutes per OKR is enough) where the team reviews progress, flags risks, and makes resource shifts. A clear escalation path when an OKR is materially off-track. If you launch OKRs without these mechanics, the OKRs are decorative. ## Step 5 — Reinforce and review The mid-quarter discipline is what 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 the OKRs are the explicit basis for prioritization conversations — then the OKRs are alive. If none of that happens, the OKRs are dead by week 6. Review means honest weekly assessment of where you are versus where you said you'd be. Off-track key results need flagging, not hiding. The point is not to make every key result look green at the weekly check; the point is to detect off-track work early enough to fix it before the quarter ends. ## Step 6 — Conduct quarterly post-mortems End-of-quarter, the team conducts a structured retrospective on the OKRs. Three questions: 1. Did we hit the key results? 2. Did hitting (or missing) the key results move the objective? 3. 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. Over time, a team that takes post-mortems seriously gets dramatically better at predicting what's achievable, how long things take, and what unexpected things break. A team that skips post-mortems — or runs them as superficial victory laps — never accumulates that intuition. **Post-mortems are training data.** Reforge frames quarterly OKR review as the loop that compounds team capability. The team that post-mortems honestly gets sharper at planning every quarter. The team that doesn't, doesn't. ## Common OKR failure modes **Sandbagging.** Setting key results so low that they're certain to be hit. This produces 100% completion rates and zero strategic value. **Activity disguised as outcome.** "Ship 4 landing page tests" is an activity. "Lift landing-page CVR from 2.4% to 3.6%" is an outcome. **Too many OKRs.** If you have 12 objectives, you don't have priorities — you have a list. The whole point of OKRs is to force the priority conversation. **OKR fatigue.** When OKRs become a tax instead of a tool, the team disengages. The cure is connection to real decisions: which projects get resources, which don't. **No socialization.** Adjacent teams don't know your OKRs, so their work doesn't ladder up to yours. **No post-mortem.** The OKRs cycle restarts at the beginning of next quarter as if nothing happened, and the team never learns. #### RGM experts say The most common cause of OKR failure we see in client engagements: leadership using OKRs to measure individual performance. Once OKRs become the basis for compensation or promotion, teams immediately sandbag. Sandbagged OKRs produce 100% completion rates and zero strategic value. The fix: separate OKRs from individual performance evaluation. OKRs are aspirational strategic targets. They should be set at the level where hitting 70% counts as success and 100% counts as having set the bar too low. Tie compensation to other things — quality of contribution, scope of impact, decision-making — not to whether the OKR hit 1.0. ## Adapting the framework to RGM client engagements For most client engagements, RGM operates on a 13-week (quarterly) OKR cadence with weekly check-ins and end-of-quarter retrospectives. Each engagement has 2–3 objectives, with 2–4 key results per objective. The OKRs are visible to the client's leadership team and to every contributor on the engagement. The pattern that works: write the OKRs in week 0, launch them in week 1, review weekly through week 12, post-mortem in week 13. The next engagement (or the next quarter of the same engagement) starts with the post-mortem learnings already integrated. **Source & further reading.** This framework was originally articulated by the team at Reforge. For the original essay, see . RGM has expanded the framework with operator-side examples, RGM playbook content, and integration with the broader RGM growth strategy. ## Related frameworks [**The Four Fits Framework** Product-Market Fit alone is not enough to build a $100M+ business. The Four Fits — Market-Product, Product-Channel, Channel-Model, Model-Market — and why all four must align. RGM's operator expansion of Brian Balfour's Reforge framework.](/learn/frameworks/four-fits/)[**The Data Scaling Framework** Crystal Widjaja's 3-stage data maturity model: Data Informed → Data Driven → Data Led. How to build the analytics, instrumentation, infrastructure, and team that match your company's actual data maturity.](/learn/frameworks/scaling-data/)[**How to Build a Growth Team** Three growth practitioner profiles (Builder, Optimizer, Visionary), three structural models (centralized, decentralized, hybrid), and the 4-step process for building a high-impact growth function — expanded from Reforge's framework.](/learn/frameworks/build-growth-team/)[**FRAME · A Better Product Review** Product review meetings are where strategic alignment happens — or fails to happen. The FRAME framework (Focus, Rules of engagement, Attendees, Memo, Engagement) for facilitating product reviews that produce decisions, not theater.](/learn/frameworks/frame-product-review/)