Let me tell you a little story about assertiveness as a (digital) project manager. Don’t underestimate the power of No. Although this topic is not really related to Scrum, I would like to share a life lesson that I’ve been thinking about a lot lately. In my career as a digital project manager, I have always worked in very dynamic environments with complex activities. Especially in the field of digital product development, in combination with human factors, deadlines, schedules, egos and politics. In these environments, flexibility is often the adage. The pursuit of the ‘yes’ prevails. Everything is possible. And if not, a solution is sought, no matter the cost, often at the expense of quality, sustainability or well-being. Assertiveness is often tamed because of the customer-contractor relationship. An answer other than ‘yes’ is seen as rigid and unserviceable.
And then, just then, nothing is more enlightening – or gives so much catharsis to both the giver and the receiver – than giving a simple answer:
“No.”
Is this my newfound toddlerhood? Is my benevolence and positivity finally broken after all these years of project management? Well, no! I argue that saying ‘no’ can also be of service.
What we tell ourselves when we say yes
‘Yes’ and ‘no’ are not just words. They carry emotional cargo.
‘Yes’ is a confirmation: the door opening, new possibilities, growth, approval. It sounds generous. It sounds like the right thing.
‘No’ lands differently. Rejection. Refusal. Denial. Stagnation. We know this, so we avoid it. We try, in our benevolence, to steer toward ‘yes’ even when the situation doesn’t deserve one.
That’s the trap. Westrum’s organisational typology observes that pathological and bureaucratic cultures systematically suppress inconvenient truths; the “yes that serves no one” is a cultural artefact of those environments, not just an individual people-pleasing habit.
Everything is possible. Until it isn’t.
Project managers operate in a genuine field of tension: budget, planning, staffing, technology, internal politics, and external expectations. In digital product development, feasibility is never abstract; it is a real constraint that interacts with all the others. Add flexible hours, remote work patterns, and part-time schedules, and the planning complexity becomes substantial.
“Nice plan you got there. It would be a shame if something happened to it…”
The project management triangle (scope, resources, time, quality) is always under pressure. Most of the time, small adjustments are possible. Move a working day. Push a deadline a bit. Add a feature to keep a stakeholder happy. Individually, these feel harmless. And individually, they often are.
The problem is that projects are not a series of isolated decisions. They are a cumulative system. The Scrum Guide grounds empirical process control in three pillars: transparency, inspection, and adaptation. A “yes” that obscures a real constraint collapses transparency first, and once that’s gone, inspection and adaptation become guesswork rather than professional judgement. One small accommodation sets the ground for the next. The project manager who always finds a way trains the system to keep asking.
The accumulated wreckage of yes
- What impact does this decision have on the quality of the process or product?
- Is that impact acceptable, and do the people involved actually know about it?
- Can the impact be addressed with a different intervention, and what does that intervention cost in turn?
If the honest answers lead you to “no”, that answer is valid. More than valid: it is useful.
There is another thing the perpetual “yes” costs, beyond project integrity: other people’s autonomy. Daniel Pink (Drive, 2009) identifies autonomy as a primary driver of intrinsic motivation. When a project manager removes every obstacle, they erode the team’s autonomy and, with it, the engagement they were trying to sustain. If you solve everything, people stop solving things themselves. You do not become indispensable. You become a bottleneck wearing a service hat.
Saying “yes” a lot also builds an expectation that has nothing to do with reality. You are not a miracle worker. Not everything is possible. Confessing that is not rigidity; it is honesty about constraints that are already there, whether you name them or not.
No is a form of care
How much do you value your own standards if “anything goes”? This is not a rhetorical question. It deserves a considered answer.
‘No’ is usually a deliberate response, not delivered from frustration or defeatism, but from a considered position. A ‘no’ can come from a deeply helpful place. It shows that you stand for the process and the people in it, for the thing you were actually hired to protect.
You will be surprised how well people accept ‘no’. Not because they don’t want what they asked for, but because they trust that the person saying no has a reason. And because a considered refusal, unlike a hollow yes, is something they can actually work with.
The useful form of ‘no’ is never just a full stop. It is a comma. “No, but…” or “No, because…” There is a real difference between slamming a door and leaving it ajar. The first is obstruction. The second is negotiation from an honest position.
Miracle worker. Problem fixer. The person who always finds a way. These labels that project managers accumulate are not always compliments. Sometimes they are the residue of a professional who never learned to say no with confidence. I’ve worn those labels. It took me longer than I’d like to admit to understand the cost.
In healthy working relationships, assertiveness reduces stress. It sets a clear signal about what is real, what is possible, and what would actually serve the work. A ‘yes’ that doesn’t hold up is not service. It is a deferred problem wearing a smile.
No is a valid answer.