A Project Manager Who Agrees to Every Request May Cause More Harm Than One Who Refuses

By: Ahmed Ali El-Dabaa

The most dangerous project manager for a team is not necessarily the autocratic or overly resistant one. Sometimes it is that polite manager who cannot say "no" to the client.

Imagine a project to develop a system serving thousands of users. Both parties agreed on a clear scope, a specific execution timeframe, and a budget commensurate with the required deliverables.

After work begins, the client requests adding a few features. The project manager agrees to maintain the good relationship. Then additional requests emerge from a different department, so he agrees again, promising everyone that the timeline will not be affected.

At first, this seems like evidence of cooperation, flexibility, and customer care.

However, after a while, the team begins working longer hours, quality testing is cut short, incomplete tasks pile up, and deadlines become a constant source of pressure.

Ultimately, the project is delayed, quality issues arise, and the very client the manager tried to satisfy becomes the first to object to the results.

The project manager bought the client's satisfaction in the present moment and paid for it with the team's ability to deliver on future promises.

This opens an important discussion about the true meaning of customer focus.

Serving the client does not mean accepting every request without evaluation. A client may know their needs well, but they do not always have a complete picture of the impact of the requested change on resources, testing, cost, and other commitments.

Here lies the project manager's responsibility to turn the request into an informed decision.

They might say: We can implement this change, but it will require additional costs. Or, it can be implemented within the current budget if we reprioritize. Or, it can be postponed to a later phase to protect the launch date.

These responses are not a refusal to cooperate, but rather a professional practice that protects both parties.

In fact, disciplined change management is part of building trust with the client. An organization that is upfront with its clients about the cost of decisions gives them a better ability to choose, rather than making attractive promises that cannot be fulfilled.

Here, we must not place the sole responsibility for the problem on the project manager; some organizations create a culture that rewards satisfying the client regardless of the cost, and punishes anyone who sets realistic boundaries for commitments.

When the word "no" becomes a threat to one's career, the organization begins systematically producing unachievable promises.

I believe that a professional project manager's competence is not measured by the number of requests they approve, but rather by their ability to turn client desires into realistic commitments that deliver value and protect quality.

The word that best expresses respect for the client might actually be "no," provided it is accompanied by a professional explanation and a feasible alternative.

Trust is not built on promising everything, but on the consistent ability to deliver on what we promise.