Think of the last leadership team meeting you attended. How much of it was people reading updates that could have been an email? How many decisions left the room with a named owner and a date?
The leadership team meeting is the most expensive recurring meeting in most organizations, measured by the salaries in the room. It is also the place where cross-functional problems should get resolved. When it becomes a round of updates, those problems move into side conversations and escalation emails.
What the meeting is for
A useful way to define the purpose: the leadership team meeting exists to make decisions that need more than one leader, to resolve cross-functional conflicts, and to review whether commitments are on track. Information sharing is a support activity, not the purpose. If something can be read, it should be read before the meeting.
Replace spoken updates with a written pre-read
Ask each leader to submit a short written update by a set time before the meeting, using a consistent format:
- Progress on commitments since last time.
- Items at risk, with a reason and what is needed.
- Decisions needed from this group, with a recommendation.
Everyone reads it first. The meeting then starts with the second and third items. This alone often recovers half the meeting's time.
Use a fixed agenda with time boxes
A typical structure for a 60-minute meeting looks like this:
- Review commitments (10 minutes). Anything due or overdue. Closed items are noted quickly. At-risk items are flagged for discussion.
- Decisions (30 minutes). Two or three items, each with a named owner, a recommendation, and the options considered. The group decides or sends it to a defined escalation route.
- Cross-functional issues (15 minutes). Problems that involve more than one function and cannot be solved by two people offline.
- Close (5 minutes). Read back the decisions and commitments, each with an owner and a date.
The details can vary. The principle is to protect time for decisions and place the commitment review at the start so the meeting stays tied to what was promised.
Run a decision, not a discussion
For each decision item, the owner states the question, the options, and a recommendation in a few minutes. Others ask clarifying questions, then offer positions. The decision owner decides, or the group votes if that is the agreed method. Before moving on, state the decision aloud and name who will carry it out. A decision with no owner is likely to return next month.
Handle the topic that does not fit
Some topics belong elsewhere: a two-person issue, a detailed technical debate, or something that needs more information. Keep a visible "parking" list with an owner for each item and a date for when it will return, in a smaller group or in the agenda. Parking is only useful if the list is actually revisited.
Leader behaviors that make or break the meeting
- Start and end on time. Late starts teach people that the agenda is flexible.
- Do not re-decide in the room. If a decision was owned by someone, support it unless new information justifies reopening.
- Ask quiet people directly. Strong perspectives often come from the leader who has not spoken yet.
- Close with a read-back. It takes two minutes and prevents most misunderstandings.
A four-week trial
Do not announce a big redesign. Change the format for four weeks and ask for feedback at the end. Track two simple measures: how many decisions left the meeting with an owner and date, and how many agenda items were repeats from earlier weeks. If repeats fall and owned decisions rise, the format is doing its job.
The Culture-to-Execution Sprint includes building a repeatable leadership meeting rhythm as one of its outputs for intact teams working on one live priority.