It almost always starts with a reasonable request.
“While we're at it, could we add this too?”
“We just need one small change.”
“Could you bring the deadline forward by a week?”
“Could we have a quick call tomorrow as well?”
The first time, the manager says yes.
Being available matters. The client matters. The relationship matters.
Then another request arrives.
And another.
At some point, the project no longer looks like the one that was originally agreed. The team is constantly working under pressure, priorities keep shifting, and what initially looked like flexibility starts to have a cost.
Yet saying no still feels risky.
If I set a boundary, will they think we are not customer-focused enough?
If I raise the issue, will I damage the relationship?
If we cannot find a solution anyway, will they go somewhere else?
This is where managing the client stops being merely a commercial or contractual issue and becomes a leadership issue.
Being customer-oriented does not necessarily mean always saying yes.
Sometimes it means having enough authority to make limits, consequences and alternatives visible before an apparently harmless yes becomes a problem for everyone.
The problem is not always the “difficult client”
Calling someone a “difficult client” can be convenient.
But it does not always help us understand what is actually happening.
Sometimes the client really is aggressive, inconsistent or disrespectful.
More often, however, the difficulty develops within the relationship.
An expectation was never made explicit.
A small exception became the new normal.
An urgent request was accepted without explaining what would have to move.
Extra work was absorbed because doing it seemed easier than opening an uncomfortable conversation.
A postponed decision gradually became the supplier's responsibility.
In 2026, the Chartered Management Institute published an in-depth article on scope creep, the gradual expansion of work beyond what was originally agreed.
What is particularly interesting is that the experts interviewed do not describe it only as a contractual problem. Very often it is also a matter of relationships, expectations and communication: apparently reasonable small requests that, when they are not made visible and discussed, progressively change the nature of the project.
A boundary, therefore, is not only useful once something has gone wrong.
It helps keep the relationship understandable while it is still working well.
The first yes teaches the client what to expect
There is a less obvious aspect to this.
Client expectations are not created only by what we explicitly promise.
They are also created by what we repeatedly do.
If we always reply in the evening, that availability may gradually become an expectation.
If an out-of-scope request is absorbed without discussion, the next request may appear equally normal.
If every urgent request is accommodated without making visible what had to be postponed, the client may conclude that bringing deadlines forward is always possible.
Not necessarily because they are trying to take advantage.
Simply because behaviour creates expectations.
This is one reason why late boundaries are so difficult to introduce.
If we have said yes for months, a sudden:
“That isn't included”
may feel to the client as though the rules have changed.
Managerial capability, therefore, is not only about being able to set a limit.
It is about making the limit visible early enough.
Always saying yes can look customer-oriented. Until the bill arrives
There is a form of availability that looks highly professional.
The manager protects the client from every difficulty.
Changes are absorbed internally.
The team is asked to make “one last effort”.
Work is reorganised.
Uncomfortable conversations are avoided.
The client sees smooth delivery.
The team sees something else.
Deadlines that keep changing.
New activities coming in without anything being taken out.
Priorities that suddenly become urgent.
Evenings or weekends required to keep a promise made elsewhere.
And, above all, a growing sense that any external request automatically matters more than what had already been agreed internally.
At that point, the manager is protecting the client relationship by transferring its cost to the team.
And that is where the issue becomes leadership.
Research on customer-facing roles also suggests that strong customer orientation is not always protective. In some circumstances, especially when it is combined with customer incivility or relational pressure, it may be associated with greater emotional exhaustion.
A 2026 study involving 548 hospitality employees highlighted precisely this paradox: high customer orientation can make people more vulnerable to the effects of customer incivility when adequate organisational resources and boundaries are missing.
Being customer-oriented does not mean having no boundaries.
Source:
https://so06.tci-thaijo.org/index.php/IJBS/article/view/289523
Why saying no is difficult even for experienced managers
The problem is not always knowing what to say.
Sometimes the manager knows perfectly well that the request is not sustainable.
The difficulty lies in what they imagine might happen afterwards.
The client will get angry.
They will think we are not collaborative enough.
We could lose the contract.
My manager will ask why I couldn't find a solution anyway.
Perhaps a more capable manager would have made it work.
This is where business coaching can be particularly valuable.
Not because it teaches a formula for saying no.
But because it helps distinguish what is actually happening from what the manager fears might happen.
Is accepting the request really necessary?
Or am I avoiding a difficult conversation?
Is the client asking for reasonable flexibility?
Or have we simply never clarified the boundaries?
Am I protecting an important relationship?
Or am I trying to avoid being perceived as unhelpful?
The distinction may be subtle.
But it completely changes the way we enter the conversation.
A boundary is not a wall
When we hear the word boundary, it is easy to imagine a rigid response:
“No, that's not included.”
But setting a boundary does not necessarily mean opposing the client.
A good boundary can keep collaboration open.
It says:
this request is possible, but it has consequences; let's decide together how to manage them.
That is very different.
Imagine that a client requests an additional activity only a few days before delivery.
There are three possible responses:
“We can't do it.”
“Fine, we'll do that too.”
Or:
“I understand why this is important. We can include it. To do that, however, we need to decide whether to move the delivery date or reduce one of the activities already planned. Which option would be more useful for you?”
In the third response, we are not rejecting the client.
We are making the trade-off visible.
And, importantly, we are returning part of the decision to the person who is changing the request.
A practical sequence for difficult client conversations
When pressure increases, it can be useful to remember four simple steps:
acknowledge → define the boundary → make the trade-off visible → offer a choice.
It is not a script to recite.
It is a way of structuring the conversation.
Acknowledge
Before setting a limit, recognise the need.
“I understand why this change matters to you.”
“I understand the need to bring the deadline forward.”
“I can see why this has become a priority.”
Acknowledging does not mean agreeing.
It means showing that you understand what matters to the other person.
Define the boundary
Then make the reality visible.
“This activity was not part of the agreed scope.”
“With the resources currently allocated, we cannot bring both deliveries forward.”
“This change requires additional work beyond what is already planned.”
A boundary works better when it describes facts and conditions rather than assigning blame.
Make the trade-off visible
Every choice uses resources.
Time.
People.
Budget.
Priorities.
Quality.
The client needs to be able to see what changes when the request changes.
“If we bring this activity forward, we need to postpone the other one.”
“We can add this element and keep the deadline, but it will require additional resources.”
“If this becomes the new priority, we need to agree which of the previous priorities will no longer be one.”
Pressure decreases when the cost of the decision stops being invisible.
Offer a choice
Finally, instead of ending with a refusal, open a decision.
“Which of the two options would you prefer?”
“Which priority creates more value right now?”
“Would you rather keep the delivery date or expand the scope?”
A conversation that seemed to be:
you versus us
can become:
which choice do we make together?
The most dangerous phrase may be: “We'll take care of it”
There are times when this phrase communicates reliability.
And rightly so.
The problem arises when it becomes an automatic response.
“We'll take care of it” can sometimes mean:
I don't want the client to see the problem.
I don't want to open a conflict.
I'll find someone internally who can absorb the cost.
We'll sort it out later.
But some difficulties need to become visible.
Not to dump the problem on the client.
To allow the client to participate in the decision.
If we systematically hide the cost of requests, the client has no way of knowing that what they are asking for is becoming unsustainable.
And the team ends up working inside a promise they never helped to make.
When the manager becomes the buffer between client and team
Many managerial roles sit exactly in this position.
The client on one side.
The team that has to deliver on the other.
And in the middle, someone trying to hold the two together.
Being a good buffer can be useful.
The manager filters noise, protects the team from unnecessary tension and translates external requests into clear priorities.
But there is a difference between filtering and absorbing.
If the manager keeps absorbing everything, sooner or later the pressure appears somewhere else.
Irritation.
Excessive control.
Permanent urgency.
Sharper feedback.
Micromanagement.
Overload.
This connects directly with what happens to managers under pressure: pressure that is not processed is easily passed on.
Protecting the team does not mean hiding every problem from them.
It means preventing unnegotiated problems from automatically becoming operational emergencies.
A client can be important without always being right
“The customer is always right” is a useful phrase for reminding us of the importance of service.
As a managerial principle, however, it is incomplete.
The client may be right about their needs.
They may have information we do not have.
They may change their mind.
They may reasonably ask for flexibility.
But they may also underestimate the complexity of a request.
They may not see the organisational cost of a change.
They may hold expectations that are incompatible with one another.
They may ask for something that puts quality, deadlines or people at risk.
Professionalism does not mean automatically agreeing.
It means bringing into the relationship what the client cannot see from the outside.
That is one way adult professional trust is built.
Not a relationship in which one side asks and the other executes.
A relationship in which both sides bring the information required to make better decisions.
When the problem is not the client but our need to please them
This may be the most uncomfortable question.
Some highly capable managers struggle to set boundaries precisely because they care deeply about the relationship.
Being seen as available, reliable and solution-oriented is an important part of their professional identity.
Saying:
“We cannot do this under these conditions”
can feel almost like a failure.
But reliability and availability are not the same thing.
Someone can be extremely available and promise something they will not be able to deliver.
Or they can be clear about limits and keep every commitment they make.
Which one builds greater trust over time?
Coaching can be particularly useful here: helping managers notice which personal beliefs are entering the professional relationship.
I always have to find a solution.
I cannot disappoint the client.
Saying no creates conflict.
If I'm good at my job, I should be able to make it work anyway.
These beliefs are understandable.
But when they become automatic rules, they can reduce the very clarity the role requires.
The contract matters. But it is not enough
Of course, some issues need to be managed through contracts, scopes of work, change requests, budgets and clearly defined responsibilities.
Not everything is coaching.
And it would be naive to assume that a good conversation can compensate for a poorly defined contractual scope.
The point, however, is that even the best contract has to be lived through real conversations.
Because scope creep rarely arrives with a warning that says:
“Attention: I am changing the scope of the project.”
It sounds more like:
“Since you're already working on it…”
“It's only a small change.”
“Could we also take the opportunity to…”
The manager needs to recognise that moment.
And have enough clarity not to postpone the conversation until the problem has become too large.
Not every relationship needs to be saved
There is one final possibility that we often avoid naming.
Not every client relationship should be maintained at any cost.
A difficult request can be negotiated.
A misunderstanding can be clarified.
A conflict can even strengthen a professional relationship.
But when respect, reciprocity and the minimum conditions for working well are consistently absent, the question changes.
It is no longer:
“How can I say no better?”
It becomes:
“Is this relationship still sustainable?”
Setting a boundary may have a cost.
Not setting one has a cost too.
Leadership also means making both visible.
Being customer-oriented also means knowing when to challenge the client
Perhaps we can move beyond a common misconception.
A client does not only need someone who will deliver whatever they ask for.
Especially in complex professional relationships, they also need someone able to say:
this choice will have this consequence.
this objective is not compatible with this constraint.
this request is possible, but something else will need to change.
based on our experience, this option increases a risk that is worth discussing.
Saying yes to everything may look like service.
Telling the truth, even when it is uncomfortable, can be a higher form of service.
A boundary does not necessarily destroy trust.
When it is clear, consistent and respectful, it may be exactly what allows trust to last.