Project managers are no strangers to constant demands—new features, scope creep, last-minute requests. It can feel like an endless juggling act. But real leadership isn’t about saying “yes” to everything; it’s about knowing when to say “no” and doing it well.
A colleague once told me about a project that nearly collapsed because every stakeholder request got the green light. The team was stretched thin, deadlines slipped, and chaos took over. Only when they hit pause, set clear priorities, and refocused on what truly mattered did they turn things around. The project wasn’t just saved—it thrived.
Saying “no” isn’t about shutting people down; it’s about protecting the work that really moves the needle. It keeps resources aligned, timelines realistic, and teams from burning out. The key? Setting clear criteria. Does this request drive real value? Does it fit the objectives and timeline? If not, it’s okay to push back—gently but firmly.
Next time a request comes in, take a breath. Ask yourself: Does this serve the bigger picture? If not, respond with a thoughtful “not now” and explain why. When teams master the art of selective “no’s,” they create space for the right “yes’s”—the ones that lead to real success.
What’s one thing you need to say “no” to today?
Dr. Te Wu ( Te Wu ) is the CEO and CPO (Chief Project Officer) with PMO Advisory, a Project Management Institute’s (PMI) Authorized Training Partner. The company specializes in project, program, and portfolio management and strategic business execution through its training, conferences, and consulting services. Te is also a Professor at Montclair State University.
