For most of my early career I said yes to nearly every deadline I was handed, because I thought saying no would make me look like I could not handle the pressure that everyone else seemed to be handling fine. Twenty years and four different manufacturers later, I know that almost everyone around me was quietly cutting corners to hit those same deadlines, and the ones who said no early and clearly were, more often than not, the ones whose designs did not come back with field failures six months later. Learning to push back is not a soft skill separate from engineering competence. It is part of the job, because a schedule that does not leave room for proper analysis or review is a schedule that has already decided which corners will get cut, whether anyone admits it out loud or not.
- The Project Where Saying Yes Cost More Than Saying No Would Have
- Learning to Say No With Numbers, Not Just Discomfort
- Distinguishing a Tight Deadline From an Unreasonable One
- The Particular Difficulty of Saying No as a Contractor
- Offering an Alternative Instead of Just an Objection
- Putting Pushback in Writing, Even When the Conversation Goes Well
- Building the Habit So It Gets Easier, Not Harder, Over Time
The Project Where Saying Yes Cost More Than Saying No Would Have
Early in my career, I was asked to finalize a bracket design for a vibration-loaded application in about a third of the time I would normally want for that kind of analysis. I said yes, because the project manager framed it as urgent and I did not yet have the confidence to push back on someone more senior than me. I skipped a proper fatigue check and relied on a rough hand calculation instead, telling myself it was probably fine.
It was not fine. The bracket cracked at a weld toe during field testing about four months later, triggering a redesign, a re-test cycle, and a schedule delay that ended up costing far more time than the proper analysis would have taken in the first place. Nobody blamed me directly, because the pressure to compress the schedule had come from several directions, but I knew exactly what had happened, and it taught me a lesson I have never forgotten: agreeing to an unreasonable deadline does not make the underlying work take less time. It just moves the time cost to later, usually with a failure attached to it, and usually at a moment that is more expensive and more visible than the original deadline ever was.
Learning to Say No With Numbers, Not Just Discomfort
My first attempts at pushing back on deadlines were emotional rather than concrete, along the lines of telling a manager that a timeline felt too tight. That kind of pushback rarely worked, because it was easy for a manager under their own schedule pressure to dismiss a feeling, especially from a contractor who could be perceived as replaceable.
What actually changed the outcome of these conversations was replacing feelings with specific numbers. Instead of saying a deadline felt unreasonable, I started saying something like: this analysis normally takes four working days based on the last three similar projects I have done, and I have two days available, so here is exactly what will be skipped if we hold the current date. On a project involving a pressure vessel bracket, laying out precisely which checks would be omitted — not a vague “less thorough,” but a named list of the specific verification steps that would not happen — got the deadline moved by three days in a conversation that had gone nowhere the day before when I had only expressed general concern. Specificity turns a pushback from an opinion into a decision the other person has to actually own.
Distinguishing a Tight Deadline From an Unreasonable One
Not every tight deadline deserves pushback, and learning to tell the difference took me longer than I would like to admit. A tight deadline that simply requires focus, cutting out unrelated distractions, or working through a genuinely difficult but achievable schedule is just part of engineering work, and treating every tight deadline as a crisis erodes your credibility for the times pushback actually matters.
The distinction I now use is whether hitting the deadline requires skipping a verification step that exists specifically to catch a known failure mode, versus requiring me to simply work more efficiently or postpone lower-priority tasks. On one project, a deadline felt uncomfortably tight but did not actually require skipping any analysis — it just required me to defer some documentation cleanup and focus purely on the calculation itself for a few days. I did not push back on that one, because the discomfort was about pace, not about safety margin. On another project around the same time, a similarly tight deadline did require skipping an interference check on a moving assembly, and that one I pushed back on hard, because the two situations were not actually the same kind of pressure even though they felt superficially similar from the outside.
The Particular Difficulty of Saying No as a Contractor
Pushing back on a deadline carries a different weight when you are a contract engineer rather than a permanent employee, because there is always an unspoken awareness that a contractor who causes friction can simply not have their contract renewed. I felt this acutely in my first several years of contract work, and it made me swallow objections I probably should have raised.
What shifted my thinking was realizing that the reputation of a contract engineer is built over years and across multiple client relationships, not just within a single contract, and a contractor known for rubber-stamping unreasonable deadlines eventually becomes known for producing designs that fail in the field, which is a far worse reputation to carry than being known as someone who occasionally slows a schedule down for a good reason. I once ran into a case where I pushed back firmly on a deadline for a load-bearing weldment, was told plainly that the client was frustrated with the delay, and a year later was specifically requested for a new project by a different manager at the same company who had heard about that exact episode and wanted an engineer who would flag problems rather than hide them. The short-term friction was real, but it was not the whole story.
Offering an Alternative Instead of Just an Objection
A flat no, without anything else attached to it, tends to get overridden, because it leaves the person setting the deadline with nothing to work with except pressure back onto you. What has worked far better over the years is pairing any pushback with a concrete alternative that gives the other person a real choice rather than a wall.
On a project with an unreasonable analysis timeline, instead of simply saying the deadline could not be met, I offered two options: extend the deadline by the time actually needed for a full check, or accept a reduced scope where I would verify only the single highest-risk failure mode within the original timeline and flag the rest as unverified in writing. The project manager chose the reduced scope, which was a reasonable trade-off given the actual business pressure, but critically, it was a decision made with full visibility into what was and was not being checked, rather than a decision nobody realized they were making. Giving people a real choice, instead of just resistance, is what turns pushback from a confrontation into a negotiation.
Putting Pushback in Writing, Even When the Conversation Goes Well
Even when a deadline conversation ends amicably, I have learned to follow it up with a short written summary of what was discussed and decided, because verbal agreements about schedule trade-offs have a way of being forgotten or reinterpreted once the pressure of the moment has passed. Early in my career I skipped this step, assuming a good conversation was enough, and more than once found myself blamed later for a scope reduction that had actually been agreed to jointly.
Now, after any conversation where a deadline gets adjusted or a scope gets reduced under time pressure, I send a short email or message summarizing exactly what was agreed, including specifically what analysis or verification is being deferred or skipped and who made that call. This is not about covering myself defensively, though it does serve that purpose. It is more that a written record keeps everyone honest about what was actually decided, and it has more than once prompted a manager to reconsider a scope cut once they saw it stated plainly in writing rather than as a passing comment in a hallway conversation.
Building the Habit So It Gets Easier, Not Harder, Over Time
The uncomfortable truth about pushing back on deadlines is that it does not get easier just by doing it once. Each new project, each new manager, and each new client relationship resets some of that discomfort, and I still feel a flicker of the same anxiety I felt twenty years ago before a difficult schedule conversation, even though I now know from experience how these conversations tend to go.
What has changed is not the discomfort itself but my trust in the process. I know now, from a long enough track record, that a specific, numbers-based pushback paired with a real alternative gets taken seriously far more often than it gets dismissed, and that the times it does get dismissed are usually the times where the eventual failure proves the pushback was warranted in the first place. Saying no as a design engineer is not a personality trait some people have and others do not. It is a practiced skill built the same way any other engineering competency is built, through repetition, through paying attention to what worked and what did not, and through accepting that the discomfort of pushing back is almost always smaller than the cost of a design that shipped without the analysis it actually needed.



コメント