Insights

Executive Teams

The decisions an executive team must own together

Executive teams create enterprise value when they reserve collective attention for the consequential choices that no function, committee or individual leader can make well alone.

Four executives concentrating on one shared decision token at the centre of a round boardroom table.
Collective leadership does not mean every decision belongs to the collective.

Executive teams are often criticised for slow decisions. The visible symptoms are familiar: too many meetings, extended consultation, repeated debate and choices that return to the agenda after they were apparently settled.

The instinctive response is to demand more speed.

But speed is rarely the first design question. The more important question is whether the decision belongs in the executive room at all—and, if it does, what the team must contribute that no individual can provide.

Some leadership teams pull too many decisions upward. Executives become the approval layer for work that should sit within clear delegated authority. Others move in the opposite direction. Important cross-enterprise choices are dispersed across functions, with no forum capable of resolving the consequences for the whole organisation.

Both patterns weaken accountability.

Research on decision effectiveness suggests that high-quality, high-velocity decision-making is associated with stronger organisational performance, while the time executives invest in decisions is often experienced as poorly used.[1] Tools such as Bain’s RAPID framework have become influential because they make decision roles explicit: who recommends, agrees, performs, provides input and decides.[2]

The framework matters. The prior leadership judgement matters more: which choices require collective enterprise work, and which require the discipline to let someone else decide?

Three classes of executive decision

An executive team can clarify its role by distinguishing three classes.

Decisions the team must own together

These are choices whose consequences cross several accountabilities and materially shape enterprise value, risk or identity. They may include strategy, capital and resource allocation, transformation sequencing, enterprise operating-model choices, culture-shaping standards and succession for critical leadership roles.

The team’s responsibility is not necessarily unanimity. It is to bring the relevant enterprise perspectives into the choice, expose trade-offs and create commitment across the system that must deliver it.

Decisions the team should shape but one person must own

Many consequential choices benefit from executive input but require a single accountable decision-maker. A product launch, market entry recommendation, technology architecture or workforce change may cross boundaries, yet clarity still depends on one person holding the decision.

The executive team should contribute evidence and implications without converting input into collective veto rights.

Decisions the team should deliberately release

If a choice can be made well within one leader’s mandate and agreed guardrails, bringing it to the executive team usually adds delay rather than value. Delegation is not the absence of governance. It requires clarity about outcomes, risk tolerance, consultation and when escalation is expected.

The strongest executive teams are as disciplined about what they will not decide as what they will.

Why decisions become congested

Decision congestion is sometimes described as a process defect. Often it reflects a deeper leadership tension.

Authority is ambiguous. Several people believe they have approval rights; no one is sure whose judgement is final.

Participation is confused with ownership. Because stakeholders deserve input, they are treated as though they must agree. Consultation expands until commitment becomes impossible.

The decision has not been framed. Leaders debate solutions before agreeing on the problem, criteria, constraints and time horizon. Different answers are inevitable because people are answering different questions.

Trust is low. Decisions are pulled upward because leaders do not trust how judgement will be exercised below them—or because previous decisions have been made without the promised consultation.

Functional identity dominates. Executives enter the room as advocates for their domains rather than stewards of the enterprise. Debate becomes negotiation among interests.

These conditions cannot be solved by placing an acronym beside every agenda item. They require a team to examine how power, expertise and accountability actually operate.

A decision discipline for the executive room

For major choices, five questions create useful discipline.

What exactly are we deciding? A well-formed decision statement is specific enough that the team will know when it has decided. “Discuss digital” is a topic. “Decide whether to consolidate customer data onto one platform over the next 18 months” is a decision.

Why does this decision belong here? The answer should identify the enterprise value, risk or interdependence that requires executive attention. If it cannot, the choice may be better placed elsewhere.

Who holds the decision? Collective input should not obscure final accountability. Even when a board formally approves or an executive team collectively endorses, the organisation needs to know who will carry the decision into delivery.

What must be true? Explicit criteria improve the quality of disagreement. Leaders can test strategic fit, customer impact, financial value, risk, capability and reversibility without arguing only from positional preference.

What happens after the decision? A decision without a communication path, delivery owner and point of review is an intention. The team should agree how the choice will travel and what evidence will bring it back.

Candour before commitment

Good decision discipline is not an argument for sterile process. Consequential choices involve uncertainty, judgement and competing values. The quality of the conversation matters.

Edmondson’s research on psychological safety shows how a shared sense of interpersonal safety supports learning behaviour.[3] In an executive team, that safety should enable—not dilute—challenge. Leaders need to present disconfirming evidence, acknowledge uncertainty and question the assumptions of more powerful colleagues.

The test is what happens next. Once a decision is made, executives must be able to commit without pretending the debate never occurred. Private relitigation is particularly damaging: it weakens the choice, fragments communication and teaches the organisation that formal decisions remain provisional.

This is why decision quality and team effectiveness are inseparable. A team that cannot disagree honestly will make fragile decisions. A team that cannot commit afterwards will struggle to execute even good ones.

Decision rights reveal the operating model

In executive roles across integrated businesses, I have seen decision confusion create more friction than structural complexity alone. People can work across countries, functions and business units when they understand where judgement sits and how their perspective will be used. They struggle when every boundary becomes a negotiation.

Mapping a small number of recurring enterprise decisions can therefore be more valuable than rewriting a complete authority manual. Choose the decisions that currently consume time, cross boundaries or repeatedly reopen. Clarify the decision statement, owner, contributors, criteria and follow-through. Then observe what the exercise reveals about strategy, trust and capability.

Decision rights are not merely boxes on a governance chart. They are one of the clearest expressions of how an organisation expects leadership to work.

The objective is not to make every decision collective. It is to make collective leadership available where only the executive team can create the necessary enterprise judgement—and to release the rest with confidence.

Five decisions to examine

  • Which recurring choice currently consumes disproportionate executive time?
  • What important enterprise decision has no natural home?
  • Where has “input” quietly become a veto?
  • Which decision should move closer to customers or delivery?
  • What choice has been made formally but not yet accepted behaviourally?

Sources and further reading

  1. McKinsey & Company (2018), “Decision making in the age of urgency.” https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/decision-making-in-the-age-of-urgency
  2. Bain & Company, “RAPID Decision Making.” https://www.bain.com/insights/management-tools-rapid-decision-making/
  3. Edmondson, A. C. (1999), “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly, 44(2), 350–383. https://doi.org/10.2307/2666999
  4. Vroom, V. H. (2000), “Leadership and the Decision-Making Process,” Organizational Dynamics, 28(4), 82–94. https://doi.org/10.1016/S0090-2616(00)00003-6
  5. McKinsey & Company (2025), “Demystifying top-team performance: What every CEO needs to know.” https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/demystifying-top-team-performance-what-every-ceo-needs-to-know