Sometimes “no” is part of strategy

Over the past few years I’ve realised something important: the quality of your portfolio is defined not only by the projects you take on, but also by the ones you refuse. Especially in consulting and strategy, where the true cost of a mistake is reputation.

There are situations where saying no is not weakness, but professional integrity:

• When there are no conditions for a result. Without source data, access to information, the ability to ask real questions, or relevant hands-on industry context, a strategy turns into a “make it look nice” exercise — or a document disconnected from reality.

• When there’s no foundation of trust. Complex problems can’t be solved fast and deep without trust. Otherwise the outcome becomes formal, politically correct — and useless.

• When the request doesn’t match the real problem. A company may think it needs a communication plan when the real problem is strategy. They want a “brand,” but what they really need is a product and model. Doing what was asked instead of what creates value is poor service.

• When timelines kill common sense. Speed is fine until it replaces thinking. When there’s no time to compensate for what’s missing—information, trust, clarity, industry hands on expertise —the risk of failure becomes guaranteed.

There are only three non-renewable resources: reputation, time and energy. Saying no is part of making choices. Because:

• Clients also value honesty — even if you don’t end up working together.

• No is a filter — it separates those who want results from those who want activity.

• Responsibility is not only about what you do — but also what you refuse to do. Taking a knowingly broken project is still a decision, just a bad one.

I choose to work where I can create impact, shift business trajectory and be a partner — not a contractor.

Are you able to say “no” when it’s the right thing to do?