Pilot-With-Your-Best-Team Rollout
Don't roll OKRs out company-wide; hand the book to your strongest team, let them adapt it, then spread by twos.
- Difficulty
- Easy
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 90%
Wodtke's antidote to the most common OKR failure: speed. Leaders read Measure What Matters, get excited, mandate OKRs for everyone, discover the illusion of knowledge (they never really understood the mechanics), and spit it out declaring 'OKRs don't work.' Instead, pilot with a single high-performing multidisciplinary team who will figure out how OKRs fit your culture, then propagate the working template two teams at a time.
Origin
Christina Wodtke's rollout guidance from Radical Focus, reacting to widespread failed top-down OKR mandates after John Doerr's Measure What Matters.
Core principles
- 01The number-one cause of OKR failure is speed — mandating everywhere before anyone understands the mechanics
- 02The illusion of knowledge: like explaining how a ballpoint pen works, you think you understand OKRs until you try to implement them
- 03Your best team always wants to be better and is imbued in your culture, so they'll find where OKRs fit and where they don't
- 04Don't use OKRs to fix a bad team — you'll make everyone hate OKRs and make the team worse
- 05OKRs are a vitamin, not a medicine; they supercharge strong teams and merely expose weak ones
How to run it
- 1
Pick one high-performing multidisciplinary team
Choose your best cross-functional team — smart, capable, and steeped in your culture — to run the first OKR experiment.
Pro tip The best team always wants to get better, so they'll engage genuinely rather than resist.
Watch out Never pilot on a struggling team hoping OKRs will fix it; that poisons the whole company against the method.
- 2
Hand them the material and let them run
Give them the book (or blog posts) and say 'we're thinking about OKRs — see if it works,' delegating the learning instead of trying to master it yourself under time pressure.
Pro tip As a leader you don't have time to become the expert; let your best team absorb it and report back.
Watch out Skimming the source yourself and mandating from a shallow understanding is exactly how rollouts fail.
- 3
Check in after ~3 months
Circle back a quarter later and ask what they figured out — where OKRs helped, where they didn't fit your culture, and what they adapted.
Pro tip They'll surface culture-specific adaptations (folding OKRs into existing stand-ups, a Slack 'brag channel' instead of emails) you'd never have designed top-down.
Watch out Don't rush this feedback loop; a quarter is the minimum to learn anything real.
- 4
Propagate two teams at a time
Take the working, culture-fitted template to two more teams, then two more, then your management team — spreading gradually rather than all at once.
Pro tip Each wave hands off a proven template plus lived experience, compounding adoption quality.
Watch out A big-bang company-wide launch reintroduces the exact speed problem you were avoiding.
In the wild
Wodtke describes the pattern she sees repeatedly: leaders read Measure What Matters, get excited, skim it, have HR implement OKRs for everybody, everyone is briefly happy, then sad, then they spit it out and conclude OKRs don't work. Nobody calls her for advice before doing OKRs — only after it has failed.
→ Predictable failure and a company convinced OKRs are broken, when the real cause was a rushed top-down rollout on a shallow understanding.
Common mistakes
Mandating OKRs company-wide from day one
Excited leaders roll OKRs out to everyone before anyone understands them, hit the illusion-of-knowledge wall, and the whole company rejects the method; piloting with one team contains the risk.
Piloting on a weak team to fix it
Using OKRs as a turnaround tool on a struggling team makes them hate OKRs and makes the team worse, because OKRs are a vitamin for strong teams, not a medicine for broken ones.
Is it for you?
Best for
Executives and heads of ops considering an OKR adoption who feel time pressure to standardize the whole org at once.
Not ideal for
Very small startups where there's effectively only one team — there's no separate pilot group to learn on first.
From the transcript
“I can tell you I can repeat everything I said, but instead I'll just say speed”
“it's what is it? The illusion of knowledge? Like if I asked you right now how does a bicycle work?”
“give my book to your best team and say, we're thinking about OKRs, can you guys see if it works? And then three months later,…”
“then you have a template and then you can take it to two more teams and then you can take it to two more teams”
“If you try to fix a bad team with OKRs, you'll make everybody hate OKRs and make the bad team worse”
From the episode
The ultimate guide to OKRs
Christina Wodtke (Stanford)