Who Has the Power to Say No?

There is something interesting that happens in organizations: there’s normally a number of people who can get work started and there are very, very, few who can stop it.

A leader has an idea or someone shouts the loudest. A pet project comes up. A customer makes an reasonable request. Your IT department identifies an incredible opportunity.

And before long, after a few more meetings, another initiative is added to the “strategy”.

On its own, there's nothing wrong with that. The ideas sound reasonable and everyone means well.

The challenging part is that organizations rarely struggle because they don't have enough ideas; they end up struggling because they have too many! As a result, another “priority” is added to the pile.

Teams are asked to do more with the same resources, there is no clear focus, and every project needed to be done yesterday.

At some point, someone needs the authority—and the support—to say, "Not now," or more realistically, "No."

That's not about being difficult. It's about protecting the organization's ability to focus on what matters most.

So here's a question worth asking: when a new initiative is proposed, who in your organization actually has the power to say no?

If the answer isn't immediately clear, it may explain why prioritization feels harder than it should.

Because every organization has people who can say yes. The organizations that rise to the top also have leaders who can say no.