BridgeLogicsProjects OKR Workshop Facilitator
A coaching skill for planning and running group OKR sessions. The goal is a room that leaves with OKRs that are co-owned, outcome-driven, and ready to execute — not a document that gets forgotten after the meeting ends.
Core Philosophy
OKR workshops fail most often before the session starts. Teams arrive without shared context, without a view of last cycle's performance, and without alignment on what problem this cycle needs to solve. The result is an hour of debating priorities instead of writing goals.
The facilitator's job is to make the room's thinking visible and the disagreements explicit — so the OKRs that come out reflect a real decision, not a compromise.
How to Use This Skill
- Planning a workshop → Start with Pre-Work Setup
- Running the session now → Go to the 4-Phase Session Guide
- Capturing output after the session → Use the Post-Session Format
- Workshop produced weak OKRs → Run the Troubleshooting Protocol
Step 1: Pre-Work Setup
Do this at least three days before the session.
What the Facilitator Needs
Ask the user:
"Do you have last cycle's OKR scores and retrospective notes available?"
If no: the session needs to start with a quick scoring review. Budget 15 minutes for it. If yes: share them with participants before the session as pre-reading.
"Do you have the company or team strategy for this cycle documented anywhere?"
If no: the session cannot produce good OKRs. Help the user articulate a one-paragraph strategy statement first. OKRs without a strategy anchor drift into activity lists.
"Who will be in the room — and do they all have context on last cycle's performance?"
If some participants are new or do not have context: brief them separately before the session, or build a context-setting opening into the agenda.
Pre-Work to Send Participants
Three days before the session, ask participants to prepare:
- One sentence: what is the biggest problem this team needs to solve this cycle?
- One metric: what is the one number that, if it moved, would tell you the team had a good cycle?
- Review: last cycle's OKR scores and one thing that got in the way
Tell them: this is not homework they turn in. It is context they bring to the conversation.
Step 2: The 4-Phase Session Guide
Recommended timing for a 2-hour session:
- Phase 1: Context (15 min)
- Phase 2: Problem alignment (20 min)
- Phase 3: OKR drafting (50 min)
- Phase 4: Stress-test and commit (30 min)
- Buffer: 5 min
Phase 1: Context (15 minutes)
Open with what happened last cycle — briefly.
Say: "Before we set new goals, let's spend 10 minutes on what we learned from last cycle."
Surface:
- What scored well and why
- What did not score and the most honest reason
- One thing the team wants to do differently this cycle
Do not let this become a blame conversation. Keep it factual. Move on.
Phase 2: Problem Alignment (20 minutes)
This is the most important phase. If the room cannot agree on the problem, they cannot write OKRs.
Ask the full group: "What is the most important problem this team needs to solve this cycle?"
Collect all answers visibly — on a whiteboard, a shared doc, or sticky notes. Do not filter yet.
Then facilitate to a top 2 or 3. Ask: "If we could only solve one of these this cycle, which one has the highest impact on the company's direction?"
This forces prioritization. The top answer becomes the anchor for the Objective.
Coaching note: If the room cannot converge, there is a strategy problem above the team. Name it. "It sounds like we do not have clarity on the top priority. That is worth surfacing to leadership before we set OKRs — otherwise we will write goals for a direction that may shift."
Phase 3: OKR Drafting (50 minutes)
Work through one Objective at a time.
Draft the Objective (10 minutes per objective)
Ask: "If we solve the problem we just identified, what does success look like at the end of the cycle — not in terms of what we built, but in terms of what is different?"
That statement becomes the draft Objective. Write it in the room. Read it back.
Ask: "Does this feel ambitious enough to be worth a full cycle of focus?"
If no: push for more direction. If yes: move to Key Results.
Draft Key Results (15 minutes per objective)
Ask: "How will we know we achieved this Objective? What would we measure?"
Collect answers. For each one, ask: "Is this measuring what changed, or what we shipped?"
Redirect output-based answers to outcomes. Use the examples from the okr-coach references if needed.
Push for 2 to 3 Key Results per Objective. No more.
For each Key Result, confirm:
- Is there a baseline? If not, when can we get it?
- Is the target achievable in one cycle at 60 to 70% confidence?
- Does the team own this, or does it depend on someone outside the room?
Phase 4: Stress-Test and Commit (30 minutes)
Run the full OKR set through a quick stress-test as a group.
The Group Stress-Test
Read each Objective and its Key Results aloud. Then ask:
"Does this set — taken together — represent the most important work this team can do this cycle?"
If yes: confirm and move to commit. If no: ask "what is missing or wrong?" and adjust.
Confidence Vote
For each Key Result, do a quick confidence check: "On a count of three, hold up fingers 1 through 10 for your confidence this is achievable."
If the range is wide (some people say 3, some say 8): "Let's understand the gap. What does the low end see that the high end does not?"
Surface the assumption and resolve it before the session ends.
Commit
End the session with explicit commitment: "Is everyone in this room willing to own these OKRs for the cycle?"
Get a verbal yes from each stakeholder. Not silent agreement. Spoken confirmation.
Assign an owner to each Key Result before the room leaves.
Step 3: Post-Session Output Format
Produce this document within 24 hours of the session.
OKR WORKSHOP OUTPUT — [Team Name]
Session date: [date]
Facilitator: [name]
Participants: [list]
Cycle: [Q_ YYYY]
OBJECTIVE 1: [text]
KR1: [text]
Baseline: [X] | Target: [X] | Owner: [name]
KR2: [text]
Baseline: [X] | Target: [X] | Owner: [name]
KR3: [text]
Baseline: [X] | Target: [X] | Owner: [name]
OPEN ITEMS: [anything unresolved — baseline to confirm, owner to assign, dependency to surface]
FIRST CHECK-IN: [date — should be within 2 weeks]
RETROSPECTIVE DATE: [end of cycle]
Session notes: [key decisions made and why]
Send this to all participants and their manager within 24 hours. The longer the gap, the more the commitment fades.
Step 4: Troubleshooting Protocol
Workshop produced vague OKRs
Root cause: Phase 2 was skipped or unresolved. The room wrote OKRs before aligning on the problem. Fix: Go back to problem alignment before any further OKR writing.
The same people dominated the conversation
Root cause: The structure allowed it. In Phase 3, use individual silent drafting before group sharing. Fix: Ask everyone to write their Key Result suggestions privately for 3 minutes before the group discusses.
OKRs were agreed in the room but abandoned within a week
Root cause: Commit phase was soft — nodding, not speaking. Or leadership did not model OKR use. Fix: Require verbal commitment and assign owners before the session ends. Set the first check-in date before anyone leaves the room.
The session ran out of time
Root cause: Phase 1 and 2 ran long because context was missing. Fix: Send pre-work and ensure all participants review last cycle's scores before arriving.
Leadership keeps changing the OKRs after the workshop
Root cause: Leadership was not in the room or the OKRs were not reviewed with them before publishing. Fix: Run a 30-minute leadership alignment check before finalizing. Or include leadership in Phase 2 at minimum.
Facilitator Reminders
- Your job is to make the room's thinking visible — not to write the OKRs for them.
- Silence in a workshop is usually disagreement, not agreement. Ask about it.
- If you are also a participant, you cannot be a neutral facilitator. Separate the roles.
- A good workshop leaves the team feeling heard and clear. Not exhausted and uncertain.