The OKR nobody could remember on Friday
Forty-seven objectives, two hundred ten key results, one quarterly off-site. Nobody could name their KR a week later. Working as designed.
A company I sat with last spring had wrapped its quarterly OKR off-site. 47 objectives. 210 key results. A Notion database with conditional formatting the head of operations was rightly proud of. The CEO told me the system was finally working.
On Friday, I asked four random people what their key result was. Three checked their laptop. The fourth gave me the wrong KR, confidently, from memory.
The system wasn't working. It was doing what OKRs always do when the list outruns working memory: producing a tracking exercise nobody mistakes for direction. The 210 KRs were a record of last quarter's work, lightly rewritten to face forward. In honest terms, it was calendar wallpaper.
The brain can't hold 40 priorities. It can hold three. Maybe four on a generous day. Once the list grows past what you can recite in an elevator, it stops being a priority list and becomes a status document. Status documents don't change behavior. They describe it.
What an OKR is for, the only thing it's for, is letting a middle manager decline a request. Someone asks the team to do a thing. The team looks at the three sentences on the wall, says that doesn't serve this, and the request goes away. That's the whole job. Tracking, dashboards, quarterly reviews: all of it is downstream of whether the three sentences exist and stick.
The test is unsentimental. Walk into your office on a Friday afternoon. Ask three people who aren't 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 don't have OKRs. You have a planning ritual that produces a document nobody opens after the off-site.
The repair is brutally simple and almost nobody does it. Cut to three objectives. Cut to two or three KRs each. Recite them at every all-hands. Reference them when you kill a project. Repeat them until people roll their eyes and finish the sentence for you. That eye-roll is the system working. It's the moment the priority moves from a doc into a brain, the only place it can do any work. The same discipline that turns a bloated status meeting into three numbers turns forty objectives into three you can name.
None of this is new. It's the old rule about prioritizing the end goals that matter and dropping the rest. If your OKR can't be remembered on Friday, better tracking software won't save it.
Fewer OKRs will. Said out loud, more often.