Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
In today’s fast-paced, high-stakes business world, the drive to deliver more, faster, and cheaper is relentless. Product Owners and Project Managers stand at the crossroads of customer expectations, executive ambition, and the realities of team capacity. Too often, they are pressured to accept impossible deadlines and unrealistic scope—leading to stress, burnout, technical debt, and ultimately, failed projects. Yet, saying "no" is not just a professional necessity; it’s an ethical responsibility. This post explores why and how Product Owners and Project Managers must be empowered to push back, and how organizations benefit when boundaries are respected.
-Have you ever had to say "no" to an unrealistic deadline or scope?
-How did you approach it, and what was the outcome?
-What advice would you offer to others facing similar pressures?
Blog post
The Responsibility to Say "No": Empowering Product Owners and Project Managers to Ethically Push Back Against Impossible Deadlines
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
An important perspective.
The responsibility is not merely to say "no". It is to prevent the organization from making commitments that reality cannot support.
In many cases, unrealistic deadlines are not the result of a single decision. They are the consequence of incentives, governance structures and decision-making processes that reward optimism more than realism.
Ethical pushback therefore serves a broader purpose. It protects not only team well-being, but also decision quality, stakeholder trust and the integrity of commitments.
The most valuable leaders are not those who promise the impossible. They are those who make trade-offs visible before the organization commits itself to outcomes it cannot sustainably deliver. Saving Changes...
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
There have been situations where the requested scope, timeline, and available capacity simply didn't align. Instead of simply accepting the commitment, we discussed what could realistically be delivered within the timeframe and what would need to change. Sometimes that meant reducing scope, sometimes extending the timeline.
Agreeing to an unrealistic commitment rarely changes the reality of the work. The constraints are still there Saving Changes...
Yes—and saying “no” is often part of responsible project leadership. Saying “no” doesn’t mean rejecting the request outright. It means challenging it constructively and redirecting toward a realistic solution. Saving Changes...
Senior IS Project Manager| Baycare Health SystemsClearwater, Fl, United States
Yes I have said 'No' on many occasions. For example we had an IS Project that was Going Live on Sunday morning during the IS Maintenance window, and I received a request to change the scope while I was at home Friday evening! This was not a forever no, but it was a not for implementation during this deployment window.
There are other occasions when NO is the correct answer because the requirement does not align with your strategy. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Luis Branco My experience with software developers, especially in Agile, is that they are very optimistic. There are many reasons to say NO (lack of capacity, skills etc) but the first step is to understand the problem. Agile tried to put guardrails on optimistic estimates by inventing the Story Points (dependent on many factors like size, complexity, priority, dependencies) but it is a failure. Very few people know that SP originated as ideal days, when everything is perfect, unlike real life. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Lissette Indhira Pimentel Sosa "There have been situations where the requested scope, timeline, and available capacity simply didn't align", that's always the case outside the training room. In traditional project management we say to pick 2 out of scope, time and money. Agile tried to lock the time and money but it is not simple. That's where project management skills and experience add value to an organisation; not colourful weekly reports. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Sreesudha Ayyalasomayajula thank you. That's my point: saying no is not a critical attitude or trying to be difficult. From a responsible professional it is Honesty. Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Michael King good point. No doesn't mean an absolute decision. It can be revised when information changes. That's what Agile supposed to be: adaptation to changes Saving Changes...
Yes. I've found it's usually less about saying "no" outright and more about reframing the conversation around trade-offs. When faced with an unrealistic deadline or scope, I work with stakeholders to clarify priorities, assess risks, and present options—such as reducing scope, adding resources, phasing delivery, or extending timelines. My goal is to align expectations with what can realistically be delivered while still achieving the most important business outcomes. This approach helps maintain trust and keeps decision-making focused on facts rather than assumptions. Saving Changes...
Ming YeungAdjunct Professor| Various academic institutesToronto, Ontario, Canada
Dan, I concur that saying no in a high‑pressure environment is never easy, but it has become one of the most important skills I have had to develop as a project professional. I have absolutely faced situations where deadlines or scope were misaligned with reality whether due to optimism, external pressure, or simple misunderstanding. Early in my career, I tried to absorb the impact by pushing myself and the team harder, but the result was predictable: stress, rework, and outcomes that satisfied no one. The turning point came when I realized that pushing back isn’t an act of defiance; it’s an act of stewardship. When I’ve had to say “no,” I’ve approached it by reframing the conversation around trade‑offs. Instead of a flat refusal, I present clear options: “We can hit this date if we reduce scope by X,” or “If the scope must remain, here’s the realistic timeline based on current capacity.” Grounding the discussion in data, such as velocity, dependencies, and / or risk, helps shift the dialogue from emotion to evidence. In most cases, stakeholders appreciate the transparency, and the outcome is a more sustainable plan that protects both delivery quality and team well‑being. My advice to others is simple: don’t wait until a crisis to set boundaries. Build trust early by communicating consistently, sharing constraints openly, and demonstrating that your goal is shared success, not obstruction. A well‑reasoned “no” is often the most responsible “yes” you can give. The organization benefits when we protect the integrity of the work and the people doing it. Saving Changes...
Community Champion
