Three retrospective questions only get you in. The value is in the fourth

An end-of-quarter review contains two different meetings, and many companies hold only the first. The first is accounting for results: the values of the key results, the state of delivery, the numbers. The second is a retrospective of the process, a conversation about how we got to those numbers. In it the numbers are where the discussion starts, not the final truth, and that is exactly why it is better for someone other than the objective owner to present them. The person who carried the objective through the quarter is attached to it, which is normal, but it makes it harder for them to look at the result from the outside. It is also worth looking wider than the key results alone and asking what changed during the quarter in processes, in responsibilities and in the organisation itself.

A retrospective usually asks three questions: what to start doing, what to stop, what to continue. They are only the way in. The value is in the fourth, the question of why it worked and why it didn't, dug into layer after layer until the answer stops being a first reflex. For it to be answerable at all, the objectives have to be set at the beginning of the quarter as hypotheses to be tested. The review then stops being an argument about whether the objective was met and turns into a decision about the next step. In the episode we show this on a hypothesis about a chosen client segment, tested on two axes at once: whether enough clients of that kind can be won, and whether they can be served at the expected level. Confirmation of both meant scaling up in the following quarter. A stumble on the service side would have sent the work towards internal processes rather than sales.

The third thread is cultural, and it is the one that most often drops off the agenda. A review slides by default into looking for what went wrong, so a slot for successes has to be planned: twenty to thirty minutes in which everyone shares their own or praises someone else's. This isn't decoration. Good practices are what get scaled, and a practice nobody has named has no way of reaching the rest of the organisation. Connected to this is something I still have no good method for. At a joint retrospective with a leader and their direct reports in the room, you hear eighty per cent of the truth, and the twenty left unsaid is usually exactly what is blocking the team. One-to-one conversations before the meeting help, but they cost time, which at the end of a quarter is in shortest supply.