The OKR nobody could remember on Friday
Forty-seven objectives, two hundred and ten key results, one quarterly off-site. Nobody could name their own KR a week later. The system was working as designed.
A company I sat with last spring had just finished its quarterly OKR off-site. Forty-seven objectives. Two hundred and ten key results. A Notion database with conditional formatting that the head of operations was justifiably proud of. The CEO told me the system was finally working.
On Friday, I asked four random people what their key result was. Three of them checked their laptop. The fourth gave me the wrong KR — confidently, and from memory.
The OKR system was not working. It was producing what it always produces when objectives exceed working memory: a tracking exercise nobody mistakes for direction. The two-hundred-and-ten KRs were a record of every team's last quarter of work, lightly rewritten to face forward. The system was, in honest terms, calendar wallpaper.
The brain cannot hold forty priorities. It can hold three. Maybe four on a generous day. The moment the list exceeds the size that can be recited on an elevator, the list stops being a priority list and becomes a status document. Status documents do not change behavior. They describe it.
What an OKR is supposed to do — the only thing it is supposed to do — is allow a middle manager to decline a request. Someone asks the team to do a thing. The team looks at the three sentences pinned to the wall, says that does not serve this, and the request goes away. That is the entire purpose. Tracking, software, color-coded dashboards, quarterly reviews — all of it is downstream of whether the three sentences exist and are memorable.
The test is unsentimental. Walk into your office on a Friday afternoon. Ask three random people, not on your leadership team, to name the company's number-one objective. If they can — without checking a doc, without hedging — your OKRs are doing work. If they can't, you do not have OKRs. You have a planning ritual that produces a document nobody opens after the off-site.
The fix is brutally simple and almost nobody does it. Cut to three objectives. Cut to two or three KRs per objective. Recite them at every all-hands. Reference them when killing a project. Repeat them until people roll their eyes and finish the sentence with you. That eye-roll is the system working. It is the moment the priority moved from a doc into a brain, which is the only place it can do any useful work.
If your OKR can't be remembered on Friday, the answer is not better tracking software. It is fewer OKRs, said out loud, more often.