As long as you hand out tasks, your capacity caps the whole organisation

The second version looks almost the same and works differently. You come to the managers not with a list of reports but with context and with the outcome you are after, an improvement in that product's profitability. From that moment the conversation in the meeting is no longer about the format of a report but about ideas. That is the whole difference between delegating tasks and delegating outcomes, and it sounds trivial until you count what you lose along the way. Habit also pulls back towards the old way harder than it seems: in this very conversation the phrase about a task done well keeps coming back by reflex, even while we spend an hour talking about outcomes.

You lose three things. First, you become the bottleneck yourself, because at some point your own capacity turns into the limit of the whole organisation, and it won't go any further until you start working differently. Second, the tasks you handed out came from your assumptions, and you look at the process from above and from a distance, so your idea of a solution can simply miss the mark, even if everyone did their part perfectly. The third is the most costly and the hardest to notice, because it looks like a trait of the team. Complaining that people show no initiative usually describes the style of delegation, not the people. If someone brings an outcome and hears several times in a row that something else was meant, they stop using their own head and start doing exactly what they are told. It is hard to hold that against them afterwards.

OKRs come in through a side door here, and that is the real thesis of this episode. To write a good quarterly objective you have to go through the mission, vision, strategy and annual goals anyway, so along the way you end up with a ready story that can be told in no more than five minutes. That is exactly the material a doer needs to connect the dots instead of waiting for the next instruction. The episode gives the example of a freelancer hired to generate leads: before a word is said about tasks, they get the context of the organisation, the problem to solve and an agreement on an outcome counted as five leads a week, and thanks to that they start proposing solutions themselves. Providing that context is not a courtesy to the team, it is the main job of the board and managers. If they can't pass it on and support people in delivering, they aren't doing their own job.