Skip to main content
Steady at the Top
← All articles

How to build an executive team that can disagree and deliver

Build executive trust through explicit practices for challenging proposals, making decisions, carrying out commitments, and repairing failures. Apply those practices to real work. The team needs to know how a disagreement reaches a decision and what happens after the decision is made.

Team psychological safety is a shared belief that members can take interpersonal risks within their team. Amy Edmondson develops the construct in her 1999 study, Psychological Safety and Learning Behavior in Work Teams. The study associates psychological safety with learning behavior in work teams.

Safety to question a plan differs from agreement with the plan. It also differs from dependability in delivering a commitment. An executive team needs room to expose a weak assumption and a clear way to hold the resulting work accountable.

Start with the decisions that keep returning

An executive group may appear agreeable in meetings while reopening decisions through separate conversations. Another group may argue intensely but leave without a clear owner or conclusion. Both patterns can obstruct delivery.

Select a recent consequential decision and reconstruct its path. What proposal was considered? Who challenged it? Who had authority to decide? What commitment followed? What happened when someone later disagreed?

The answers reveal the operating problem more precisely than a general claim that the team lacks trust. A missing decision owner calls for a different correction from a CEO who humiliates people for reporting problems.

If the group has become divided into persistent alliances, use the executive faction-conflict guide. A working agreement needs a fair discussion process; it should not become a document one faction imposes on another.

The meeting replayed at the kitchen table

In a composite private scene, a CEO returns home after an apparently successful executive meeting. During dinner, messages arrive from two executives asking to revisit separate parts of the decision.

The CEO begins answering each privately. By the end of the evening, the plan has several versions, and the original owner does not know which one controls the work.

The problem is observable: the team has no shared route for reopening a decision. The CEO’s individual accommodations may be well intended and still make the ambiguity worse.

Preserve the questions and return them to the authorized decision route. Distinguish genuinely new information from dissatisfaction with a choice already made. Both can deserve attention, but they need not have the same effect on execution.

Create an executive disagreement-and-delivery agreement

An executive disagreement-and-delivery agreement is a proposed set of practices for evidence, challenge, authority, commitment, reopening, and repair. It is not a validated psychological intervention or a substitute for formal governance.

Build it around a real decision rather than a list of values everyone can endorse abstractly. Keep the agreement short enough to use during the next meeting.

1. Establish authority and the decision question

For the selected decision, identify who recommends, who provides required input, who decides, and who owns delivery. Check these roles against actual governance and operating authority.

The APA’s 2018 role-ambiguity entry describes unclear behavioral expectations in a position. That concept helps distinguish an authority gap from a personality conflict. If nobody knows who can decide, more candor alone will not close the gap.

State what the decision must settle. An open discussion about “customer experience” may contain several choices with different owners. Separate them before asking the group to commit.

2. Define how evidence and challenge enter the discussion

Ask the proposal owner to state the recommendation, supporting evidence, assumptions, alternatives, and important uncertainties. Give relevant executives a fair opportunity to question the account.

Agree on conduct that makes the challenge usable. Ask for a specific objection or missing fact. Do not require a complete replacement plan before someone may identify a consequential flaw.

The CEO should follow the same standards. An invitation to disagree has little practical value if the first objection receives ridicule or an immediate loyalty test. Address inappropriate conduct directly through the applicable management or independent process.

3. Close the decision with an executable commitment

At the decision point, state the chosen option, owner, resources, timing, and dependencies. Record important conditions and unresolved questions. Ask the delivery owner to explain what they will do next.

Distinguish consent from compliance with an authorized decision. An executive may retain a substantive objection while being responsible for implementing the chosen plan within their role.

Do not use this distinction to suppress legal, safety, ethical, or other concerns that require escalation. A working agreement cannot waive reporting rights or authorize improper conduct.

4. Set a route for reopening and changed information

Define which developments require reconsideration and who can authorize it. New customer evidence, a failed dependency, or a material resource change may matter. The relevant threshold depends on the decision.

Require a reopening request to identify what changed and which part of the decision it affects. This makes the request assessable without treating it as disloyalty.

Stop making contradictory private instructions. If the CEO changes a decision through the proper authority, update the owner and affected team. Preserve the version history so people can understand why the plan changed.

5. Review delivery and repair failures in the agreement

At the next work review, compare commitments with actual results. Identify whether a failure came from an unrealistic assumption, missing input, unclear ownership, or conduct that violated the agreed process.

Address the specific failure and its consequences. If someone broke a commitment, use the promise-repair guide to establish the account and a feasible response.

Revise a rule when the work shows it is unhelpful. Do not treat the agreement as a test of personal virtue. Its purpose is to give the team a usable route from disagreement to delivery.

Apply the agreement to a disputed launch

Imagine a hypothetical team deciding whether to launch a service next month. Sales supports the date because customers are waiting. Operations says the support workflow is incomplete. Finance wants the cost of a delay made explicit.

The CEO can identify the decision, invite the competing evidence, and establish who will approve readiness. The team may choose a phased launch, a delay, or another feasible option. The example does not establish which option is correct.

A useful closing could be:

“We have decided on this launch sequence with the conditions recorded here. Operations owns the readiness check, and the approved owner can reopen the date if that check fails. Bring new evidence through that route so the teams receive one current plan.”

Use the wording only when it matches the actual authority. A recorded condition should be something the responsible owner can inspect, not a vague instruction to feel comfortable.

When an executive messages afterward, the CEO can ask whether the message contains new evidence and route it accordingly. That maintains the process without refusing to hear the concern.

Distinguish fair process from a favorable outcome

Colquitt’s 2001 research supports four dimensions of organizational justice: distributive, procedural, interpersonal, and informational. Applied to executive decisions, these dimensions help separate the result from how it was reached and explained.

An executive may dislike the allocation and still recognize a fair opportunity to provide evidence. Another may receive the preferred budget through a process others reasonably question. Neither outcome alone establishes the quality of the process.

Review the explanation, treatment, decision method, and allocation separately. The research does not guarantee that fair procedures eliminate conflict or make every decision effective.

The CEO also needs to explain which information cannot be shared and why, within legitimate limits. Confidentiality should not become a general excuse for unexplained decisions.

Keep safety and accountability connected to work

The psychological-safety and accountability guide examines how permission to raise concerns can coexist with performance expectations. In the executive group, inspect both sides.

Can an executive disclose a missed milestone promptly? Does the team then establish the consequence, owner, and corrective action? A group that punishes disclosure may learn too late. A group that hears every explanation but never follows up may leave delivery unresolved.

Edmondson’s study does not establish that a meeting rule causes trust or performance gains. Use its construct to examine the shared expectations the team’s conduct creates.

Avoid declaring the team safe because nobody objected to the agreement. Ask whether people can use the challenge route when the issue is consequential and the CEO has expressed a strong preference.

Watch the effects on the wider organization

Employees receive the consequences of executive disagreement through priorities, staffing, and instructions. Check whether the leadership group sends one current account of decisions and handles exceptions consistently.

The employee-motivation guide addresses the broader conditions affecting work. In this context, conflicting executive instructions can make responsibility hard to fulfill even when employees are motivated.

Do not ask staff to choose which executive’s informal direction to obey. Give them an escalation route when instructions conflict. The executive team should resolve the authority issue rather than transferring it downward.

When a decision changes, communicate what changed and which work should stop, continue, or move. Otherwise, the organization may keep executing several versions while the leadership group believes it has aligned.

Evaluate the agreement on the next real disagreement

Choose a near-term review after the team has used the agreement. Examine a decision that received a meaningful challenge, not only an easy consensus.

Check whether the objection was heard, the authority was clear, and delivery followed the recorded version. Inspect any reopening request and whether it identified new information or an unresolved procedural issue.

If the CEO bypassed the route, address that conduct first. A rule applied only to other executives will not provide a dependable operating standard.

Keep the practices that clarify decisions and improve follow-through. Remove rituals that consume time without answering a work question. Executive trust has practical evidence when people can question the proposal, understand the decision, and rely on the commitments that follow.

Sources

Steady at the Top