Reading the System Through the Artefact
The artefact tells you what the system believes.
When OKRs in an organisation consistently come out one way rather than another, that is not random. It is the management system expressing itself through whatever format you have given it. A team's OKRs are not data about the team. They are data about the management system that produced them.
Four patterns recur. They are not problems. They are signals.
Signal one - OKRs used as a stick
When OKRs are visibly linked to performance review. When a Key Result is missing, it carries a personal cost. When the targets in the artefact are conservative, because the targets in the artefact are also the targets in the performance conversation.
The system is telling you: we believe people work because they are accountable.
This is a particular management philosophy. It has a long history. It is also empirically wrong - Deming spent his career demonstrating that performance variation is overwhelmingly the property of systems rather than individuals, and that holding individuals to account for system-level variation produces fear without improvement. The OKR system that uses targets as a stick is encoding a theory of motivation that the evidence has been against for fifty years.
But the system does not know it is doing this. The OKR template makes the encoded theory invisible. The pattern is the signal.
Signal two - OKRs used for control
When Objectives are written downward by leadership. When teams are consulted but not authoring. When alignment is enforced by template rather than negotiated by conversation. When the cascade is mechanical rather than dispositional.
The system is telling you: we believe coordination requires central authorship.
This is the philosophy of scientific management transplanted into a knowledge-work context. It assumes that the people closest to the work cannot be trusted to know what the work should be. It is the philosophy that built mass production. It does not transfer.
The OKR template makes it possible to encode scientific management while using the vocabulary of empowerment. Teams "own" their OKRs while having no say in what those OKRs are. The pattern is the signal.
Signal three - OKRs set and forgotten
When the OKR drafting workshop produces an artefact that is then filed. When the operating rhythm runs on different signals - projects, programmes, tickets, deadlines. When the OKRs reappear at the next quarterly ritual unchanged or replaced.
The system is telling you: we believe planning and doing are separate activities.
This is a Taylorist assumption rendered in twenty-first century language. Planning happens at one cadence, in one room, with one set of people. Doing happens at a different cadence, in different rooms, with different people. The artefact bridges nothing because nothing is asking it to bridge.
The OKR template is rhythm-neutral. It can be operated on a weekly cadence (Wodtke) or an annual one (most large-enterprise rollouts). The pattern of forgetting tells you which the organisation has chosen, regardless of what the policy document says. The pattern is the signal.
Signal four - OKRs used and ignored
When OKRs are cited in leadership presentations but absent from sprint planning. When reporting against them is performative. When the artefact persists because abandoning it would create political friction, while the actual work follows different signals.
The system is telling you: we believe the appearance of alignment matters more than alignment.
This is the most uncomfortable of the four signals. It is the signal of a system that has lost trust in its own instruments and has chosen to maintain them as theatre rather than confront what they were supposed to measure. It is the management equivalent of a building that has been declared structurally sound for political reasons even though the surveyors disagree.
The OKR template gives this signal somewhere to hide. The artefact looks the same whether it is load-bearing or decorative. The pattern is the signal.
What to do with the signals
Read them. Not as problems to fix. As evidence of what your management philosophy already is.
The instruments at the end of this playbook give you a structured way to read. The signals are diagnostic only - they tell you what the system believes. Changing what the system believes is a different conversation, and it sits in the section on constraints.
But the diagnosis matters first. Most failed OKR programmes are responses to symptoms without diagnosis. The team that introduces weekly check-ins to combat set-and-forgotten without changing the planning-doing split underneath produces forced cheerful theatre on top of the same disconnection. The treatment looks like a fix and is not.
You cannot intervene in a system you have not read.
Last updated 15 May 2026
Licensed under CC BY-SA 4.0.