Over the past 26 years, I’ve worked with leaders across manufacturing floors, call centres, head offices and boardrooms in different industries, with different pressures, different cultures. There is one pattern that shows up almost everywhere I go: the leader who has quietly become the organisation’s answer to everything. The one whose diary has no white space left, whose phone lights up through dinner, and whose default response to almost any request, reasonable or not, is “sure, leave it with me.”
We tend to admire this leader. We call them committed, hands-on, a safe pair of hands. But spend long enough inside an organisation and you start to see what that constant “yes” is actually costing the leader, the team, and often the business itself.
This month, I want to talk about a skill that
rarely makes it onto a leadership competency framework, but quietly determines
how sustainable and how strategic a leader can actually be: the ability to say
no, set a boundary, or push back, without being flattened by guilt for doing
it.
The Reflex Behind The Yes
In my experience, very few leaders say yes to everything because they’ve made a considered decision that everything deserves their time. More often, the yes is a reflex and reflexes are worth examining, because they were usually built for a different version of the job.
For some leaders, saying no feels like letting someone down, and the discomfort of disappointing a colleague outweighs the very real cost of yet another overloaded week. For others, being needed has quietly become part of how they know they’re valuable. If people stop asking, what does that say about their relevance? And for many leaders, particularly those managing upward, no still feels risky. It can feel like it might be read as not being a team player, not being “up for it,” or not understanding how much pressure everyone is under.
None of these reasons are irrational. They’re
just rarely examined which means the yes keeps happening on autopilot, long
after it stopped serving anyone, including the people it was meant to help.
What The Constant Yes Actually Costs
The most visible cost is the leader’s own time and energy, but it rarely stops there. When a leader absorbs every escalation, every extra task and every “quick favour,” they become the bottleneck through which everything must pass even the decisions their team is perfectly capable of making without them.
I’ve sat with teams where this dynamic had been running for years, and the pattern was always the same. The team had quietly stopped bringing problems to a close themselves, because they knew the leader would either take it over or redo it anyway. The leader, meanwhile, had no time left for the work only they could do: thinking ahead, developing people, noticing what was changing in the business before it became a crisis. Everyone was busy. Very little was actually moving.
There’s also a slower, less visible cost:
resentment. Leaders who say yes to everything rarely say so cheerfully forever.
It tends to curdle, quietly, into exhaustion, irritability, or a creeping sense
of being taken for granted. These are feelings
that are hard to name because, on paper, the leader agreed to all of it.
See Boundaries As Trade-Offs
One of the reasons “set boundaries” can feel like unhelpful advice is that it sounds like a flat no, delivered once, that solves everything. In practice, most workplace boundaries are trade-offs.
Instead of “I can’t take that on,” a boundary often sounds more like: “I can take this on, but it means the report we discussed for Friday will move to next week. Is that the right call?” Or: “I want to give this the attention it needs, so I’d rather pick it up properly tomorrow than do a rushed version today.” Or simply: “Let me check what’s already on the team’s plate before I commit us to this.”
What changes in each of these isn’t the
outcome so much as the ownership of the trade-off. Instead of the leader
silently absorbing the cost, the cost becomes part of the conversation. Often,
the other person didn’t actually need an instant yes; they needed to know their
request had been heard and taken seriously. A considered “not like that, but
here’s what I can do” tends to land far better than either a guilty yes or an
abrupt no.
When The Request Comes From Above
It’s one thing to renegotiate a deadline with a peer or a direct report. It’s another to do it with the person you report to and this is often where the reflexive yes is strongest, and hardest to question.
I’ve coached leaders who could set boundaries beautifully with their teams, but became a different person entirely the moment a request came down from their own manager. The urgency felt automatically legitimate, simply because of where it came from. But urgency from above doesn’t cancel out the trade-offs below. It just hides them until something else quietly slips.
In practice, this rarely needs to look like
resistance. It can be as simple as: “Happy to prioritise this. To do it justice, I’ll need to move the
client proposal to next week. Are we comfortable with that?” Framed this way,
it isn’t a no. It’s information that most managers genuinely want, because it
lets them make an informed call rather than discovering the cost later, when
something else has already been dropped without anyone deciding it should be.
The Guilt Is Information, Not a Verdict
Even leaders who intellectually understand all of this often still feel guilty the first few times they hold a boundary. That guilt is worth paying attention to but not necessarily obeying.
Guilt is frequently a signal of socialisation rather than a signal of genuine harm. Many of us were taught, directly or indirectly, that being good at our jobs means being endlessly available, and that needing things from other people such as time, patience, or a delayed deadline makes us a burden. Those messages run deep, and they don’t disappear just because someone reaches a leadership title. If anything, the pressure intensifies, because now there are more people who could, in theory, use a piece of the leader’s time.
The useful question isn’t “does this feel
uncomfortable?” It almost always will be, at first. The more useful question
is: “Have I actually caused harm here, or have I simply disappointed someone’s
expectation of unlimited access to me?” Those are very different things, and
learning to tell them apart is, in itself, a leadership skill.
Start Small: Pause Before Saying Yes
None of this requires a dramatic overhaul, and I wouldn’t recommend one. The leaders I’ve seen make this shift sustainably tend to start with one small, repeatable habit: a pause before the yes.
That pause can be as short as a breath, or as concrete as “let me look at my week and come back to you.” In that pause, the question worth asking is simple: what will I need to drop, delay, or hand to someone else in order to do this well? If the honest answer is “nothing, I have the capacity,” then yes is exactly the right response, given freely rather than reflexively. If the answer involves quietly sacrificing something else, family time, a strategic priority, another person’s deadline, that trade-off deserves to be named, even if the final answer is still yes.
Over time, that small pause does something quite significant. It turns a leader’s calendar from a record of everyone else’s priorities into a more honest reflection of their own and it models, for everyone watching, that capacity is finite and worth managing on purpose.
This is, in many ways, the heart of moving
from reactive people management to intentional leadership. Reactive leadership
says yes to whatever lands hardest or loudest. Intentional leadership asks,
even briefly, whether this is the right thing to say yes to and is willing to
live with the discomfort of sometimes answering no.