OKRs OKRs - overview Present 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. 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. 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. 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. Fix the constraints the system works under Visibility Show commitment versus aspiration, and the Key Result behind each decision Rhythm Bring OKRs into the weekly cadence of the work Safety Make missing a Key Result cost nothing personally If all three look easy to maintain, at least one is not really there. 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. Deming's four lenses expose what OKR teaching ignores System Do team OKRs add up, or optimise locally? Variation Can you tell a real miss from normal noise? Knowledge Which theory of change are you running? Psychology Which theory of motivation do you assume? The four are interdependent. Apply them together. 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. Read your own practice before you change it The Reading Instrument asks four sets of questions: What a typical OKR carries, and who wrote it What happens when a Key Result is missed Where OKRs live between quarters What a team can say without paying for it It produces a conversation. Where readings differ, the system is least clear about itself. Read the full playbook profound.fyi/playbooks/okrs Licensed under CC BY-SA 4.0.