How many OKRs should a program run?

3 to 5 objectives, with 2 to 4 KRs each. More than that, the team can't hold them. Fewer, and you're probably underscoping. The template is sized for 5 objectives with room to expand.

Quarterly. Annual OKRs become wish lists by month 3. The template is built around a 13-week quarter with weekly check-ins and an end-of-quarter scoring session.

Should I share OKRs across the org?

Yes, with one caveat. Share objectives broadly so other teams can align. Share KRs at the leadership level so commitments stay credible. Sharing every KR with every team produces theater.

Excel or Google Sheets?

Both. The template is .xlsx and opens cleanly in Google Sheets. Confidence and scoring formulas carry over.

All tools › Governance & Growth › OKR Tracker

Outcomes

OKR Tracker

Most OKRs are dead by week 4. The strongest ones I've seen live because they are scored honestly, reviewed weekly, and reset with discipline. This template is built for the second kind.

$29 one-time, instant download

✓ Excel + Google Sheets · ✓ Confidence column · ✓ PDF cheat sheet

Buy Now, $29

Secure checkout via Gumroad · 30-day refund

Or get all 16 PM tools for $99. The full toolkit ships every template in the catalog: status reports, RAID logs, charters, OKRs, and more. See what's in the bundle ›

Premium · Includes the playbook
Already buying the bundle? Add the book for $30 more. The Director's Library bundles The Director's Playbook (the book) with the full 17-tool toolkit for $129. Same tools, plus the operating manual that ties them together. View the Library, $129 ›

What's in the download

OKR register (Excel)

Objectives at the top, key results indented beneath, with confidence column, scoring column, and a check-in row per week. Conditional formatting that surfaces the KRs slipping out of confidence before the quarter closes.

Confidence column built for early warning

Most OKR templates score at end-of-quarter. By then the quarter is already over. The confidence column forces a 1-5 read every week so the team can see a KR drifting in week 4 instead of week 12.

Stretch vs. commit (the 0.7 trick)

A score of 0.7 on a stretch goal is a win. A score of 1.0 on a commit goal is a baseline. The template makes the distinction explicit so the end-of-quarter conversation is about what to learn, not who hit what.

Quick-reference cheat sheet (PDF)

The 5 rules that separate working OKRs from ceremonial ones, when to skip OKRs entirely, and the end-of-quarter scoring + reset script.

Use forever, no subscription

One purchase, yours to keep. Use it on every program, customize for your team. Works in Excel and Google Sheets.

Why most OKRs die by week 4

Most teams that adopt OKRs do them badly. They skip the parts that make them work: measurable key results, weekly check-ins, honest scoring, and a ruthless reset at the end of the cycle. If you nail those four, OKRs compound. If you don't, they become a quarterly ceremony nobody respects.

The most common failure mode is the initiative-disguised-as-objective. "Launch the new platform" is not an objective. It is an initiative. The objective is the outcome that justifies the initiative: "Reduce checkout abandonment by 25% by end of Q3." The platform launch is one possible way to get there. Most teams write the initiative as the objective and then can't tell whether they succeeded.

"An OKR scored honestly at 0.4 teaches you more than an OKR scored politely at 0.9."

This template is built to enforce the discipline that makes OKRs work. Confidence forces weekly honesty. Scoring forces end-of-quarter honesty. The cheat sheet covers when to use OKRs and when to skip them entirely.

Objective vs. Key Result, plain

The single most common OKR mistake is confusing the two. The fix is a one-line test.

Objective. The outcome you want. Qualitative. Memorable. "Reduce checkout abandonment so the team stops losing the buyers it already attracted."
Key result. The measurable consequence of hitting the objective. Quantitative. Specific. "Reduce checkout abandonment from 38% to 28% by end of Q3."

If you cannot put a number on the key result, it is not a key result. It is an aspiration with a date.

When NOT to use OKRs

OKRs are the wrong tool for some teams. The cheat sheet covers the full list, but the headline cases:

Pure operational work where the metric is uptime, not a quarterly target.
Teams in their first 90 days, where the right artifact is the charter, not a measurable target.
Teams under 5 people, where OKRs add ceremony the team can't carry.

OKR Tracker

What's in the download

OKR register (Excel)

Confidence column built for early warning

Stretch vs. commit (the 0.7 trick)

Quick-reference cheat sheet (PDF)

Use forever, no subscription

Why most OKRs die by week 4

Objective vs. Key Result, plain

When NOT to use OKRs

Often bought together

Program Charter

Roadmap Tracker

Decision Log

Or get all 17 tools, $99