How to Push Back on an Unrealistic Deadline Without Damaging the Relationship
Every engineer eventually sits across from a stakeholder who says "we need this in three weeks" about something that genuinely needs six. The instinct is either to say yes and quietly hope for the best, or to say "that's not realistic" and watch the conversation get defensive fast. Neither approach actually works well, and the difference between engineers who get their pushback taken seriously…
Engineers often find themselves discussing unrealistic deadlines with stakeholders. The instinct can be to either agree and hope for the best, or to firmly reject the timeline and risk a defensive response. Neither approach is effective, and the key difference lies in how the pushback is framed. Stating "that's not realistic" outright is subjective and can be seen as dismissing the stakeholder's urgency.
To push back successfully, engineers should explain the reasoning behind their estimate, just as they would expect a vendor to do when quoting a price.
Rather than bluntly rejecting the deadline, break down what the proposed three-week timeline would entail. For example, estimate the time needed for tasks like database migration, API layer development, frontend integration, testing, and handling third-party payment integration. This provides the stakeholder with concrete information to evaluate and encourages a discussion about trade-offs instead of putting them on the defensive.
When offering alternatives, provide options that still meet key business objectives. For instance, consider reducing the scope to ship the core functionality within the original three-week timeline, while deferring less critical features to a later phase. Alternatively, suggest bringing in additional resources to parallelize tasks, which can help meet the deadline without sacrificing quality. By presenting these options, engineers give stakeholders real choices to make, rather than presenting an impassable wall.
It's important to separate the estimate from the person providing it. The estimate should describe the complexities of the system and how long similar tasks have historically taken, rather than reflecting personal availability or willingness to work longer hours. Framing the estimate this way shifts the conversation from a negotiation over effort to a collaborative analysis of the underlying reality.
In some cases, an aggressive deadline may be arbitrary or tied to an external factor that wasn't initially communicated. Asking the stakeholder to clarify what is driving the specific timeline can uncover crucial information that changes the conversation entirely. If the real constraint is tied to a specific event, such as a demo for a meeting, the problem becomes much more manageable.
In cases where the full scope cannot be delivered within the requested timeframe without compromising quality, the goal should not be to win the negotiation. Instead, the objective is to ensure the decision-maker has full information about the trade-offs involved. Clearly documenting the chosen compromise, such as shipping with limited testing to meet the deadline and acknowledging the associated risks, protects both the project and the engineer who raised the concern.
Ultimately, pushing back on unrealistic deadlines effectively is about replacing a verdict with a breakdown that stakeholders can evaluate, and replacing an objection with options they can choose between. Engineers who adopt this approach consistently tend to have their concerns taken more seriously than those who rely solely on confidence or seniority. This method treats the estimate as a shared problem to solve, fostering collaboration and leading to better outcomes for everyone involved.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
