Coffee with OKRs · 4 min read
Writing the goals is the easy part. The hard part is making them part of company life
This episode is a preview of a workshop, and we say so straight away so that nobody is caught off guard. It is worth watching for a different reason: to see a whole implementation laid out in blocks, from deciding whether to implement at all to closing the first cycle.
From the episode · in Polish
An implementation laid out in ten blocks
The episode goes step by step through the workshop programme, that is, through the ten blocks of an implementation: when OKRs make sense, where a good objective comes from, what structure to choose, how to plan communication, how long a cycle should be and how to close the first one. The part on the structure of objectives and on the cascade from the Google material starts at around the thirtieth minute. This is a promotional recording, so part of the time goes on describing the training itself. from 00:30:52
The recording is being edited. Leave your address and you'll get the link when it's ready.The episode has one claim, and it runs against the way OKRs are often sold. Setting goals for an organisation is usually the easier part. The hard part is getting those goals to actually become part of company life and getting anyone to use them. That is where the blockers are, not in the writing itself. The biggest of them is not a lack of knowledge about the method, but not knowing what the next step is, and the discouragement that follows. A book about OKRs reads logically, and the blockers only appear when you try to do anything in your own company.
That is why the first block of an implementation is not writing goals, but sorting your own problems into two piles: those OKRs really address and those they won't touch. OKRs on their own won't turn micromanagement into managing for outcomes, they push in that direction and that is all. The second filter concerns language. I want to improve transparency and I want to improve alignment are sentences that mean a lot and nothing at all, and they are exactly where most implementations begin. Workshop participants get them back as homework, to make them concrete for their own company: what exactly is supposed to be visible, to whom and when. This is one of the more frequent moments when something surprises people.
The third point corrects a picture many people carry in their heads as the definition of the method. The cascade of objectives running from the company level through teams all the way down to personal objectives comes from a Google material from 2012, which Google itself later stepped back from. The material is still circulating and still shaping ideas, and a structure of objectives doesn't have to be multi-level to work. It is similar with communication: everyone knows it matters, so nobody plans it, and when an implementation isn't working, what is usually missing is communication in a specific place, not the goals themselves.
To be honest about the episode itself: it is promotional, and part of the material is a description of the programme rather than content in its own right. One thing from it is worth repeating, though, because it concerns our own mistake. The first edition of this workshop lasted one day, and only participants' feedback showed that this much material can't be absorbed in a single day. We split it into two, and the hours keep growing anyway.
Takeaways
Three things worth taking from this episode
- 01
The hard part starts after the goals are written
Setting goals for an organisation is relatively easy. Implementations break down only when people try to put them into practice, and the biggest blocker is not knowing what the next step is.
- 02
Sort your problems first, then write goals
List your problems and divide them into those OKRs address and those they won't touch. Make statements about transparency and agreeing on direction concrete before they become an objective.
- 03
The cascade down to personal objectives is someone else's material from years ago
The picture of objectives running all the way down to the level of a single person comes from a Google video from 2012, which its author has stepped back from. Choose the simplest structure that works for you.
The whole topic in one place
OKR implementation in a nutshell
The blocks described above are a training programme, so naturally they show the scope rather than the course of events. What it looks like in a specific company, stage by stage and in what order, we have described separately, in the text that brings this whole thread together. That is also where you will find the full set of episodes on implementations, with a note on what each one adds.
Author

Lena Zhukova
founder; strategy workshops, quarterly sessions
Founder of OKR Poland. For twenty years she has worked with boards of companies from 30 to a few thousand people; she wrote dozens of strategies with them and helped implement them in more than 40 organisations.
Next texts by e-mail
The OKR Poland newsletter
We write when we have something to say. To start: eight hours of recording on preparing a company for strategy workshops, plus the OnePager.
