OKRs

This playbook is for leaders and practitioners working with OKRs in their organisations. It treats OKR adoption as a question of management philosophy rather than a question of writing templates, drawing on Deming's System of Profound Knowledge, Wodtke and Cutler, the post-2018 OKR reform tradition, and the wider sociotechnical literature.

OKRs

A management philosophy with a template attached

The template is the visible part of a philosophy

The Objective and Key Results are the visible part. Underneath sit assumptions about trust, ambition, and how decisions get made.

Most adoption failure is the philosophy showing through the template.

You cannot adopt OKRs without adopting the philosophy they assume.

profound.fyi

A team's OKRs are data about the management system

Four patterns recur. Each one shows what the system believes.

  • Used as a stick: people work because they are held to account
  • Used for control: coordination needs central authorship
  • Set and forgotten: planning and doing are separate activities
  • Used and ignored: looking aligned matters more than being aligned

You cannot intervene in a system you have not read.

profound.fyi

OKRs do two jobs when they work

Objectives radiate intent. Someone outside the team can read one and act on it without asking.

Key Results anchor decisions. They tell the team what to stop, and give it grounds to say no.

An OKR that does neither is wallpaper: formally correct, functionally absent.

profound.fyi

Each failure pattern breaks one or both jobs

  • Used as a stick breaks both. Key Results anchor blame instead of decisions.
  • Used for control stops the Objective radiating, because the team did not write it.
  • Set and forgotten stops anchoring, because nobody consults the Key Results.
  • Used and ignored consults them for show and ignores them in the work.

Ask which job has broken. The answer tells you which constraint is missing.

profound.fyi

Fix the constraints the system works under

  1. Visibility Show commitment versus aspiration, and the Key Result behind each decision
  2. Rhythm Bring OKRs into the weekly cadence of the work
  3. Safety Make missing a Key Result cost nothing personally

If all three look easy to maintain, at least one is not really there.

profound.fyi

Without safety, the other constraints fail

A team with weekly check-ins but no safety checks in conservatively and hides bad news.

A team with visibility but no safety writes Key Results that hide its real ambitions.

Safety means OKRs are separate from performance review in practice as well as on paper.

profound.fyi

Deming's four lenses expose what OKR teaching ignores

  1. System Do team OKRs add up, or optimise locally?
  2. Variation Can you tell a real miss from normal noise?
  3. Knowledge Which theory of change are you running?
  4. Psychology Which theory of motivation do you assume?

The four are interdependent. Apply them together.

profound.fyi

Explaining every miss makes the system worse

A Key Result misses by 15%. The team writes a plausible story about why. Leaders act on that cause. Next quarter it varies again.

That is tampering: reacting to noise as if it were a signal.

Asking teams to explain noise produces fiction.

profound.fyi

Read your own practice before you change it

The Reading Instrument asks four sets of questions:

  1. What a typical OKR carries, and who wrote it
  2. What happens when a Key Result is missed
  3. Where OKRs live between quarters
  4. What a team can say without paying for it

It produces a conversation. Where readings differ, the system is least clear about itself.

profound.fyi

Read the full playbook

profound.fyi/playbooks/okrs

All slides

The playbook is structured in seven parts:

  1. The Core Thesis - OKRs as a management philosophy with a template attached.
  2. Reading the System Through the Artefact - the four failure patterns as signals of what the management system believes.
  3. The Two Functions - what OKRs do when they work: radiating intent and anchoring decisions.
  4. Interventions as Constraint Changes - visibility, rhythm, and safety as the three constraints that decide whether OKRs do their work.
  5. The System of Profound Knowledge Lens - Deming's four parts applied to OKR practice. The diagnostic home base.
  6. Open Questions - what is not yet settled.
  7. Acknowledgements and References.

Elements of the framework are hypotheses rather than proven positions. They are marked as such throughout.

The first artefact is The Reading Instrument - a structured way to read your own OKR practice as evidence of what your management system actually is. Further artefacts will be added as they develop in practice.

Licensed under CC BY-SA 4.0.