One of the hardest and most counterintuitive leadership skills I had to learn as a CEO was this:
Saying no is a strategic skill.
I did it a lot.
And yes, it caused friction at times.
But it was essential.
Not because ideas, funding, partnerships, or new roles were bad. Many were exciting and genuinely well intentioned. But because every 'yes' has a cost, and those costs are often invisible at the moment you say yes.
Saying no protects your people.
It protects their focus, energy, and ability to deliver the mission well.
It also protects you, by ensuring your attention is spent where it matters most.
Take funding as an example.
Every new grant brings opportunity. It also brings reporting, coordination, meetings, expectations, and opportunity cost. Even “good” money can quietly constrain you if it pulls attention away from your core priorities.
The same is true for new roles.
Hiring too early, or at the wrong moment, can destabilise a growing organisation. Each new role changes workflows, decision making, and cross team execution. Sometimes that disruption is game changing. Sometimes it derails momentum. Timing matters more than intent.
Over time, I learned that the mission must be the guide for saying no.
Before saying yes, ask:
Does this align with our mission?
Does it advance this year’s priorities?
Do we have the capacity to do this well?
Is the timing right?
Who benefits, and who bears the cost?
What work does this displace?
Because the hidden costs of yes add up quickly.
Admin. Meetings. Coordination. Expanding expectations.
What starts as an exception easily becomes the new norm.
When that happens, follow through slips, teams stretch too thin, annual rhythms break, and burnout creeps in quietly.
An explicit default stance can be helpful:
- Always no, unless it replaces existing work with less effort or significantly increases stability
- No to work requiring new systems or reporting unless setup and maintenance are funded and integrated into plans
- No to projects or partnerships outside the annual plan unless they clearly accelerate an existing priority and have defined cross team bandwidth
- No to work that fragments alignment across departments unless it directly strengthens culture and cross functional performance
Just as important as the decisions was how these are communicated them.
Boundaries need to be clear internally and externally.
If they are not clear internally, teams spend huge amounts of time exploring opportunities that will never be taken forward.
Introduce simple discipline early on.
A single place for new requests.
Clear go or no go moments.
Decisions written down, with the reason why.
And language embedded into team norms: before we say yes, we always check…
Perhaps most importantly, is to normalise bringing new ideas into planning cycles, not constantly throughout the year (there are always exceptions).
Saying no is not about being closed or unambitious.
It is about protecting focus so that when you do say yes, you can actually deliver.
Curious how others handle this.
What rules or disciplines have helped you say no without losing momentum?
Warmly,
Liz
Strategic Advisor | Former CEO | Founder, Volante
Based in Kenya, available globally
