The strategy presentation shows twelve strategic initiatives. All important. All urgent. All with a sponsor in the management team. The CEO nods with satisfaction: comprehensive, ambitious, all areas covered.
Six months later: The organization is busy, but nothing is finished. Three initiatives are on schedule. Four are stuck. Five exist only on paper. Resources are fragmented, results are meager.
Good strategy requires focus. And focus means consciously saying no. Cutting eight out of ten good ideas. Not putting them on the waiting list. Not “doing them later.” Cutting them. The question is not: What is most important? The question is: What do we leave out, even though it is important?
A managing director I advised faced exactly this situation. Nine strategic initiatives, all with good justification. Her decision: keep three, stop six. The first few weeks were painful. Six project managers were disappointed, three division heads felt bypassed. But after six months, the three remaining initiatives had made substantial progress, whereas the organization had previously been treading water with nine initiatives. Her conclusion: “Saying no was the hardest part. Sticking to it was even harder. But it was the best decision of the year.”
What is called prioritization in most organizations is a sorted wish list. All ideas remain on the list. All tie up attention. All create expectations. Nothing is cut.
Peter Drucker summarized the problem in one sentence: “There is nothing so useless as doing efficiently what should not be done at all.” The most efficient way to pursue twelve initiatives simultaneously remains ineffective if the organization only has the capacity for three.
The reasons why executives still say yes too often are understandable. Consensus is easier than conflict: saying no means contradicting someone—a division head, a fellow board member, a stakeholder with expectations. Keeping options open feels clever, even though not deciding is also a decision, usually the worst one. Ambition is confused with strategy: a long list of initiatives looks visionary, a short list looks unambitious, yet the opposite is true. The costs of saying yes are diffuse and distributed, while the benefits are concrete and tangible; therefore, the true costs never appear in any business case. And sunk costs bind us: “We’ve already put so much into it” is one of the most expensive arguments.
Every yes has a price. Attention is the scarcest resource: the more initiatives, the less time for each individual one in the management team, until attention is insufficient for any. Resources become fragmented: the same experts are scheduled for multiple projects, switching between contexts and delivering mediocre results everywhere instead of excellence somewhere. Organizational energy is consumed: every initiative generates meetings, coordination, and reporting; the organization occupies itself with itself instead of with results. And credibility erodes: if projects regularly fizzle out, the organization learns that announcements mean nothing and that waiting things out is a valid strategy.
| What happens when you say yes | What happens when you say no |
|---|---|
| Short-term: Everyone satisfied, no conflict | Short-term: Disappointment, need for explanation |
| Medium-term: Resources fragmented, nothing finished | Medium-term: Focused resources, visible results |
| Long-term: Credibility erodes, culture of waiting it out | Long-term: Organization learns that decisions matter |
Prioritization succeeds not through gut feeling or political balancing, but through clear criteria applied consistently.
First: Check against core objectives.
Does the initiative contribute to the two or three strategic core objectives? Not to just any goal somewhere in the strategy, but to the core objectives. Experience shows that it is difficult to pursue more than three core objectives simultaneously. Additionally, check resource realism: Do you have the people, skills, and capacity to seriously pursue the initiative? Practically, not theoretically, with a buffer for the unforeseen. If the answer is “it’ll be tight,” the answer is no. And make the opportunity costs explicit: What can you not do if you do this? Every yes is an implicit no to something else.
Second: Say no without burning bridges.
Justify objectively, not politically. “Does not fit the strategy” is a statement. “We had decided otherwise” is a non-statement. Separate the idea from the person: rejecting an initiative does not mean rejecting the person. Do not offer false hope: “Maybe next year” is not a no; it is a postponed yes that creates expectations. And close the door without locking it: document why you said no so that you can consciously revise it later if conditions change. A clear no is more respectful than a dishonest maybe.
Third: Establish prioritization as a management team decision.
Agree on the evaluation criteria before talking about specific initiatives. If the criteria are only set once the projects are on the table, they will be made to fit. Prioritization is a decision of the entire management, not the CEO alone. If cuts are made, they should be made in all areas; nothing destroys acceptance faster than the impression that some areas are being spared. And what has been decided in the management team is represented collectively to the outside world, even by those whose initiative was cut.
The difference between busy and successful organizations? Successful ones have fewer initiatives, but those get finished.
Saying yes is easy. It makes people happy, at least in the short term. It avoids conflict. It feels like action. Saying no is hard. It disappoints people. It forces conflict. It feels like a restriction. But leadership without no is not leadership. It is the management of expectations that will never be met.
The art of no is not a limitation. It is the prerequisite for everything you want to achieve with your yes.
Tomorrow, take your current list of initiatives and ask yourself one question: Which three initiatives would you stop immediately if you were honest? You probably already know the answer. The question is whether you have the courage to say it out loud.
Twenty priorities are none at all – Saying no alone is not enough. How to create true focus.
The right moment to stop – Sometimes the most important no is the one given to a project that is already running.
Proven tools and models for self-application are available under Solutions.
If you want to take these thoughts further for your company, a no-obligation initial conversation is worthwhile.
