An OKR rollout isn't decided by the goals, but by whether people come to the check-in prepared

The question about the number one habit gets an answer in this conversation that you won't find in any guide to writing goals. It is consistency. A fixed slot for a short check-in, one everyone knows without looking at the calendar, instead of a meeting that has to be squeezed in somewhere every week. The health metric for the programme is simpler than companies would like it to be: attendance and preparation. If people turn up and know what they are talking about, the programme is alive. If every other person turns up and only remembers on the spot what has happened over the last two weeks, there is no point in polishing the wording of the goals, because the problem is somewhere else. For this to work, the meeting has to stay within its time: four minutes per person, questions held until the end, other topics put on a list for later. With prepared people, eight to ten people fit into thirty-five minutes, and seventeen into an hour.

The second point overturns the most common objection to the check-in, namely that it is one more meeting added to people's workload. It is meant to replace meetings, not to add to them, because a conversation about what matters most right now makes some other conversations unnecessary. In the episode there is the story of a sceptical manager who was just going through the motions with the programme, and after two weeks came of his own accord to say he was convinced, because thanks to one check-in he had cancelled three meetings a week. Underneath sits a change that is harder than the method itself: moving from reporting what we have done to talking about where we want to be at the end of the quarter and how confident we are of it. It sounds like a small matter of wording and it isn't, because it forces a projection where people have been trained to give an account.

The third thread concerns people, and here the conversation gets uncomfortable. Without a sponsor on the board who commits their time, not just their approval, the programme doesn't go beyond an operational slice and never touches the strategy. A leader high up in the structure who only goes through the motions with goals is not a local problem, because it spills over into everything below them, and you have to sit down with them in private instead of waiting for it to sort itself out. The framework gives guidelines, not rules, so every organisation makes its own version within the set lane, and the biggest source of failure is people who have read the book, turned it into a rigid code and start using it to steer others. For years I kept telling workshop participants that they had to come prepared, and I felt it was my own organisational quirk. One of the teams I work with shortened its quarterly goal-writing session over three quarters from two days to two or three hours. Not because it learned to write goals better, but because it learned what to prepare before the meeting and what information to look for.