The reporting trap
A review can be full of accurate information and still leave the organisation exactly where it was. Each function reports its work, the pack shows red and amber items, leaders ask for explanations, and the meeting ends with actions to provide more updates. The unresolved choice—what to stop, change, fund or escalate—moves to the next meeting.
This is a common management pattern offered as an illustration, not a Forward Matter client result. Reporting is useful when it prepares a choice. It becomes costly when a forum rewards a complete narrative more than a clear decision. The test is simple: what changed because this review happened?
Give each forum a decision purpose
Before redesigning the slides, write down the decisions that belong in the forum. A weekly leadership review may unblock delivery and resolve immediate dependencies. A monthly review may reallocate capacity, revisit risks and adjust commitments. A quarterly review may reset the portfolio and its intended outcomes. The exact cadence depends on the organisation; the authority to decide matters more than the calendar.
For each forum, define its decision boundary: what the group may decide, what it must recommend elsewhere, and what belongs with a named owner outside the meeting. If every issue is escalated without a clear owner, the review is a queue. If every topic is discussed without a decision right, it is a broadcast.
Build the agenda around exceptions and choices
Start with the outcome or commitment at risk, not a tour of every workstream. Ask what has changed since the last review, why it matters now, and which choice would improve the situation. An issue needs a proposed decision, credible options, the consequence of waiting and the person with authority to choose. Routine updates can be read beforehand.
A useful agenda entry might say: “The next 90-day commitment depends on a specialist team already assigned to two other priorities. Decide whether to defer one initiative, reduce scope, or add capacity, with the associated cost and delay.” That gives leaders a decision to make. “Capacity is amber” does not.
Keep the evidence small and honest
The pack should show the intended outcome, current signal, confidence in that signal, material constraint and the choice required. Trend matters more than colour alone. A green status based on completed activity can conceal an outcome that is not moving. A red signal can be healthy if it exposes an assumption early enough to change course.
Distinguish a fact from an interpretation and a request. “The milestone moved two weeks” is a fact. “The delay is caused by an approval bottleneck” is a hypothesis to test. “Approve a different sequence today” is a decision request. If the evidence is weak, record what must be learned and when, instead of manufacturing certainty.
Use a decision record that changes the work
At the end of each discussion, capture the decision, its reason, the accountable owner, the affected commitments and when the effect will be checked. A decision such as “continue to monitor” should name the threshold that would trigger action. An unresolved issue should have an owner and an explicit return date.
At the next review, check whether the decision was implemented and whether it had the expected effect. This closes the loop between leadership and delivery. Without it, the same constraint can be narrated every month while teams absorb the consequences.
A 20-minute test for your next review
Take the last three leadership review packs and minutes. For each meeting, count the material decisions made, not the number of actions assigned. Identify the items that appeared more than once without a decision. Then ask: Did the right person have authority in the room? Was there a choice with options? Was the evidence good enough? Did a decision change a priority, capacity, ownership or sequence?
Choose one recurring item for the next agenda. Write a one-page decision brief with the choice, two or three realistic options, the trade-off of each, the recommendation and a date by which the decision is needed. Send routine status in advance. Use the meeting to make and record the choice. This is a small test of whether the forum is designed for decisions.
When the problem runs deeper than the meeting
Sometimes the agenda is the problem. Often it is a symptom: priorities exceed capacity, ownership is split across functions, or no forum has the authority to resolve a trade-off. A tighter meeting will expose that constraint but cannot resolve it on its own.
Forward Matter's free Execution Health Check can help you assess whether Rhythm, Ownership, Priorities and Planning are connected in your organisation. Use it when several forums keep revisiting the same unresolved issues. If the constraint is already clear, focus first on the decision rights and operating rhythm needed to change the work.