The coach's playbook
Good OKR facilitation is not about teaching a format. It is about creating the conditions where a team builds a habit. That means getting the sponsor on board before the first session, using structure to protect the room from the loudest voice, and knowing what to watch for once you step back.
Before you start: readiness and the sponsor
The biggest risk in any OKR engagement is not the team's skill. It is the cadence quietly lapsing when things get busy. Only the senior sponsor can hold that. So the first output from a new engagement is not an Objective. It is a commitment from the sponsor: the cadence in calendars for the full cycle, and the sponsor modelling attendance. Without that commitment, the rest of the work has no anchor.
Have the sponsor conversation before the team session. Ask for one concrete thing: "Can we get a recurring invite for every check-in and review into the calendar before we start?"
- Have this conversation one to one, not in the group session. A public ask is easy to defer; a direct ask is harder to avoid.
- If they hesitate, name the risk plainly: the cadence will be the first thing to slip when the quarter gets busy, and it cannot be recovered from the back.
- If they will not commit, surface that now rather than discovering it in week four when the first check-in gets cancelled and nobody reschedules it.
Example: the readiness gate
"We will sort out the cadence once the quarter starts." The calendar invite never goes out, the first check-in has no quorum, and by week six the OKRs are effectively orphaned.
A recurring calendar invite for every weekly pulse and the monthly review lands in everyone's diary before the first writing session. The sponsor's name is on the invite. It holds.
An invite that already exists is much harder to cancel than one that still needs to be created. The readiness gate turns a future intention into a present fact.
Alignment starts at the top. If the sponsor will not protect the rhythm, no amount of facilitation skill can compensate for that absence.
In the room
A leadership team converges badly in open discussion. The most senior voice anchors everyone else and the room calls it consensus. Structure beats seniority. Silent generation before any plenary, physical card-sorting for result-versus-activity, and a forced cut for focus all produce a better result than asking the group what they think and waiting for someone to go first.
Default to "1, 2, 4, all": everyone writes alone, then shares in pairs, then in fours, then the whole group. The senior person speaks last, not first. "Write your answer on your own before you share it."
- For Key Results, print each proposal on a card and sort the pile into "result" or "activity" as a group, no debate during the sort. The disagreements that surface afterwards are the lesson, not an obstacle to it.
- For Objectives, give out all candidates and give each person a limited number of votes. The argument that follows is the prioritisation conversation the team has been avoiding.
- When the group lands on an Objective everyone can live with rather than one anyone believes in, name it. Ask if they would be glad to achieve that by the end of the quarter. If the answer is flat, keep going.
Example: stopping the room from being captured
The director names an Objective in the first two minutes, everyone nods, and the session is effectively over. The team leaves with an OKR set that belongs to one person and is owned by nobody.
Silent write, three minutes. Pairs share, two minutes. Four-group clusters emerge. The plenary sees three candidates and votes with dots. The Objective the team argued its way to is one they will defend in a check-in, because they chose it.
People commit to what they helped choose. Silent generation means every voice gets into the room before the loudest one can close it down.
Focus and alignment are produced by structure, not by hoping the room speaks up.
Handling resistance
Resistance is predictable. "We have no time for the meetings." "We tried OKRs before and it did not work." "This is just more admin." And the urge, usually from the person with the most to lose, to relitigate whether to use OKRs at all. A coach who tries to win that argument has already lost it. The move is not to sell; it is to make the first small win visible and to protect the rhythm long enough for that to happen.
When a leader offers a long justification for why an off-track Key Result is actually fine, ask once: "What would have to be true for that to be wrong?" Then let it sit.
- When the pushback comes early, name it calmly rather than absorbing it. "It sounds like you are not convinced this is worth the time. That is worth saying out loud."
- Do not relitigate the decision to use OKRs. Redirect to the next concrete step. "Let's write one Objective and see what that surfaces."
- The "no time" objection usually softens after the first check-in that actually finishes in 15 minutes. Keep the early sessions short and crisp; that is the evidence base you are building.
Example: the "no time" objection
The weekly check-in is the first thing cancelled when the quarter gets busy. Within six weeks the OKRs have no rhythm, updates are weeks stale, and the format is quietly blamed for not working.
The weekly is 15 minutes, structured around three questions per Key Result. The sponsor attends. When the inevitable busy week arrives, the meeting survives because it costs almost nothing to hold and the sponsor treats it as non-negotiable.
Resistance shrinks when the overhead is genuinely small. The first thing to get right is the meeting length, not the OKR quality.
Transparency dies the week the cadence is treated as optional.
Knowing it worked
You will know the coaching transferred not when the OKRs look right, but when the team runs them without you. The signals are concrete: the Objective count dropped to a few (focus is visible); updates happen without being chased and outsiders can read the intent (transparency); each Objective traces to a higher goal and the team can explain the connection (alignment); and, the clearest sign, the team raises a mid-cycle pivot themselves rather than waiting to be asked.
Track three things across the cycle: the proportion of Key Results that are outcome-based, check-in attendance without you in the room, and whether the team initiates a pivot. "Is the team raising problems before I ask about them?"
- Aim for all Key Results outcome-based by the end of the writing session, most check-ins running without you by week six, and at least one team-initiated pivot before end of quarter.
- When you notice the team running a check-in without prompting, step back further. Absence is the coaching signal: they no longer need you in the room.
- The graduation moment is the self-initiated pivot. When a team spots that a Key Result is not moving and proposes a change before the coach raises it, the habit has transferred.
Example: the graduation signal
The coach runs every check-in, writes up every update, and prompts every difficult conversation. Remove the coach and the rhythm collapses within two weeks.
By week six the team runs the check-in. The coach is not in the room. At week eight the team raises a pivot: one Key Result is clearly not moving and they want to redirect effort. The coach hears about it afterwards, not before.
The goal was never well-formatted OKRs. It was a team that gets focus, transparency and alignment from the practice on its own. The coach's job is to make themselves unnecessary.
The goal was never good-looking OKRs. It was a team that no longer needs a coach to run them.
Paste it into Diagnose and get a rubric score alongside the patterns flagged in this guide.