Briefing: reading an operating model in ninety minutes

The briefing walks through the diagnostic in the order we actually run it. First, the calendar audit. We read whose time the executive committee actually spends, on what, and how far that is from what the strategy says matters, and we take it from the calendar itself rather than from anyone in the room, because the two accounts rarely agree. In the recorded session the gap is 61%. Three of every five leadership hours went to subjects the strategy does not mention.

Second, the decision trace: the last ten significant decisions, timed from necessity to communication. The recorded organisation averaged 29 days. The longest was a pricing decision, at 96. Third, the initiative register, which is everything in flight, tested against the question nobody asks out loud. Who would notice if this stopped?

The session ends with three numbers on one page: the attention gap, the median decision latency, and the load ratio, which sets initiatives in flight against measured capacity. Together they describe the operating model as it is rather than as the organisation chart draws it. In our experience the room recognises the description immediately. It has simply never seen it written down. What ninety minutes will not tell you is why the gap opened in the first place, and we have learned not to speculate about that in the room, because the explanation offered first tends to be the one that costs the room least.

Three instruments carry the session, and all three are published in the framework library and may be applied without licence: the calendar audit template, the decision trace protocol, and the load register. None of it is proprietary. The briefing closes on the question the diagnostic exists to sharpen. We are not asking whether the operating model is good. We are asking whether it can carry what you are about to ask of it.