How long should an OKR kickoff meeting take?

For a team of 5–15 people, 3–4 hours is typical for a thorough kickoff that includes context-setting, OKR review, alignment discussion, and initial decomposition. You can run a lighter version in 2 hours if pre-work is done in advance.

Who should attend the OKR kickoff meeting?

For startups and scale-ups, the full team should attend. The kickoff creates alignment and shared ownership — both are undermined if people are absent. For larger organisations, run it at the team level with leadership present for the company OKR presentation, then teams break out for their own OKR sessions.

What should be prepared before the OKR kickoff meeting?

Three things: (1) Scores and retrospective for last quarter's OKRs, (2) Draft company objectives from leadership, (3) Each team lead's initial thoughts on their key results. This pre-work ensures the kickoff is a conversation, not a blank-sheet exercise.

Workflow

OKR Kickoff Meeting Guide

Name: Loach
Rating: 4.8 (24 reviews)
Author: Loach

A six-step agenda that takes your team from last quarter's scores to this quarter's aligned OKRs — in 90 minutes.

Run Your Kickoff with Loach See the Full Planning Process

Free forever up to 5 users. No credit card required.

90-Minute Kickoff Agenda

OKR Kickoff — [Quarter] [Year]

0:00 — Review last quarter (20 min)

— Each team: scores + top lesson (2 min each)

0:20 — Company objectives (15 min)

— Leadership presents 2–3 objectives + Q&A

0:35 — Team key results (30 min)

— Each team: 2–4 KRs for owned objectives (5 min each)

1:05 — Alignment (30 min)

— Dependencies, overlaps, target adjustments

1:35 — Week 1 priorities (15 min)

— Each team states week 1 focus before closing

The Six-Step Kickoff Agenda

Each segment has a time box and a clear output. The meeting ends with every team knowing their week 1 priorities.

Share pre-work before the room opens (async, day before)

Send participants the drafted company objectives, last quarter's OKR scores, and a template for team key results 24 hours before the session. Kickoffs that start cold waste the first hour recapping — kickoffs that start with pre-work get to alignment in minutes.

Tip: If leadership hasn't drafted company objectives before the kickoff, cancel and reschedule. The kickoff depends on directional clarity from the top.

Review last quarter (20 min)

Open the session by reviewing last quarter's OKR scores. Each team lead presents their scores in 2 minutes or less. The goal is shared understanding, not a post-mortem. Surface the most important lessons and move on.

Tip: 0.7 is the target score, not 1.0. If all scores are 1.0, the OKRs were too easy. If all scores are below 0.5, targets need calibration.

Present company objectives (15 min)

Leadership presents the 2–3 company objectives for the quarter. These are directional and qualitative — they answer 'where are we going?' not 'how will we measure it?'. Leave time for questions to ensure everyone understands the intent behind each objective.

Tip: Objectives should pass the gut-check test: does every person in the room understand what winning this quarter looks like? If not, revise the objective before moving on.

Teams present key results (30 min)

Each team presents 2–4 key results for the objective(s) they own. This is a draft — not a final commitment. Other teams can ask clarifying questions and flag dependencies. Keep each team to 5 minutes maximum.

Tip: For each key result, ask: 'What would we work on in week 1 if we had to start today?' If nobody can answer, the KR isn't ready.

Alignment and negotiation (30 min)

Surface cross-team dependencies, overlaps, and gaps. Adjust targets based on capacity and strategic priority. This is where the actual alignment happens — not in an all-hands where OKRs are presented as done. Teams that skip this step discover conflicts in week 3 of the quarter.

Tip: Use a shared OKR document or tool so all teams' key results are visible side-by-side. Alignment is impossible when OKRs are siloed.

Confirm week 1 priorities (15 min)

Before closing the session, each team states what they are working on in week 1. This step is the proof of planning: if a team can't name their week 1 priorities, the planning isn't finished. Writing this down ends the meeting with clarity rather than enthusiasm.

Tip: Week 1 priorities should connect directly to a specific key result. If a priority doesn't tie to a KR, question why it's a priority.

How Loach Supports the OKR Kickoff

Agenda generation, live editing, and week 1 priorities — all in one place.

OKRs ready before the session

Set up objectives and key results in Loach before the kickoff — so the meeting is focused on alignment and refinement, not creation from scratch.

OKR editing during the session

Teams update their key results in Loach during the kickoff. Changes are captured in one place rather than spread across docs and notes.

Shared OKR visibility

All teams' OKRs are visible in one workspace during alignment. Dependencies and overlaps surface before the quarter starts, not after.

Week 1 priorities from your OKR breakdown

After the kickoff, decompose your OKRs in Loach to generate weekly priorities. The first Monday of the quarter starts with clarity, not a blank page.

Related Workflows

Quarterly OKR Planning

The full process before and after the kickoff

Weekly OKR Check-in

Keep the plan alive throughout the quarter

OKR Retrospective

Score and learn at quarter end

Frequently Asked Questions

Run a 90-Minute Kickoff That Actually Aligns Your Team

Loach gives your team shared OKR visibility during the kickoff and connects the output to week 1 priorities. Free for up to 5 users.

Start Free — No Credit Card