The Executive Team Meeting That Doesn't Waste the Room

What the room has that no other forum does

An executive team meeting is the one hour in the week when every function's view of the company sits at the same table. The head of product can be asked by the finance director what a change does to margin. The operations head can tell the commercial lead, before a launch rather than after it, what a promise to a client will cost the service desk. That cross-examination is the reason to put eight senior people in one room.

Most executive meetings that feel wasted are not short of structure. They have an agenda, a pre-read and a facilitator, and many have already been cut back to the forums that matter. What they lack is traffic between functions, and the executive team meeting that doesn't waste the room is defined by that traffic more than by its agenda. Without it, each item is presented by its owner, questioned lightly by the chair, and passed.

The lane-keeping pact

The pattern runs on a rule nobody states: I will not comment on your function if you do not comment on mine. It is most stable in teams whose members get on well. A room in which each member speaks only for their own function holds one function's knowledge per item, at the price of eight.

A digital bank we worked with shows the cost. Its product head brought a redesign of account opening to the executive meeting: fewer screens, and a document check moved to after the account was live. Risk confirmed the check would still be performed. Finance noted that the build was in budget. The operations head said nothing, because the item was product's. Three months later the operations team was clearing a queue of accounts opened without documents, by hand, at a cost nobody had approved. The operations head had seen it coming in the meeting and had not considered it their item to speak on.

The silence is easy to read as a culture problem, to be fixed with an offsite and a commitment to candour. The commitment rarely outlasts the offsite, because the pact is not a failure of nerve. Each member who keeps it is responding sensibly to how the team is built.

Why nobody breaks it

Three features of most executive teams sustain it:

• reciprocity, since a member who challenges a peer's item has invited the same scrutiny of their own next week
• asymmetry, since the owner of an item always knows more about it, so a challenge from outside the function risks looking uninformed in front of the chief executive
• scorecards, since each member is measured on their own function's results, and nothing they are measured on rewards improving a colleague's decision

None of these is a matter of temperament. Change the people and keep the structure, and the new team settles into the same pact within a quarter. The silence is produced by the design of the team, so the remedy has to be a change of design rather than an exhortation.

Where the trade-offs go instead

The disagreements do not disappear. They move. Two members with a real conflict settle it between themselves before the meeting, in a form both can live with, and bring the result to the table to be ratified. Or one of them takes it privately to the chief executive, which is one of the ways a weekly meeting becomes a briefing for one person. Either way the room sees a finished position and loses the view of every function that was not party to the side deal.

Since the pact rests on the cost of speaking, the method lowers that cost. In the executive teams we work with, three mechanisms do most of the work. Each turns a challenge from a stance someone has to take into a job someone has been given.

The item names who else it costs

The pre-read for every item, in the form set out in the note on decision meeting structure, gains one line: which other functions carry a cost, a risk or a workload under each option. The owner writes it. A line that reads none is allowed, and it is checked. It hands the named functions an invitation, so that speaking on the item becomes answering a question rather than trespassing.

A second reader from another function

Each contested item is assigned a second reader, a member from a function with no stake in it, chosen by rota. The second reader reads the item a day ahead and brings the two questions their own function's knowledge raises: what the change does to collections, to the call centre, to the sales forecast. This is not a devil's advocate arguing a side for the exercise. It is a member contributing what their function knows, under a role that removes the cost of reciprocity, because next week the roles reverse by the rota rather than by grievance.

The pact is not a failure of nerve.

The cost round before the close

Before an item is closed, the facilitator asks each member in turn for one sentence on what the decision costs their function, or the word nothing. Silence is not accepted as an answer, and an answer of nothing is recorded against the name that gave it. A cost stated in the room can be weighed; a cost discovered after launch can only be absorbed. At the bank, the cost round on the next onboarding change took four minutes. It moved a manual review step out of the operations queue and into the product team's backlog, where it was automated before release.

A shared number on every scorecard

The three mechanisms lower the cost of speaking. They do not remove the reason members stayed quiet, which is that nothing they are measured on rewards a better decision in someone else's function. The structural answer is at least one measure that belongs to the executive team as a whole and appears on every member's scorecard: the cost to serve a customer, or the time from an application to a funded account, which product, risk, operations and finance each move and none of them owns. Once a number is shared, a colleague's item that damages it is everyone's business, and the pact loses its reason.

Reading whether it is working

The evidence is in where problems are found. Over a quarter, the team logs each cross-functional problem with a launch or a commitment and notes where it first surfaced: in the meeting, in a side conversation, or after the fact in the function that absorbed it. A team whose problems surface in the room is using the room. A team whose problems surface downstream is still keeping to its lanes, however well the hour runs.

The first piece of work is an observation. Someone outside the team sits in on two executive meetings and records, for every item, who spoke and whose item it was. Drawn as a grid, a lane-keeping team produces a diagonal: each member speaking on their own items and almost no one else's. The grid usually shows in one page why a well-run hour has stopped producing better decisions.

From there our consulting work inside the operating cadence pillar writes the cost line into the pre-read, sets up the second-reader rota and works with the team on its shared measure, and our training programmes cover the facilitation that holds the cost round when the hour runs short. An executive team meeting stops wasting the room when every item is heard by more functions than the one that brought it.