Slide Deck Template for OKR Planning Presentations

OKR planning meetings are where strategy becomes execution — or where they divorce. The quarterly OKR planning process forces every team to confront the same questions: Are we working on what matters most? Do we know what success looks like? Are our goals ambitious enough to actually change something? A well-structured OKR planning presentation is the mechanism that makes those questions productive rather than chaotic.

This guide covers the OKR framework, slide structure for both OKR retrospectives and OKR planning kickoffs, the waterfall from company OKRs to team OKRs, dependency mapping, and the most common OKR implementation failures that a good planning deck can help prevent.

The OKR Framework: A Brief Foundation

OKRs (Objectives and Key Results) were developed at Intel by Andy Grove in the 1970s and popularized by John Doerr, whose investment in Google in 1999 came with an OKR framework that Google adopted and still uses today. Doerr's book Measure What Matters (2017) brought OKRs to mainstream adoption.

Objective: A qualitative, inspiring, time-bound statement of what you want to achieve. It should be memorable enough to repeat without looking at a document. "Become the undisputed leader in our category." "Ship a product our customers can't stop talking about." "Build the engineering team that can execute our 5-year vision."

Key Results: Quantitative measures that tell you whether you've achieved the Objective. Each Objective should have 3–5 Key Results. Key Results are not tasks or activities — they are outcomes. Bad: "Launch the new pricing page." Good: "Increase trial-to-paid conversion rate from 12% to 18%."

Confidence level: Google and other OKR practitioners assign a confidence level (0–100%, or sometimes 0–1.0) to each Key Result at the time it is set. A confidence level of 50% is considered healthy — it means the goal is ambitious but achievable. If confidence is 90%+, the aim isn't high enough. If confidence is 20%, the goal may be disconnected from reality.

Grading scale: OKRs are graded at the end of the quarter on a 0.0–1.0 scale. 0.7 is considered a success (achieving 70% of an ambitious goal). 1.0 consistently means the goals weren't ambitious enough. Below 0.4 means something went seriously wrong: the goal was unrealistic, priorities shifted, or execution failed.

---

Part 1: The OKR Retrospective

Before setting new OKRs, every planning session should begin with an honest retrospective of the prior quarter's OKRs. Skipping the retrospective — rushing directly to new goal-setting because the retrospective is uncomfortable — is the most common OKR process failure.

Retrospective Slide 1: Prior Quarter OKR Grades

Display each Objective with its Key Results and the final grade (0.0–1.0) for each Key Result. Color-code by performance: green (0.7–1.0), yellow (0.4–0.69), red (0.0–0.39).

The purpose of this slide is not to assign blame — it is to create a shared picture of reality. When the entire company sees the same grades simultaneously, it eliminates the revisionist history that otherwise accumulates between planning cycles.

Retrospective Slide 2: What We Learned

For each underperforming Key Result, answer two questions: Why did we fall short? What would we do differently? These are not rhetorical questions. They should have specific, honest answers. "We set a Key Result of 18% conversion rate improvement but didn't assign ownership to a specific team. With shared accountability, it got deprioritized." That is useful. "Market conditions were challenging" is not.

For overperforming Key Results (1.0 grade), answer: Was the goal ambitious enough? If the team hit 1.0 easily, next quarter's goal should be harder.

Retrospective Slide 3: Priorities Shift Analysis

What changed during the quarter that caused you to work on things outside your OKRs? A major customer escalation, a competitive threat, a board request, a product emergency? If more than 20% of team capacity went to unplanned work, that is a systemic issue — either OKR setting isn't accounting for interrupt capacity, or the organization has a planning discipline problem.

---

Part 2: The OKR Planning Kickoff

Planning Slide 1: Company OKRs

The CEO presents 3–5 company-level OKRs for the quarter. These are non-negotiable — they represent leadership's judgment about what matters most. Every team OKR should connect to at least one company OKR.

Company OKRs should be ambitious but believable. The CEO presenting OKRs with no context or rationale is a missed opportunity. For each Objective, briefly explain: why this quarter, why this goal, and what is different about the strategy compared to last quarter.

Planning Slide 2–N: Team OKR Waterfall

Each team lead presents their team's OKRs. The waterfall structure is the most important organizational element of OKR planning: every team OKR should explicitly show which company OKR it supports.

The waterfall format:

• Company OKR: "Achieve product-market fit in the enterprise segment"

- Product Team OKR: "Ship 3 enterprise-only features with 80%+ enterprise customer adoption within 30 days of launch" - Sales Team OKR: "Close 5 enterprise accounts with ACV > $50,000" - Customer Success OKR: "Achieve 90-day NPS > 50 across all new enterprise customers"

The waterfall makes alignment visible. If a team cannot connect their OKR to a company OKR, they should ask whether they're working on the right thing.

Planning Slide: OKR Dependency Map

For complex quarters with multiple interdependent team OKRs, a dependency map is essential. This is typically a simple table or diagram showing which teams depend on deliverables from other teams to achieve their Key Results.

Example dependency: Sales OKR of "Close 5 enterprise accounts" depends on Product OKR of "Ship enterprise SSO by week 4." If Product ships late, Sales is blocked. Making this dependency explicit in the planning deck gives leadership the visibility to act on it — either by committing to the Product deadline or by adjusting the Sales Key Result.

The dependency map slide forces the conversation that most organizations avoid: "Which team's slippage breaks another team's OKRs?"

Planning Slide: Resource Alignment

Do the OKRs match the actual resources (headcount, budget, time) available this quarter? One of the most common OKR failures is that leadership approves ambitious OKRs without verifying that the teams have the capacity to pursue them alongside their operational responsibilities.

This slide presents a simple capacity check: for each major Key Result, what percentage of the team's available capacity does it require? If the sum of Key Result capacity requirements exceeds 100%, something has to give. Surface this in the planning meeting rather than discovering it three weeks into the quarter.

---

Common OKR Failures and How to Address Them in Your Planning Deck

OKRs that are tasks, not outcomes: "Launch the new onboarding flow" is a task. "Reduce first-week churn from 18% to 8%" is an outcome. If your Key Results sound like a project plan, rewrite them as outcome measurements. The planning deck should explicitly define what measurable change in the world will prove the work was worth doing.

Too many OKRs: More than 3–5 Objectives per team, or more than 5 Key Results per Objective, signals that the team hasn't made hard prioritization decisions. Everything is a priority means nothing is a priority. The planning deck should force this discipline — if a team presents 8 Objectives, the facilitator should push back before moving on.

No baseline data for Key Results: A Key Result like "Increase customer satisfaction" is meaningless without a baseline. "Increase NPS from 32 to 45" is meaningful. The planning process should require teams to have baseline measurements before committing to Key Results. If you don't know your current number, the first Key Result for the quarter might be to measure it.

OKRs that don't connect to the company OKRs: If a team's OKRs have no visible connection to any company-level OKR, the team is either working on something strategic that leadership hasn't articulated (a planning communication failure) or the team is working on something that isn't aligned with company priorities (an alignment failure). Either way, it should be surfaced in the planning session.

No owner assigned to each Key Result: Key Results with team-level ownership often end up with diffuse accountability. Best practice: each Key Result should have a single named owner who is responsible for tracking and reporting on it, even if multiple people contribute to achieving it.

---

OKR Review Cadence

OKR planning is a quarterly event, but OKR review is an ongoing process.

Weekly team OKR check-in (5–10 minutes): What is the current status of each Key Result? Any risks or blockers? This is a quick pulse, not a deep review.

Monthly OKR health check (30 minutes): Mid-quarter review with leadership. Update confidence levels on each Key Result. If confidence has dropped significantly, either reassign resources to rescue the Key Result or formally reset expectations. Don't let failing OKRs silently accumulate unrealistic expectations through the quarter.

Quarterly retrospective + planning (2–3 hours): Full retrospective of prior quarter followed by new quarter planning. This is the meeting this guide is designed for.

---

Slide Design for OKR Planning Presentations

OKR planning slides function as working documents as much as presentation slides. The audience is internal (department heads, team leads, and in some companies, all employees) and they are active participants, not passive viewers.

Tables are acceptable: OKR grading tables, dependency maps, and resource alignment matrices are better as tables than as visual graphics. Prioritize legibility over aesthetics.

Color coding is essential: Red/yellow/green status coding is so universal in OKR culture that deviating from it creates confusion. Use it consistently and define what each color means at the start of the deck.

Version control: OKR planning decks are living documents. Use slide headers or footers to show the version date. Make it clear whether a deck is "Draft — Discussion Use Only" or "Final Q[N] OKRs."

Make it accessible: OKR planning decks are often circulated before the meeting as a pre-read. Design them to be comprehensible without narration — include context that would otherwise only exist in the presenter's head.

Using slide-deck.io for Your OKR Planning Deck

Slide-deck.io generates a complete OKR planning slide deck in minutes. The AI builder creates retrospective grading slides, company OKR templates, team waterfall frameworks, and dependency map layouts. Customize with your quarter's data, share the pre-read link before your planning session, and update confidence levels throughout the quarter as your teams progress.

---

Key takeaways: Start with an honest retrospective before setting new OKRs. Enforce the waterfall — every team OKR should connect to a company OKR. Require baseline data for every Key Result. Assign a single named owner to each Key Result. Set a confidence level of ~50% on ambitious goals. And surface resource and dependency conflicts in the planning meeting, not three weeks into the quarter.