by In IT project management, authority bias can quietly undermine smart decisions and well-structured plans. Even the most experienced project managers are not immune to this powerful cognitive trap.
Authority bias happens when we give disproportionate weight to the opinions or instructions of people in positions of power, regardless of whether their advice is grounded in evidence or not.
Unchecked, authority bias can undermine even the best-planned initiatives. Let’s examine what it is, how it manifests in IT projects, and most importantly, how to prevent it.
What Is Authority Bias?
Authority bias is our natural tendency to trust and follow the opinions of authority figures more readily than we trust our judgment or the available data.
It stems from a hardwired human instinct: throughout history, survival often depended on obeying leaders who were presumed to have superior knowledge.
In modern organizations, however, this instinct can backfire. In IT projects, especially where complexity, scale, and velocity matter, blindly following “the highest-paid person’s opinion” (often called the HiPPO effect) can lead to costly mistakes.
A study from the Rotterdam School of Management even found that junior-led teams often outperform senior-led ones precisely because they foster more openness and dissent.
That said, not all authority-driven decisions are problematic. Senior leaders often bring critical context, visibility into company-wide goals, and valuable institutional memory. The key is balance: momentous project decisions emerge when the strategic direction and technical insight are allowed to challenge and refine each other.
How Authority Bias Derails IT Projects
1. Critical Thinking Gets Suppressed
When authority bias influences project managers, they may hesitate to challenge senior leaders’ assumptions, even if evidence suggests otherwise.
Example:
An executive demands the project “go live” two months early to meet a conference deadline. Despite glaring risks in security and scalability, the PM hesitates to challenge the timeline. The project launches on time but collapses under real-world usage.
Case in Point: Boeing 737 Max
In the Boeing 737 Max project, multiple engineers expressed concerns about the MCAS flight control system. However, intense pressure from senior leadership to meet aggressive timelines and outpace competitors led to their concerns being downplayed or ignored.
Two tragic crashes and 346 lives lost later, investigations revealed how authority pressure and a culture of silence overruled engineering feedback, with devastating consequences.
It is a sobering reminder that when we sacrifice critical thinking in deference to rank, even the most advanced projects can fail catastrophically.
2. Risks Are Overlooked
Project risks that conflict with an authority’s narrative often get downplayed or ignored. It can cause slight issues to snowball into major project derailments.
Example:
An architect points out that a critical third-party integration has stability issues. But because the CIO endorsed the vendor, concerns are brushed aside until a system outage embarrasses the company.
3. Priorities Get Distorted
Instead of focusing on what the project truly needs, teams may prioritize pet features or flashy deliverables favored by influential stakeholders.
Example:
A project pivots to building a “cool AI chatbot” after a senior VP casually mentions it in a meeting, despite the chatbot having no clear business case or user demand.
It isn’t just a hypothetical. Executive “pet projects” often deviate from business needs and quietly drive scope creep unless actively managed.
4. Team Morale Erodes
Over time, a culture that discourages questioning authority can erode psychological safety. Team members become passive, creativity withers, and the project’s ability to adapt declines.
Example:
Developers stop suggesting better technical solutions because they feel decisions are already made “at the top,” whether or not they make sense.
It directly ties into the concept of psychological safety, which is essential for learning and innovation in teams. When people fear speaking up, risk awareness and adaptive thinking collapse.
How IT Project Managers Can Stop Authority Bias
The good news? You do not have to accept authority bias as inevitable.
Here are practical strategies to minimize its impact:
1. Champion Data Over Titles
When presenting options or risks, anchor the discussion in evidence, metrics, prototypes, and risk assessments, and not in personalities or seniority.
Tip: Utilize dashboards, demonstrations, and mock-ups to help stakeholders visualize the data and present the real situation.
2. Normalize Respectful Dissent
Encourage your team and yourself to question ideas, not people. Make it clear that challenging assumptions, even those from executives, isn’t disrespectful. It is a responsibility.
Create premortem rituals, where the team imagines reasons the project might fail. These allow for risks to be voiced early, without blame.
⚠️ Note on Organizational Culture
Let’s be real, not every workplace is psychologically safe. In rigid or politically charged environments, openly challenging authority can feel risky. If that’s your context, dissent doesn’t have to be loud to be effective.
Build alliances quietly. Ask clarifying questions that highlight trade-offs. Use documentation (e.g., risk logs, decision logs) to surface concerns without direct confrontation.
Influence isn’t just about pushing back; it’s about creating space where others can think critically, too.
3. Ask Clarifying (Not Confrontational) Questions
Instead of flatly opposing a senior leader, use thoughtful questions to surface gaps and encourage reflection.
Examples:
“What trade-offs are we willing to accept if we choose this path?”
“How might this decision impact our deployment timelines or security posture?”
4. Document Risks Transparently
Use formal tools like risk registers or RAID logs to objectively capture risks, even when authority figures drive risky decisions. Make these documents part of regular project reviews.
5. Use DACI and RACI to Reduce Bias
Frameworks like DACI (Driver, Approver, Contributor, Informed) and RACI (Responsible, Accountable, Consulted, Informed) help distribute decision-making across well-defined roles, reducing the influence of hierarchy alone.
These are widely used tools in project management, especially in complex environments where clarity trumps charisma.
When Authority Adds Value
Not all authority-driven decisions are flawed. Executives and senior stakeholders often have access to macro-level insights, market positioning, strategic dependencies, and regulatory risks that front-line teams might not see.
The goal isn’t to eliminate authority in decision-making. It’s to make sure that rank doesn’t override reason, and that project health is never sacrificed at the altar of hierarchy.
Project Managers Are Evolving, So Should Our Mindset
Project managers aren’t just taskmasters anymore. They’re becoming strategic partners, shaping how organizations deliver value, influence change, and navigate uncertainty.
Our ability to think critically, even when faced with authority, is not just helpful; it is essential.
Conclusion: Authority Bias Is Manageable If You See It
Authority bias isn’t just “someone else’s problem.” It can creep into your own thinking, too, especially under time pressure, political heat, or admiration for a leader.
The first step is awareness. The next is courage: to build cultures, processes, and habits that prioritize facts, collaboration, and shared ownership of project success.
In a world where technology and failure move fast, the best project managers aren’t just order-takers. They’re thoughtful challengers, bridge-builders, and stewards of reason.
The best ideas should always win in every IT project. Not the loudest voices.
If you’re ready to lead with insight, and not just with instinct, follow @rationalpm on X.
Get weekly prompts, frameworks, and thought-provoking takes to help you grow into the kind of project manager who makes clarity louder than rank.
You might also like…