Share Beliefs and Plans
OKRs define outcomes, not methods, so teams must articulate and continually discuss how they intend to achieve them. Separate the outcome from the work, make the plan the focus of weekly check-ins, and update your beliefs as evidence arrives.
An OKR states where you are going, not how you will get there, and that is a deliberate design choice: it leaves room for teams to find better routes than anyone could specify up front. But it creates an obligation. If the goal does not contain the method, the team must make the method explicit somewhere, and keep talking about it, or the OKR becomes a destination with no journey, admired at planning and ignored until the retrospective.
Separate the outcome from the work
The first discipline is separation. The Key Result is the outcome; the work you believe will move it lives separately as initiatives, process commitments and experiments. Keeping them apart matters because it stops the classic confusion of "we did the work" with "the outcome moved". A team can complete every planned initiative and still miss the Key Result, and that gap, work done, outcome unmoved, is the single most useful piece of information a quarter produces. Blur the two and you lose it.
Plans are beliefs, and beliefs update
The plan is not a fixed commitment; it is the team’s current best belief about what will work, and beliefs should change as evidence arrives. This reframing is powerful: it turns the weekly rhythm from a status report ("here is what we did") into a reasoning session ("here is what we now believe, and why we are changing the plan"). A team that treats its plan as a living hypothesis adapts fast; a team that treats it as a contract defends it long after the evidence has turned against it.
Make plans the focus of check-ins
This is why weekly check-ins should centre on the plan, not the percentage. "The number is at 40%" is a status; "we believed X, the evidence says Y, so we are now trying Z" is the conversation that actually moves the goal. Reviewing beliefs weekly surfaces problems while they are still small, keeps the whole team engaged in the how rather than passively watching the what, and produces the running record of reasoning that makes the end-of-quarter retrospective an honest account rather than a reconstruction.
What it buys you
The benefits compound: higher engagement, because everyone is thinking, not just reporting; faster issue resolution, because problems surface early; more confidence, because the team can see its own reasoning; adaptability, because the plan bends before it breaks; and real accountability, because "what did you believe, and what happened?" is a far more honest question than "did you hit the number?". Sharing beliefs and plans is how an OKR stays alive between the day it is written and the day it is graded.
A team’s Key Result is flat at week four. A status culture records "40%, on track". A beliefs culture says "we bet on the email channel; open rates are fine but conversion is not, so we now believe the landing page is the blocker and are testing that". Same data, completely different quarter.
Why separate outcomes from the work? +
So you can tell "we did the work" apart from "the outcome moved". That gap is the most useful signal a quarter produces, and blurring outcome and work hides it.
What should a weekly check-in focus on? +
The plan and the beliefs behind it, not just the percentage. "Here is what we now believe and why we are changing course" moves a goal; "we are at 40%" does not.
From the ZOKRI OKR Handbook, the methodology we install and maintain. Written by Matt Roberts.
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.
The plan is where OKRs live or die between planning and review. We install the check-in rhythm that keeps beliefs explicit and updating, so problems surface while they are still small.