Session Brief: OKRs

Goal

Artifact: OKR set

Working Question

Which three to five measurable outcomes will the team deliver next quarter, and how can success be recognized objectively?

Context

Company-level OKRs of the layer above; lessons learned from last quarter with final score; known external constraints (releases, compliance, hiring); open commitments from running projects.

Setup

• Format: Method session
• Duration: 1-2 h setup, plus 30 min reviews every 2 weeks
• Mode: Workshop or async
• Participants: One OKR owner per set (team lead or Product lead); two to five team members who will hold key results; optional OKR coach or Chief of Staff for cross-team consistency.
• Owner: One OKR owner per set (team lead or Product lead)
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward OKR set. After the session, the artifact should be shareable, reviewable, or reusable.

Input

OKR template (table or document with columns Objective, Key Result, Baseline, Target, Owner, Confidence), shared document, link to strategy or company bets, history of previous quarter OKRs.

Preparation

Create document with sections header, Objectives, Key Results, owner list, and review cadence. Define cadence in advance (for example every two weeks, Wednesday 30 min). Define confidence scale (for example 1-10 or traffic-light).

Agenda

1. Section 1: Strategic anchor (15 min) Owner: Facilitator Action: Place company OKRs and the North Star Metric at the top of the document. Mark which company bets this team directly supports. Hint: If the team cannot be linked to any company bet, either the strategy is unclear or the team is outside focus. Neither is usually resolved inside the OKR workshop. Output: OKR set

2. Section 2: Objectives (20-30 min) Owner: Facilitator Action: Formulate a maximum of three objectives. Each should be an outcome sentence that is inspiring and achievable in 3 months. No outputs, no feature lists. Hint: An objective like "launch Feature X" is an output, not an outcome. Reframe to the user or business outcome the launch should produce. Output: Measurement plan

3. Section 3: Key results (30-40 min) Owner: Facilitator Action: 2-4 key results per objective, each with baseline (current value), target (quarter end), and source. At least one KR per objective must be a lagging metric. Hint: If all KRs are activity metrics ("10 interviews completed"), the set measures effort rather than impact. Enforce at least one outcome KR per objective. Output: Review cadence

4. Section 4: Owner and confidence (10-15 min) Owner: Facilitator Action: Assign one named owner per key result. Record initial confidence on the defined scale. If confidence under 5, trim KR or validate assumptions. Hint: Confidence 9-10 at quarter start is a warning sign; KR is likely too conservative. Aim for start value 5-7. Output: OKR set

5. Section 5: Review cadence (10 min) Owner: Owner Action: Set timing and format: check-in every two weeks with confidence update, blockers, and adaptation decisions. Fix mid-quarter review and end-of-quarter retro. Hint: Without fixed cadence, the set dies by week 4. Put date in calendar immediately. Output: Measurement plan

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: OKR set

Closeout

• Update result artifact: OKR set
• Define location, version, and review recipients.
• Define owner, next step, and review date.

OKR set: OKRs

Working Question

Which three to five measurable outcomes will the team deliver next quarter, and how can success be recognized objectively?

Context

Company-level OKRs of the layer above; lessons learned from last quarter with final score; known external constraints (releases, compliance, hiring); open commitments from running projects.

Participants

• Owner: One OKR owner per set (team lead or Product lead)
• Participants: One OKR owner per set (team lead or Product lead); two to five team members who will hold key results; optional OKR coach or Chief of Staff for cross-team consistency.

Input

OKR template (table or document with columns Objective, Key Result, Baseline, Target, Owner, Confidence), shared document, link to strategy or company bets, history of previous quarter OKRs.

Template

OKR Set

Objective 1

Why is this objective important?

Key Results

• KR1:
• KR2:
• KR3:

Confidence: 0.0-1.0 Owner: ...

Review rhythm

• Weekly check-in:
• Mid-cycle review:
• Final review:

Risks and dependencies

• ...

Completion Check

• OKR set is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision