Meetings are the operating system of execution

Execution sits between functions

Most work that matters to the whole enterprise does not belong to one executive. Growth brings commercial, operational and financial choices together. Transformation links technology, people and the business. An operating-model change creates dependencies between functions, regions and business units.

Each leader can analyse and act within their own area. The leadership team is needed where those areas meet: to interpret shared information, expose competing priorities, settle dependencies and make choices that no function can make alone. A well-run meeting gives that collective work a proper forum.

When the formal meetings do not perform that role, coordination moves elsewhere. It appears in email chains, bilateral calls, escalations, informal alliances and meetings before the meeting. The work has not disappeared. It has become slower, harder to see and less clearly owned.

A calendar needs an operating rhythm

Many leadership teams meet constantly without running the business together. Their calendars contain reviews, steering groups, project updates and presentations, yet the same cross-functional problems return each week. A strategic question receives five minutes at the end of an operational review; a tactical obstacle consumes the time reserved for longer-term thinking; the monthly meeting repeats the weekly meeting with more polished slides.

The problem is often that meetings have been designed as individual events. Each has an agenda, but its role in the wider operating rhythm is vague. Subjects travel between forums, decision rights change from one room to the next, and leaders prepare for the meeting in front of them without knowing how it connects to the next one.

The Table Group separates this work into a daily check-in, weekly tactical meeting, ad hoc strategic discussion and quarterly off-site. The labels and cadence can change; mixing all four jobs in one recurring meeting is what causes trouble.

Use the room for work that needs the team

A standing agenda is useful only while it reflects the work. Functional updates and project reports can create an orderly meeting while displacing the issues that currently need collective attention. Review priorities and the team’s scorecard first, then choose the obstacles and performance signals that require discussion. Move a strategic issue into a forum with the time and preparation it deserves.

Presentations need the same discipline. Slides can structure information and create a record, but they can also turn the meeting into a sequence of broadcasts. One person presents, others listen selectively, and questions wait until the end. The difficult issue appears on slide 36, just as the available time runs out. The team has received information without doing much work together.

What happened in this meeting that could not have happened if everyone had read the material alone?

If the answer is very little, the meeting was probably unnecessary or badly designed. Information can be distributed before or after. Time together should be kept for interpretation, challenge, integration, decisions and accountability.

Make disagreement usable

Leadership decisions contain legitimate tensions: speed and certainty, global consistency and local discretion, growth and margin, investment for the future and performance this year. No individual function can resolve these choices on behalf of the enterprise.

Meeting design can still suppress the disagreement needed to reach a sound decision. A crowded agenda rewards brevity. A pre-read built around one preferred answer narrows the discussion too early. Abstract language conceals the practical trade-off. When the chair closes at the first sign of resistance, the minutes may show a decision while the disagreement continues through other channels.

The Table Group argues that important issues should be brought forward and worked through until the team reaches resolution. Strategic discussions need a clearly defined issue, adequate preparation and enough time for genuine debate. Its Five Dysfunctions model connects productive conflict with commitment: leaders are more likely to support a decision when the relevant concerns have been heard and answered, even when their preferred option is not chosen.

The meeting leader has to protect that process. This may mean slowing the conversation, naming the trade-off, asking for the case against the proposed answer or drawing in a leader whose concerns are appearing only outside the room. The aim is not prolonged argument. It is a decision whose reasoning and consequences are understood by the people expected to carry it out.

Turn decisions into visible commitments

A meeting can end with apparent clarity while leaving several interpretations behind. Phrases such as “continue the discussion”, “explore options” and “socialise with stakeholders” may describe sensible next steps. They can also postpone ownership unless the team is explicit about what happens next.

Before a consequential item begins, participants should know the expected outcome. The purpose might be to share information, generate options, advise a decision-maker, make a recommendation or take the final decision. Decision authority must be equally clear. Otherwise, people can leave the same exchange with different beliefs about what was agreed.

A decision should alter something observable: a priority, resource allocation, owner, deadline or required behaviour. Record the decision in plain language, together with the person responsible and the date by which the commitment will be met. This is a better test of clarity than the apparent agreement in the room.

Record decisions and commitments and review them later. A short commitment review in the next relevant meeting makes delivery part of the operating rhythm. If an action is late or circumstances have changed, the team can address the reason, consequence and revised commitment directly. Accountability becomes credible when leaders know that what they agreed will return to the table and that colleagues, rather than only the CEO, can challenge non-delivery.

The leader establishes the meeting discipline

Every meeting teaches people how the next one will work. An uninterrupted fifteen-minute monologue shows that airtime is unmanaged. Repeatedly postponing a difficult subject shows that discomfort can control the agenda. Allowing two executives to settle matters privately afterwards tells the rest of the team that the formal forum is not where decisions are really made.

The person leading the meeting shapes these norms through small, repeated choices: when to interrupt, when to invite a quieter view, when to insist that disagreement becomes explicit and when to close. The practical closing question remains useful: who will do what by when? Meeting leadership is less about polished facilitation than protecting the purpose of the team.

This discipline can require more distinct meetings, not fewer calendar entries. The Table Group estimates that a structured rhythm of its four meeting types occupies roughly one fifth of a leader’s time. Its argument is that this investment reduces the informal “sneaker time” spent chasing information, clarifying ambiguous decisions, repairing misunderstandings and joining extra calls outside the room.

The relevant measure is the organisation’s total coordination load. Removing a recurring meeting saves time only if the work it contained is removed or handled better elsewhere.

Audit the meetings before redesigning the organisation

When execution slows, organisations often reach for structural answers: new governance, reporting lines, decision-rights frameworks, transformation offices or additional roles. Some of these changes may be necessary. They should follow a clear view of how the existing leadership system is working.

Choose three consequential decisions from the last quarter and trace each one: where it surfaced, where it was debated, who decided, how the decision travelled and whether the commitment returned for review. The gaps between those points reveal more than a calendar inventory.

Then examine the behaviour inside the room. Useful meetings surface problems early, make trade-offs discussable, produce decisions people can explain and allow executives to hold one another to their commitments. Attendance, agenda design, pre-reads and minutes matter because they support those outcomes, not as administrative ends in themselves.

An audit may show that the organisation genuinely needs different roles or reporting lines. It may also show that the existing leadership team has no reliable place to perform its shared work. Changing the chart without repairing that operating rhythm moves the same unresolved decisions into a new structure.

Every leadership team has meetings. The final test is straightforward: do those meetings help the organisation execute, or do they merely occupy the people responsible for running it?