Before We Agree Have We Heard the Strongest Objection
When a leader supports an idea, it can become difficult to tell whether the team agrees with the proposal or is responding to the leader’s enthusiasm.
People may ask questions about the budget or suggest a better launch date. The meeting feels productive. Yet nobody has questioned whether the company should proceed.
I think this is worth paying attention to. Improving a proposal and challenging the decision behind it are different conversations. For an acquisition, a new market or a major technology investment, we need both.
What happens when the boss disagrees
Jeff Bezos described a useful example in his 2016 shareholder letter. His team wanted to approve an Amazon Studios project. He had reservations about its appeal, production complexity and business terms. The team saw it differently.
He expressed his concerns, then committed to their decision. He pointed out that requiring the team to convince him would have made the process slower.[1]
The letter does not tell us whether that particular project succeeded. What it does show is a leader allowing a decision to proceed despite his own doubts.
That matters because an invitation to disagree has limited value if the leader’s view always prevails. People need to see that another judgment can influence the outcome.
A serious objection needs more than a designated role
Assigning someone to play devil’s advocate can be a starting point. But someone who genuinely believes the plan is wrong brings something different to the discussion.
In a 2001 experiment, Charlan Nemeth and colleagues found that authentic dissent prompted more original thinking and consideration of the opposing position than an assigned devil’s advocate.[2] This was an experimental finding, rather than a study of investment returns. Still, it gives us a reason to seek out a real alternative view instead of treating disagreement as a meeting formality.
For a significant proposal, I would want the discussion to answer one question:
What is the strongest reason a capable, well-informed person would advise us not to proceed?
“Execution will be challenging” is too broad to help. “This acquisition depends on retaining three people who have not agreed to stay” gives the board something concrete to examine.
The team can then establish whether that concern has been resolved, whether it changes the terms of the decision, or whether the company is willing to accept the risk.
A check before approval
Before the next major decision, ask someone who did not prepare the proposal to write a short case against proceeding. Give them access to the evidence and time to develop their view. Ask the proposal’s sponsor to respond to it.
At the end, record what happened to the objection. Was it answered with evidence? Did it change the plan? Or are we accepting it as an unresolved risk?
This is my suggested practice, not a research-tested formula. Its value is that it makes the treatment of disagreement visible. It also gives the board a record to revisit if the risk materialises.
A peer outside the organisation can help with this examination, particularly when the proposal is closely associated with the CEO. They can question its assumptions without being responsible for its approval. They will still need enough context to offer more than a general opinion.
The leader remains accountable for the final call. Once it is made, the team needs to execute, while retaining the ability to respond to new evidence.
Before approving a proposal, I would feel more confident knowing how its strongest objection was handled. A room full of agreement cannot tell me that on its own.
Sources
[1] Jeff Bezos, 2016 Letter to Shareholders, Amazon. See the discussion of “disagree and commit” and the Amazon Studios example.
[2] Charlan J. Nemeth and colleagues, Improving Decision Making by Means of Dissent, Journal of Applied Social Psychology, 31, 48–58, 2001.
Written by Sonali Behere, Editorial Team | CEO Cohort India
About the Author
With 21+ years of experience in IT delivery, she brings extensive expertise in SAP projects, delivery governance, and leading multi-geography teams. Her leadership approach combines structured execution with collaboration, accountability, and a strong focus on sustainable outcomes. She is passionate about continuous learning, meaningful contribution, and growing as a thoughtful leader.
