Almost every leadership team we work with already holds a weekly growth meeting. Almost none of them can say what was decided in the last one. The meeting exists, the calendar slot is protected, the slides are prepared, and the organisation still waits weeks for choices that should take an hour.
This is not a discipline problem in the moral sense. It is a design problem. A meeting with no required output will reliably produce the easiest available output, and the easiest available output is a description of what happened.
What status theatre actually is
Status theatre has three tells. Each is easy to spot in a recording of your own meeting.
- Items are phrased as nouns, not questions. “Pipeline update” instead of “Do we move the two stalled deals to a lower-touch sequence, yes or no?”
- The same items recur, unchanged, for three weeks or more. Recurrence without resolution is the signature of a report that nobody is expected to act on.
- The meeting ends with actions, not decisions. “Follow up with sales” is an action. “We will not discount below 12 per cent this quarter” is a decision.
None of these are caused by weak people. They are caused by an agenda that has no slot for the decision itself. If the template asks for progress, you will get progress. Progress is a report.
Three conditions that turn a review into a decision
A decision can only be taken in a meeting if three things are true before the meeting starts. If any one is missing, the item will turn into a discussion and then into a deferral.
- One question, written as a question, with the options named. If the author cannot write the options, the item is not ready and does not enter the agenda.
- One named owner who is empowered to choose. Not a team, not a function. A person whose authority covers the consequence of the choice.
- A decision date. Either the meeting decides, or the item carries an explicit date by which it will be decided. “Parked” is not a date.
The test we useRead the agenda item aloud. If it can be answered with “thanks, noted”, it is not a decision item. Rewrite it until it cannot.
The third condition is the one teams skip. Without a date, a deferred item returns next week in exactly the same shape, and the theatre continues with better formatting.
What to change on Monday
Three changes, in order. None requires a new tool, and all three survive a change of leadership, which is the point.
- Open every review with the decision log from last week. Read the decisions taken, and confirm each one was executed. Not reported on. Executed, or explicitly reversed with a reason.
- Cap the agenda at the number of decisions the room can actually take. Five is usually honest. Fifteen is a list of things that will not be decided.
- End by writing the log entry aloud: what was decided, who owns it, when it will be reviewed. If the sentence cannot be finished, the item is not closed.
| Signal | Before | After |
|---|---|---|
| Agenda items phrased as | Nouns and topics | Questions with options |
| Meeting ends with | Actions and follow-ups | Decisions and dates |
| Item lifetime | Recurs indefinitely | Closed, or dated |
| Manager preparation | Slides of progress | One page with a recommendation |
The decision log matters more than the agenda. An agenda shapes one meeting; a log shapes the next fifty, because it makes the cost of an undecided item visible. Once a team sees the same item on the log for a month, the social pressure to decide stops being something a manager has to enforce.
What this does not fix
A decision log will not fix a room where the most senior person has already decided and everyone is waiting for the meeting to catch up. That is a different problem, and no template solves it. It also will not fix a team that lacks the data to see the options. If the numbers are contested, the meeting becomes a debate about the numbers, and the decision is deferred until the numbers are agreed. Fix the numbers first.
What it does fix is the common case: a competent team, a full calendar, and no artefact that forces a choice. That case is the majority of the meetings we sit in.
One warning that is worth stating plainly. A decision log is a record of what the organisation chose, which means it is also a record of who chose badly. Teams will resist it for that reason, and the resistance will be dressed up as a process objection. Expect it, and be explicit that the log exists to make reversal cheap, not to assign blame.
Sources and further reading
- Strathern, M. “‘Improving Ratings’: Audit in the British University System.” European Review 5, no. 3 (1997): 305–321. The source of the widely quoted formulation of Goodhart’s law.
- Goodhart, C. A. E. “Problems of Monetary Management: The U.K. Experience.” Papers in Monetary Economics, Reserve Bank of Australia, 1975. The original observation.
- Our own observation, stated as such: the three-tell diagnosis above comes from field work with leadership teams, not from a controlled study. It is experience, not evidence.
