Week 45 Day 2: How to Tell Your Boss They Are Wrong

Telling the boss they are wrong is one of the highest-risk social interactions in any organization. The team member is betting their reputation, their relationship with you, and potentially their career on the belief that you will respond well. Most people are not willing to make that bet without evidence that it is safe. Your job is to provide the evidence.

Here is the framework you should give your team for telling you that you are wrong. Framing principle one -- separate the person from the position. 'I disagree with this approach' is easier for both parties than 'You are wrong.' The first challenges the idea. The second challenges the person. When teaching your team to push back, encourage them to challenge decisions and approaches rather than attributing error to you personally. This is not political correctness -- it is communication efficiency. You are more likely to hear and process a challenge to your idea than a challenge to your judgment. Framing principle two -- lead with data or example, not opinion. 'I think we should reconsider the timeline' is an opinion. 'The last three projects with similar scope took 8-10 weeks, and we are planning 5 -- what is different this time?' is a data-grounded question. The data-grounded question is harder to dismiss because it requires engagement with the specifics rather than a simple 'I disagree.' Teach your team to bring evidence when they push back. Not because their opinion is not valuable, but because evidence-backed pushback is more effective at changing your mind. Framing principle three -- align on the goal before challenging the path. 'I know we both want to ship this feature by Q2 (shared goal). I am concerned that the current approach introduces a dependency on Team X that could delay us by 3 weeks (specific concern). Here is an alternative that achieves the same outcome without the dependency (alternative proposal).' This structure works because it signals alignment (we want the same thing), identifies a specific risk (not a general complaint), and offers a constructive alternative (not just a problem). Framing principle four -- choose the right moment. Teach the team that timing matters. Challenging a decision in the middle of a stakeholder presentation is different from challenging it in a one-on-one before the presentation. The content of the challenge may be identical; the context determines whether it is received as helpful (pre-presentation) or undermining (during presentation). Share these four principles with your team. Put them in your Leadership Operating Manual under 'How to Push Back on Me.' Give the team explicit language they can use. The more specific you are about what effective pushback looks like, the more likely you are to receive it.

The social risk of upward voice (telling the boss they are wrong) is documented by Milliken, Morrison, and Hewlin (2003) in their research on 'an exploratory study of employee silence,' which found that 85% of employees could identify at least one issue they felt unable to raise with their manager, and the primary reason cited was fear of being labeled negatively (troublemaker, not a team player, disloyal). The separation of person from position (framing principle one) implements what Fisher and Ury (1981) call 'positional bargaining' versus 'interest-based negotiation' in 'Getting to Yes' -- their research demonstrates that negotiations focused on positions (you are wrong, I am right) produce adversarial dynamics, while negotiations focused on interests (we both want the project to succeed; I see a risk in this approach) produce collaborative problem-solving. The data-grounded pushback recommendation (framing principle two) is supported by research by Dutton, Ashford, O'Neill, and Lawrence (2001) on 'moves that matter: issue selling and organizational change,' which found that upward influence attempts were 3.5 times more likely to succeed when they included quantitative evidence or concrete examples than when they relied on opinion or intuition alone. The timing recommendation (framing principle four) is documented by Dutton, Ashford, O'Neill, and Lawrence as the 'timing and packaging' dimension of issue selling -- their research found that the same message delivered in a private setting before a decision was finalized was perceived as helpful contribution, while the same message delivered publicly after the decision was announced was perceived as undermining, regardless of the message's accuracy or value.