We have all likely heard the advice that good leaders need to be open to other perspectives. That’s how we address our blind spots for the benefit of the business. The problem is that this well-meaning counsel is the equivalent of saying, “Just relax.” It describes the ideal end state, not how you get there.
The main reason leaders resist disagreement, I believe, is that disagreement registers as a threat. Psychological research, including studies on cognitive reactivity, shows people often conflate criticism of ideas with criticism of self. In other words, if you challenge my idea, you’re implicitly questioning my competence, my judgment, and my place in the room. This neurological threat response—linked to the amygdala and social pain pathways—triggers a defensive reflex. As a result, when control feels like it’s slipping, the instinct is to grip harder by shutting down debate and demanding agreement. Often, none of this is explicit; most leaders would say they welcome pushback. But the dynamic is the same, and we must be aware of the subtle ways we can filter feedback to confirm what we’ve already decided.
Why “Be More Confident” Isn’t the Answer
The answer isn’t simply “be more confident.” If your confidence isn’t anchored in anything specific—just a general sense that you’re competent—it has no real foundation and can easily shatter under critique.
What actually works is domain-specific confidence. Psychologist Albert Bandura’s seminal research on self-efficacy found that capability beliefs tied to specific domains predict performance and resilience far better than generalized self-assurance. It means knowing what you are genuinely good at, and being equally honest about what you are not. For leaders, this reframes the whole question of control. If my authority rests on being right about everything, every disagreement is a threat. But if my authority is domain-specific, disagreement outside that area is just someone else’s lane. I can let it go because my core identity as a leader is secure.
This is different from humility as a mere personality trait. Research on intellectual humility, such as work by psychologists like Elizabeth Krumrei-Mancuso, shows it’s less about being modest and more about accurate self-assessment—being willing to revise your views when evidence warrants. It is a disciplined skill, not a passive disposition.
The Microsoft Transformation: A Case Study in Secure Authority
Satya Nadella’s reign at Microsoft is a classic example of this principle in action. When he took over in 2014, the company was known for a famously combative “know-it-all” culture where internal competition and defending turf were common, and admitting uncertainty was seen as a weakness. This culture had contributed to missed opportunities in mobile and cloud.
Nadella began a deliberate shift to a “learn-it-all” culture. What made this possible was his public and clear articulation that his core expertise and passion lay in product vision and long-term platform strategy; for everything else—from specific engineering practices to go-to-market tactics in new regions—he was willing to defer to domain experts. This wasn’t false modesty; it was a strategic delegation of confidence. By the end of his first five years, Microsoft’s market cap had roughly tripled, soaring from around $300 billion to over $900 billion, largely by embracing cloud computing (Azure) and open-source technologies—areas where leadership had previously been resistant but engineers had been advocating. The shift allowed critical feedback from teams to surface, be heard, and acted upon.
Building Systems for Constructive Disagreement
While self-awareness is the personal foundation, allowing for productive disagreement also requires structural support. The goal is to create processes that make dissent routine, depersonalized, and focused on the idea, not the individual.
One powerful method is what researchers call “constructive controversy”. The process involves arguing a position sincerely, then reversing and arguing the other side with equal conviction before reaching a final conclusion. Decades of study on this technique, including meta-analyses in educational and organizational psychology, show that while participants initially defend their corner aggressively, the role reversal often leads to a breakthrough moment. People frequently stop mid-argument and acknowledge, “I didn’t realize how strong the other side’s case actually is.” The purpose is to separate people’s identities from the ideas they are debating.
Another straightforward tactic is formally assigning someone the role of “devil’s advocate” or “flaw-finder” in a proposal review. If someone is just doing their job, the act of critique can hardly be taken personally. This institutionalizes skepticism and ensures vulnerabilities are surfaced without social penalty.
None of these processes work, however, without a foundation of psychological safety. This term, popularized by Harvard Business School professor Amy Edmondson, defines team environments where people can speak up with ideas, questions, concerns, or mistakes without fear of humiliation or punishment. The company that is free to disagree internally is often not just the safest, but also the most innovative and resilient, as it can surface and correct errors before they escalate.
The High Cost of Suppressing Dissent: Boeing’s 737 MAX Crisis
The catastrophic cost of getting this wrong is well documented. Boeing’s safety failures with the 737 MAX have been extensively linked in official reports—including the U.S. House Transportation Committee’s 2020 report and NTSB investigations—to a culture where warnings didn’t travel upward because technical disagreement was treated as disloyalty or a lack of team spirit.
Consequently, while serious safety concerns about the Maneuvering Characteristics Augmentation System (MCAS) had surfaced repeatedly among engineers after the first two fatal crashes in 2018 and 2019, these concerns were reportedly minimized or siloed. It took the Alaska Airlines 737 MAX 9 emergency in January 2024—a mid-flight fuselage panel blowout—to force immediate, FAA-mandated inspections and reignite a congressional expert panel to review Boeing’s safety and cultural reforms. This extreme case illustrates a universal truth: the leader who needs to be right about everything ends up controlling nothing, because the critical information that would help them adapt either never arrives or is systematically ignored.
Conclusion: The Leader Who Actually Stays in Control
True leadership control isn’t about monopolizing decisions; it’s about curating an environment where the best information wins. This requires two intertwined commitments: first, the personal work of defining your domain of expertise with honesty, so that disagreement outside it doesn’t feel like a mortal threat.
