When those conversations sit in separate meetings, a leadership team can miss the relationship between an apparent local success and a wider business constraint.
I favour a small number of shared priorities with explicit decision rights. The review is then used to resolve dependencies and adjust resources. It is less useful as a ceremony in which every function reports activity without exposing the choices it needs help to make.
Review rhythms tend to accumulate rather than evolve. Each function asks for its own slot, each new initiative brings its own steering group, and the calendar slowly becomes a record of past priorities. Within that structure, information travels upwards as reporting rather than as requests for help. Leaders learn that a steady status update is safer than an admission that a dependency is stuck. The consequence is a leadership team that sees a great deal of activity but rarely sees the trade-offs, which are precisely the matters it exists to resolve.
I build the enterprise review agenda from decisions requested, not from updates offered. The pre-read is short and covers exceptions only: where performance has moved outside an agreed range, where a dependency between functions is blocking progress, and where a resource shift is being proposed. Every item states the decision required, the options considered and who owns the consequence. The hardest item is taken first, while the room still has energy. Routine performance is circulated in writing and discussed only when someone has a question that genuinely needs the whole team.
Imagine a business whose sales team is winning contracts in a promising new segment while the service operation is quietly stretching to cope with the onboarding load. Reviewed in separate meetings, both look healthy: sales is ahead of plan and service is meeting its response standards, just. Reviewed together, the connection becomes visible. Service quality for new customers is at risk, and the renewals that justify the segment depend on it. The leadership team can then choose deliberately whether to slow commitments, add capacity or reprice, rather than discovering the choice later through complaints.
A fair objection is that a shared review becomes a bottleneck, drawing decisions to the centre that business leaders should be making themselves. I share that concern. The rhythm should handle only the choices that cut across units or alter enterprise priorities. Everything else belongs with the leaders accountable for delivery, and part of the review's purpose is to make that boundary explicit. If a business leader brings a matter they could have decided alone, I return it to them, and I say so plainly so the rest of the organisation hears the signal.
None of this works without candour, and candour depends on how the chief executive responds when bad news arrives. If the person who raises a stalled dependency is questioned more sharply than the person who stays silent, the organisation will learn silence quickly. I try to thank people for early warnings in the room, and to ask what help they need before asking how it happened. The board has a role as well: when directors see the same short list of priorities that management uses, they can test whether the rhythm is doing its work.
The rhythm is only as good as the decisions it produces. I judge each review by whether something changed afterwards: a resource moved, a dependency resolved, an assumption retired. If three consecutive meetings change nothing, the rhythm has become theatre, and the leadership team needs to redesign it before the organisation learns to perform for it.