Pushback is information
Some pushback is exactly what a team needs: someone spotting a risk you missed. Some is a pattern, where the same person resists in the same way, whatever the idea. The second kind usually tells you something about how this person likes to receive ideas.
Before you respond, ask one question: does this person push back on the substance, or on the way it arrived?
Three common reasons, and how to adapt
- They need the detail before they can agree
- In meetings they ask for numbers, examples or the plan behind the plan. Send the details in writing before you meet, lead with the facts, and give them time to read.
- They need a hand in shaping it
- They push back on finished proposals but contribute freely to open questions. Bring the problem before the answer, and ask for their version first.
- They need time to think
- They resist in the room and come around a day later. Separate the discussion from the decision: share the idea, then agree when you'll decide.
What to try in your next conversation
- Look back at the last two or three times they pushed back. What did they ask for each time?
- Change one thing: the order (facts first, or the why first), the channel (written or spoken) or the timing.
- Ask directly: “What would make this easier to say yes or no to?”
- Notice what happens, and keep what works.
What usually makes it worse
- Arguing harder with the same approach.
- Labeling the person (“negative”, “not a team player”) instead of describing what happens.
- Saving it all up for a formal review instead of talking about it now.
See the pattern for one specific person
Sixen reads the work conversations you choose and notices how each person communicates: what they ask for, how they decide, and what makes them push back. You get a read on the person, the moments behind it, and two or three ways to approach them next time. You can accept, edit or reject every read, and only you see it.