How Pushback Drives Forward Momentum
Ever been handed a project with an impossible deadline or asked to implement a feature that doesn't feel right?
In moments like these, you face a tough choice: stay silent and hope for the best, or push back to try and stay ahead of disaster. While many developers remain silent, pushing back (when done correctly) safeguards the success of your project, your team, and your reputation.
This week, we explore why pushing back is often the best thing you can do for a project, when it's appropriate to push back (and when it isn't), and how to do it professionally. By the end, you'll see that saying "no" or "not so fast" can be a strategic move that leads to better outcomes for everyone involved.
Why Pushing Back Protects Outcomes
Saying "yes" to every request might feel like being a team player, but it can backfire badly when "yes" isn't realistic. If you silently accept a task with impossible parameters, you risk project failure, burnout, or delivering poor-quality work.
In contrast, a well-placed "push back" can save the project. Here's why speaking up is often the smartest choice:
- It leads to better decisions: When team members voice concerns or suggest alternatives, the whole team can course-correct toward a better solution. Studies show that when employees share novel ideas or flag problems, organizations innovate more and perform better.
- Leaders expect it: Despite the fear of displeasing your boss, capable leaders value honest feedback. They don't want a crew of "yes-people" offering blind agreement. As executive coach Debra Benton notes, good managers know to be wary of sycophants and would rather hear the truth, even if it means an employee respectfully pushing back.
- It protects your reputation: Agreeing to an unrealistic demand sets you up for failure. If you know you can't deliver great work under the given constraints, saying "yes" will only harm your credibility and leave everyone disappointed when the promise falls through.
Remember, the goal of pushback isn't to be oppositional; it's to champion the outcome. When you raise a concern, you're essentially saying: "I care about this project's success. Let's find the best way to achieve it."
That mindset benefits your team, your company, and ultimately your career. As long as you voice it the right way (more on that soon), pushing back is often the most responsible thing you can do.
When to Push Back (and When Not To)
Knowing when to push back is just as important as knowing why. You can't (and shouldn't) contest every decision – that would turn you into a constant naysayer. The key is to pick your battles and focus on the issues that truly impact outcomes or ethics. Here are situations where pushing back is typically justified:
- Unrealistic timelines or scope: If your boss or client asks for a feature overnight that realistically takes a month, it's time to push back. Delivering in that timeframe would likely mean poor quality or burnout – a lose/lose scenario.
- Insufficient resources or support: Similarly, push back if you're asked to achieve something without the necessary tools, team, or budget. For example, implementing a complex new system solo when it requires a team.
- Ethical or quality concerns: If you're ever asked to do something against your moral code or that compromises quality standards (e.g., "just ship it with the known bugs" or "fudge the numbers on the report"), do not hesitate to push back. Anything illegal, immoral, or blatantly undermining the mission is especially fair game to refuse.
On the flip side, when should you let it go? If the issue is minor, subjective, or not truly impactful, it might not be worth pushing back hard. Ask yourself: "Will this matter in the end? Or is it just my personal preference?" Save your political capital for the big stuff. As the saying goes, choose your battles wisely.
If you become the person who pushes back on every little thing, your genuinely significant concerns might lose their punch. So, if the choice of code indentation style annoys you but doesn't harm the project, maybe let that one slide. But if the plan threatens the project's success, that's when your voice is needed.
|
|
Wondering If a Startup Is Right for You?
Big Creek Growth Company shares what it’s really like to work in a startup and what founders are looking for when hiring.
|
|
How to Push Back (The Ladder Approach)
Let's say you've identified a valid reason to push back. How you deliver your message is what makes the difference between a productive discussion and an acrimonious standoff. The goal is to be assertive, not aggressive – to stand up for the outcome while still showing respect and professionalism.
One helpful way to think about this is to approach pushback like climbing a ladder: start at the first rung (the gentlest approach) and move up only as high as needed. You don't jump straight to the top of the ladder if a lower step will do.
Here's a step-by-step ladder for effective pushback:
1. Start with questions and understanding
The lowest rung of pushback is often just clarifying the request. Sometimes what feels unreasonable might be a miscommunication. Begin by asking questions in a curious, non-confrontational tone.
For example: "So that I understand, are we expecting to complete this entire module in two weeks with one developer? Have we considered what that might do to quality?" Phrasing concerns as questions can gently surface the issue without direct criticism.
2. Express your concern with reasons
If hints and questions don't resolve it, step up to clearly state your perspective. Be honest about your concerns, and back them up with facts or outcomes-focused reasoning. The key here is to frame it around the shared goal.
For instance: "I'm concerned that adding those features so close to launch could introduce critical bugs (which would hurt our users’ experience). Based on our testing capacity, I don't think we can guarantee stability on that timeline."
By providing a valid reason (data, past experiences, workload analysis), you make it a discussion about the work, not a personal confrontation.
3. Propose alternatives or solutions
Pushing back shouldn't be just saying "no." If you need to reject or resist a plan, come prepared with an alternative path forward. Maybe you can extend the deadline, or accomplish the same goal with a more straightforward approach.
For example: "Instead of trying to deliver all three features half-done, what if we prioritize the one that matters most to customers and do it right? That way, we hit the deadline with a solid result and schedule the others for the next update."
Offering a solution demonstrates that you're still committed to success. It turns the conversation from confrontation to collaboration.
4. Stand firm (politely) if necessary
In many cases, the discussion will lead to a compromise or adjustment after step 3. But occasionally, you might get pushback to your pushback – perhaps a manager insists on the original plan.
At this top rung of the ladder, you need to assert yourself more firmly, yet still respectfully. Re-emphasize your main point and the stakes involved: "I hear that you want to proceed as planned. I have to be honest that, in my opinion, doing so puts the project at serious risk of failure. I wouldn't be doing my job if I didn’t strongly recommend we reconsider this timeline."
By phrasing it as doing your job to voice the concern, you underline your duty to the project's success. If the issue is ethical, you might even say, "I’m not comfortable proceeding with that approach." At this stage, you're effectively drawing a line. It's uncomfortable, but sometimes necessary to protect the outcome.
Using this ladder approach, you escalate your pushback only as much as needed. Often, a gentle question (step 1) or a well-reasoned concern (step 2) is enough to prompt a change. You'd be surprised how many managers or stakeholders will rethink a request when presented with calm, factual feedback about the risks.
It's when you jump straight to an aggressive "This is impossible, no way!" that conversations tend to go awry. By climbing the pushback ladder rung by rung, you give the other party a chance to join you in problem-solving at the earliest possible stage, rather than feeling attacked.
Ultimately, pushing back is about taking responsibility for outcomes. It's recognizing that saying nothing when you foresee a problem is actually a disservice to yourself, your team, and your company. Yes, it can feel uncomfortable to question a decision or ask for a concession.
It takes courage and confidence. But as we've discussed, the short moment of discomfort is far better than the long regret of a failed project or a compromise to your integrity.
Have you ever had to push back on a boss or client for the sake of a project? How did it go? I'd love to hear about your experiences or any challenges you're facing now.
Reply to this email or leave a comment – I read every response and am here to help.