Let’s Discuss Your Key Person Dependency.

Every organization has one: The person everyone depends on.The SME or technical lead. The manager who someway, somehow seems to be involved in every important decision.

When a project gets stuck, people call them.When a decision needs to be made, everyone waits for them. When a problem needs to be solved, they get pulled into the conversation.

At first, this seems like a strength; but over time, it becomes your biggest constraint.

Organizations struggle with execution, not because they lack funding or resources, but because too much work depends on the same handful of people.

Your portfolio looks healthy on paper, yes, but behind the scenes, everything flows through a one or two person bottleneck.

Here's a simple question worth asking: if one of your key people took a month off tomorrow, what would stop?

The answer will tell you a lot about the true capacity of your organization.

Because sometimes the biggest risk isn't budget, technology, or strategy. It's the fact that far too much depends on one person.

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.

When Everything is Strategic, Nothing is a Priority.

One of the most common things I hear from leadership teams is that they have too many priorities and often, that’s not the real problem.

The real problem is that everything has been labeled as “strategic”.

The new products are “strategic”. Technology investments are “strategic”. Process improvements are “strategic”. The new HR talent initiatives are “strategic”.

When everything is labeled “strategic”, leaders lose the ability to distinguish between what may be important (and can wait) and what is truly essential.

And the outcome of pursuing everything? Resources dwindle. Teams are stretched across too many initiatives, leading to burnout among the superstar employees. Progress comes to a standstill and stakeholders are frustrated.

Many organizations view this as an execution problem, but it’s truly a decision problem.

Strategy is not a list of everything an organization wants to accomplish. Strategy is a set of choices and tradeoffs about where to focus time, money, and attention.

That means some initiatives move forward, some wait, and some never begin.

The strongest organizations aren't pursuing the most initiatives. They make deliberate decisions about which initiatives truly deserve their resources.

Because prioritization isn't about finding good ideas. It's about choosing the few initiatives that move the needle.