The problem with reporting meetings
Many recurring reviews follow the same pattern: someone presents a set of charts, attendees nod, a few questions are asked, and the meeting ends. A month later the same charts are shown again. Information has been shared, but nothing has been decided.
A performance review earns its time slot only when it produces decisions, assigned actions or an explicit choice to leave things as they are. The structure below aims for that.
Decide the purpose and cadence
Be clear about what the review is for. Typical purposes include noticing problems early, deciding where to spend limited effort, checking that a change is working, and holding agreed commitments to account.
Cadence should match the speed of the work:
- A short weekly check for operational queues and issues that need fast action.
- A monthly review for trends, recurring problems and progress on improvement work.
- A quarterly or half-yearly look at the measures themselves, the targets and the overall direction.
Too frequent and the group reacts to noise; too rare and problems grow before anyone notices. Starting a little more often and then adjusting is usually easier than the reverse.
Choose attendees deliberately
The right people are those who can explain the numbers, those who can make decisions, and those who own the actions. Large audiences tend to produce presentations, while small ones tend to produce discussion.
Common roles include:
- a chair who keeps to the agenda and time
- measure owners who can explain movements
- a decision-maker with authority over priorities and resources
- representatives of the people who use the service, where possible
For reviews that span several sites or business units, it helps to agree who speaks for each. This is part of general business unit coordination, and it is better settled beforehand than during the meeting. Some organizations hold such reviews inside an existing steering committee, which can work if the agenda leaves enough room for performance topics.
Prepare in advance
Most of the value comes from preparation.
- Circulate the data a day or two before so that the meeting is not spent reading it.
- Have each measure owner add a short note explaining any notable movement and what they think caused it.
- Mark items needing a decision, separating them from items for information.
- Check that the numbers match their written definitions, and flag any known data issues.
If the data is not trusted, the meeting will drift into arguments about whose number is right. That is a signal to fix definitions and sources, not to hold the meeting anyway.
A simple agenda
A one-hour monthly review might follow this shape. The timings are illustrative.
- Actions from last time (10 minutes). Done, not done, and why.
- Exceptions (20 minutes). Measures outside their agreed range, and what to do about them.
- Trends and early signals (15 minutes). Things that are not yet a problem but may become one.
- Decisions needed (10 minutes). Resourcing, priorities, changes to measures or targets.
- Wrap-up (5 minutes). Read back the actions, owners and dates.
Focusing on exceptions rather than going through every measure keeps the discussion on what needs attention. Measures that are stable and within range can be noted in a line.
Ask better questions
Questions that move a review toward a decision include:
- What changed, and how do we know?
- Is this a one-off or a pattern?
- What is the likely cause, and how confident are we?
- What options do we have, and what would each cost?
- Who will do what by when?
- How will we know it worked?
Questions that stall a review include demands to explain every small fluctuation and requests for yet another report with no stated use. Small movements are often normal variation; knowing the usual range from a performance baseline helps the group tell the difference.
Keep the tone constructive
If people expect to be blamed for a bad number, they will explain it away, adjust how it is counted, or stop reporting it. A blame-heavy review is one of the main drivers of the distortions described in the article on target side effects. Aim to treat a poor result as information about the system. That does not remove accountability for actions; it separates it from defensiveness.
It is also worth inviting dissent. Someone close to the work may say a measure is misleading, or that the numbers look fine while the experience is poor. Such comments are valuable, and staff or customers may need a safe route to raise them, such as feedback from business units.
Record decisions and follow up
Keep a short action log: the action, the owner, the due date and the status. Review it at the start of every meeting. Actions that repeatedly slip should be discussed openly, since they may be unrealistic, unowned or low priority.
Notes should be brief, covering decisions and reasons, rather than a transcript of the discussion.
Review the review
Every so often, ask whether the meeting is still worth holding. Questions to ask: Did recent meetings lead to any decisions? Are the right people attending? Are all the measures still used? Is the cadence right? Retiring a measure or merging two meetings is a perfectly good outcome.
Centralized operations add one more consideration. Reviews should include a way to hear whether central arrangements are slowing down local teams or being worked around. If the evidence points that way, the review is the place to discuss adjusting the model, including governance reviews of how decisions are made.