The Hardest Part of Strategy Is Choosing What Not to Do

A manager receives a new opportunity.

It looks promising. A client wants to explore something. A stakeholder asks for another initiative to be added. An RFP arrives. A familiar activity continues because it has always been part of the team’s work.

None of it looks obviously wrong.

In fact, the opportunity may be attractive. It may carry revenue potential. It may strengthen a relationship. It may keep a stakeholder happy. It may feel safer to say yes than to explain why the team should not commit.

The manager pauses.

The team is already stretched. People have agreed where attention should go. But this opportunity is difficult to reject because it is not a bad one.

That is the hidden tension in strategy.

Choosing what to do is usually the easier part. Choosing what not to do is where strategy becomes uncomfortable.

The opportunity that still looks attractive

It is easier to say no to something obviously poor.

If an opportunity has no value, no fit and no real upside, the decision is usually straightforward.

The harder situation is when the opportunity has some value.

The customer is real. The request is reasonable. The stakeholder has a point. The activity has history. The RFP could lead somewhere.

This is why strategy is hard in practice. Managers are rarely choosing between good and bad. More often, they are choosing between good and better, or between useful and strategically important.

A team can defend almost every item on the table. That does not mean every item deserves the same level of attention.

The question is not only, “Is this worth doing?”

The better question is, “Is this worth doing given the game we are trying to win?”

That question changes the conversation.

It does not dismiss the opportunity. It tests whether the opportunity belongs.

Why saying no feels uncomfortable

Saying no can feel negative.

It can feel like a lack of ambition. It can feel like turning away growth. It can feel like disappointing a stakeholder, weakening a relationship or closing a door too early.

That emotional pressure is one reason managers keep too many options alive.

They say yes for now. They agree to explore. They keep the project running. They submit the proposal. They continue the legacy activity because stopping it would create a conversation they would rather avoid.

The problem is that every yes has a cost.

That cost may not appear immediately. It may show up later as diluted focus, slower progress, weaker quality, tired people or less time for the work that actually matters most.

Avoiding the no does not avoid the trade-off.

It only makes the trade-off less deliberate.

If the team does not choose what to stop, reduce or deprioritise, the system will choose for them. Capacity will run out. Attention will fragment.

That is not strategy.

That is drift.

The practical lesson

The practical lesson is simple:

Choosing what not to do is not a sign of weak ambition. It is how strategy protects focus.

Not playing does not mean the opportunity is bad. It means the team understands where it has the best reason to commit its time, energy and capability.

This is especially important when an opportunity is attractive but does not fit.

A price-driven opportunity may still have revenue potential. But if the organisation does not have a real cost advantage, the team needs to ask whether that is truly the game it wants to play.

An RFP may be worth considering. But if the team has no clear edge, limited access to the decision-makers, or little understanding of the customer’s real problem, full commitment may not be the best use of scarce capacity.

A legacy activity may feel familiar. But if it no longer supports the direction, continuing it may simply protect the past at the expense of the future.

These are not easy calls.

But strategy becomes clearer when managers can ask:

• Does this fit the game we are trying to win?

• Do we have a real edge here?

• Will this strengthen our position, or only consume capacity?

• What are we not doing because we are saying yes to this?

• What would saying no protect?

Those questions make the cost of yes more visible.

What saying no protects

Saying no is often framed as loss.

But it can also be protection.

It protects attention. It protects quality. It protects team capacity. It protects the strategy from being slowly diluted by attractive distractions.

It also protects credibility.

If a team says everything matters, people eventually stop believing the strategy. They learn that every request can be added and every project can stay alive.

But when a manager can explain why something is not being pursued, the strategy becomes more real.

“We are not prioritising this because our current focus is here.”

“This opportunity has value, but it does not fit where we are trying to build strength.”

“We do not have a clear edge in this game, so we will not commit our best resources to it now.”

That explanation is not always easy to give. But it helps people understand that focus is chosen.

The real work

The real work of strategy is not only choosing the work that sounds valuable.

It is protecting the work that matters most from attractive distractions.

That requires judgement. It requires courage. It requires managers to make the cost of choice visible, especially when the thing being declined has some value.

This is also one of the core reflection questions behind 100 Questions Every Manager Should Ask: Where are we choosing not to play?

It is a simple question, but it marks an important shift. The manager is no longer only adding priorities, accepting opportunities or keeping options alive. They are helping the team create boundaries around the strategy.

A strategy without boundaries will eventually become a collection of good intentions.

A strategy with boundaries gives people a clearer way to act.

Not every opportunity is ours to chase.

Not every customer is ours to serve.

Not every activity deserves to continue.

Not every yes is strategic.

One question for reflection:

What are we still saying yes to because saying no would feel uncomfortable?

If this reflection was useful, join the Riverstone mailing list for practical leadership reflections and updates as the Riverstone resource library develops.