Cascading OKRs: We can do Better

Repeating my comment from a previous thread:

I still chuckle when I recall this tweet, "OKRs were actually a psyop from Google to slow down potential early stage competitors" [1].

[1] https://x.com/benwbear/status/1543056694330003456

Look at the table of contents, the fourth topic down:

https://www.scribd.com/document/394284634/The-Beginners-Guid...

Now go to page 17 to read how "OKRs do not cascade".

Just say no to OKRs.

The punchline: > OKRs Cascade Upward to Strategy, not OKRs.

Alternatively: OKRs can be an effective way to summarise a strategy conversation that has actually happened. Outside of that, caution is advised.

One of the interesting things about theory is sometimes it lets you short circuit entire ideas. For example, if someone comes up with a perpetual motion machine it makes sense to ask how they broke Thermodynamics Law 1/deleted friction. If they don't have an answer then it isn't necessary to look at any of the details to conclude the machine can't work.

With OKRs, the question is "how did you get around the problem where we can't measure programming productivity?". That is an unsolved problem in software engineering and it is impossible to design a better OKR system until it is resolved. Managers just have to wing it based on their personal opinions, things will work or fail at random, largely independent of the OKRs used.

If senior management wants to give their software teams nonsensical OKRs, the company's problem is that their senior managers are bad. Arguing with them about the OKRs probably won't make them better at managing the company and, frankly, I suspect it would be more productive just to get one of the engineers to bake a slice of something that looks like pie quickly one weekend rather than fight a losing battle on an unimportant hill. A company with nonsensical OKRs is going to have to make a habit of ignoring the OKRs anyway; the senior management can't use them for anything so all the junior managers will have to ignore them in sync. Ask the senior managers what they want at the water cooler once a fortnight and set the sprints up to deliver in that direction + some pie slices on occasion.

TLDR; I don't think articles that talk about better ways to do OKRs are the path to a better place.

OKR considered harmful:

https://www.radicalproduct.com/blog/okrs-criticism#:~:text=U....

Get this trash away from software engineering if your real goal is delivering working software and value.

It‘s purely a busy pretend work toy for management detached from real work and careerists that like to talk about increasing visibility, etc.