Week 43 Day 6: Section 4: How to Push Back on Me

If your manual only tells the team how to work with you smoothly, it is a compliance document. If it also tells them how to challenge you effectively, it is a trust document. The pushback section says: 'I am not always right. Here is how to tell me when I am wrong, in a way that I can actually hear.'

Here is how to write Section 4. Part A -- Why I need pushback: explain why disagreement is not just tolerated but required. Example: 'I have blind spots. Everyone does, but mine are predictable: I overvalue novel approaches (Wonder bias -- the new idea seems better just because it is new), I can get so excited about a direction that I miss practical obstacles (Galvanizing bias -- momentum overrides feasibility), and I underweight implementation complexity because Tenacity is not my natural lens. I need the team to push back when these blind spots activate. Your pushback is not a disruption -- it is a correction that makes my decision-making better.' Part B -- How to push back effectively: give the team a framework for disagreement that you can receive without becoming defensive. Example: 'The most effective way to push back on me is with data or a concrete example. "I think this timeline is too aggressive" is less effective than "The last three projects of similar scope took 8 weeks, and we are planning for 4 -- what is different this time?" The data gives me something to engage with rather than something to defend against. If you disagree with a direction I am excited about, lead with alignment before divergence: "I agree that X is the right goal. I am concerned about the approach because Y." When I feel that you are aligned on the goal, I can hear the concern about the approach. When I feel that the goal is being questioned, I become defensive. Strategic timing: if you need to challenge a significant decision, do it in a one-on-one rather than in a group meeting. I handle disagreement better in private because I am not managing my public reaction while simultaneously processing the disagreement.' Part C -- My commitment: state what the team can expect from you when they push back. Example: 'When you push back, I commit to: listening without interrupting, asking clarifying questions before defending my position, acknowledging when you change my mind (explicitly, so you know the pushback worked), and never penalizing you for disagreeing -- in this conversation or in any future evaluation. If you ever feel that I reacted poorly to pushback, tell me. Directly. I cannot fix what I do not see.'

The pushback section implements what Edmondson (2019) calls 'leader inclusiveness' -- the specific leadership behaviors that create psychological safety for voice and dissent. Her research identifies three components: invitation (explicitly asking for input), response (reacting constructively to voice), and follow-through (acting on input when appropriate). The pushback section addresses all three: the 'why I need pushback' paragraph is the invitation, the 'how to push back effectively' paragraph facilitates constructive response, and the 'my commitment' paragraph promises follow-through. Research by Detert and Burris (2007) on 'leadership behavior and employee voice' found that leader openness to voice (explicitly communicating that dissent is welcome) was the strongest predictor of employee voice behavior, stronger than the employee's personality traits, tenure, or job satisfaction. Critically, they found that leader openness needed to be specific (describing how to disagree, not just that disagreement is welcome) to produce actual voice behavior -- generic statements of openness ('my door is always open') were no more effective than saying nothing. The strategic timing advice (one-on-one rather than group) aligns with research by Dutton, Ashford, O'Neill, and Lawrence (2001) on 'issue selling,' which found that attempts to influence leaders were more successful when conducted in private settings where the leader had cognitive space to process the input, rather than in public settings where the leader's attention was divided between the content and their public presentation.