The surest way to put people off goals is before anyone writes the first one

This episode is built the other way round from a how-to guide. Instead of a list of good practices, we turn over card after card with behaviours that are very effective at discouraging a team, and almost none of them is a flaw in the method. Usually it is the absence of something that should have happened around it. A tool chosen because another company uses it, without checking whether it fits with everything else or whether a spreadsheet the team already knows would do. Then automatic emails reminding people to fill in data that nobody fills in, because the tool doesn't fit their day-to-day work. Or an objective where only at the final reckoning does it turn out there was no way to tell whether it had been achieved, so half the team is convinced it went well, the other half that it didn't, and the conversation drifts from facts to interpretations.

Under most of the cards sits the same asymmetry. On the board, thinking about direction comes naturally, because there is time for it. An operational person has no moment to step out of their own seat for a while and look at the organisation from the side, and learning only fits into their working hours, because after them there is home and the rest of life. Expecting engagement without a signal, without training and without making room for it is therefore lost before it begins, and the leader's role here is to make things easier, not to demand. The hardest part of the whole cycle turns out to be not planning but drawing conclusions, because it requires admitting discomfort and making decisions. We naturally choose comfortable conclusions and don't name the problem everyone is aware of. The episode also raises a question that is not usually asked aloud: is it the method that isn't working for the team, the way it is run, or the limitations of the person who watches over the process and can't let go.

When we finally sort these cards into phases, something comes out that surprised even us: most of them land before the first quarter. No answer to the question of why we are implementing the method at all, and no metric by which we will know it helps. No strategy for the goals to relate to. No decision by the board to genuinely hand over responsibility, because a declaration of trust alone doesn't replace it. And rolling it out across the whole company at once instead of a pilot, after which the problems of all teams surface at the same moment, and in the end people complain about communication. These gaps aren't visible in phase zero, because nothing is happening yet. You pay for them through all the quarters that follow.