There is a tiny word quietly causing trouble in strategic plans everywhere, and it isn't “risk,” “competition,” or even “AI.” It's the seemingly harmless word and.
Grow revenue and reduce costs. Improve the customer experience and implement a new technology platform. Expand into new markets and develop leaders. Increase productivity and strengthen retention. Modernize operations and launch three new initiatives. And, naturally, continue delivering everything the organization already does.
Individually, every one of those priorities may make perfect sense. Put them together, however, and you may have created an organizational traffic jam and called it strategy.
One of the most difficult disciplines in leadership isn't deciding what an organization should do next. Most leadership teams have no shortage of good ideas, attractive opportunities, or important problems that deserve attention. The harder discipline is deciding what the organization will stop doing, postpone, or do differently to make room for something new.
That's where the word “and” becomes dangerous.
Strategy Is Supposed to Require Choices
At its core, strategy is about choices. If resources were unlimited, organizations wouldn't need much strategy at all. We could pursue every attractive opportunity, fund every worthwhile initiative, hire every person we needed, invest in every promising technology, and give every department everything it requested.
Real organizations don't operate with unlimited resources. Capital is finite. Leadership attention is finite. Technology capacity is finite. And workforce capacity is definitely finite. Strategy therefore requires us to decide not simply what is important, but what is more important than something else.
Yet many strategic plans don't look much like choices. They look more like collections. The organization will grow, transform, innovate, digitize, improve culture, increase efficiency, strengthen leadership, enhance customer experience, reduce costs, develop employees, implement AI, and improve every major performance indicator.
It sounds impressive.
But eventually someone needs to ask a rather practical question: Who's doing all of that?
Every Priority Eventually Becomes Work
Strategic priorities can sound wonderfully clean at the executive level. “Improve customer experience” fits nicely on a presentation slide. So does “accelerate digital transformation” or “expand into new markets.”
But every strategic priority eventually becomes actual work performed by actual people.
Improving customer experience may require someone to analyze feedback, redesign processes, change technology, retrain employees, communicate new expectations, monitor results, and solve the problems that inevitably appear during implementation. Expanding into a new market may require research, recruiting, legal work, operational changes, new partnerships, management attention, and additional customer support.
The strategy may occupy one line on a PowerPoint slide. Executing it could consume thousands of workforce hours.
And that work doesn't magically arrive with its own capacity attached. More often, it lands on people who already have jobs, existing responsibilities, customers to serve, deadlines to meet, and other strategic initiatives underway.
This is where strategic ambition begins colliding with organizational reality.
Organizations Are Better at Starting Than Stopping
Most organizations have fairly well-developed mechanisms for starting things. There are business cases, budget requests, project charters, executive sponsors, kickoff meetings, implementation plans, and announcements.
We are generally much less sophisticated about stopping things.
A new initiative launches, so a committee forms. Someone needs visibility, so a report gets created. Something goes wrong, so another approval is added. A weekly meeting begins because coordination is needed during a particular project.
Then time passes.
The project ends, but the meeting remains. The executive who requested the report leaves, but the report continues. The problem that required the approval disappears, but the approval becomes part of the process.
Nobody intentionally decided that these activities deserved permanent organizational capacity. They simply survived.
Meanwhile, new work continues arriving.
This is how organizations accumulate activity. Each individual addition may be perfectly reasonable. Eventually, though, the total workload bears little resemblance to the organization's actual strategic priorities.
We keep putting things on the plate without ever clearing the plate.
Then we wonder why everyone feels full.
When “And” Becomes an Execution Problem
There is a point where strategic accumulation stops being ambitious and starts becoming counterproductive.
Employees begin juggling multiple priorities that are all described as urgent. Managers spend increasing amounts of time negotiating which department's project should come first. Deadlines move. Projects progress more slowly than expected. People work longer hours trying to keep both strategic and operational responsibilities moving.
Eventually leadership begins asking why execution is struggling.
This is where organizations need to be careful about diagnosis.
What looks like employee resistance may actually be a capacity problem. What looks like poor prioritization by managers may actually be a failure to prioritize at the executive level.
If leadership has declared twelve things critically important, employees cannot solve that problem through better time management. At some point, someone has to decide which of those twelve things wins when they compete.
That's not an employee productivity issue.
That's leadership work.
Attention Is Capacity Too
We often think about workforce capacity in terms of hours, but there is another resource that may be even scarcer: attention.
People can technically work on multiple priorities simultaneously. That doesn't mean they can give each one their best thinking.
Consider a manager moving throughout the day between operational problems, staffing issues, customer concerns, a technology implementation, budget questions, performance conversations, and a strategic transformation project. The manager may be working extremely hard, yet their attention is continuously fragmented.
Executives experience exactly the same problem. A leadership team can approve ten strategic initiatives, but it cannot necessarily provide meaningful sponsorship, problem-solving, decision-making, and oversight to all ten simultaneously.
This is one reason busyness can be such a misleading indicator of organizational health. A calendar filled with meetings and a workforce operating at full speed can create the appearance of tremendous productivity.
But a very busy organization isn't necessarily a strategically focused organization.
Sometimes it's simply an organization with too many “ands.”
Transformation Makes the Problem Even Harder
The capacity problem becomes particularly visible during transformation.
Organizations want to become something different while continuing to operate exactly as they do today. Employees are essentially asked to run the existing business while simultaneously helping build its replacement.
Sometimes that's unavoidable. Customers still need service while a new system is implemented. Payroll still needs to run while processes are redesigned. Revenue still needs to come in while the organization restructures.
But transformation requires real capacity, and leaders need to acknowledge that.
Implementing a major technology platform isn't something employees simply squeeze between their normal responsibilities. Neither is integrating an acquisition, redesigning an operating model, entering a new market, or fundamentally changing how work gets done.
When organizations treat transformation as additional work rather than a temporary redistribution of organizational capacity, implementation inevitably competes with normal operations.
Then leaders become frustrated when transformation takes longer than expected.
The problem may not be commitment. The organization may simply be trying to run two versions of itself at the same time.
The Tradeoffs We Avoid Don't Disappear
This problem often begins with good intentions at the executive level.
Finance has legitimate priorities. Operations has legitimate priorities. Technology has legitimate priorities. HR, sales, marketing, compliance, and every other function can make persuasive cases for their initiatives.
Everyone arrives at the leadership table with something important.
The difficult part comes next.
Instead of choosing among those priorities, executive teams sometimes approve most of them. It's understandable. Saying yes maintains momentum and avoids disappointing a colleague whose initiative genuinely does have value.
But avoiding the tradeoff doesn't eliminate it.
It simply moves the tradeoff somewhere else in the organization.
Eventually, employees and managers are forced to decide which deadlines slip, which customers wait, which projects receive less attention, and which priorities get quietly pushed aside.
Leadership may believe it empowered employees to prioritize.
Employees may experience it as being asked to make strategic choices leadership was unwilling to make.
A New Priority Should Change Something
Whenever a significant new initiative is proposed, there is a question I think deserves more attention:
What changes if we say yes?
Not simply, “How much will it cost?” That's important, but money is only one resource.
What existing work changes? What slows down? What receives fewer resources? What gets postponed? Whose capacity will this consume? Which existing priority moves lower on the list?
If the answer is “nothing,” it's worth looking more closely.
Occasionally an organization genuinely has unused capacity. More often, something will give. The only question is whether leadership decides intentionally what that will be or discovers it later through missed deadlines, declining quality, frustrated customers, and exhausted employees.
Strategic choices are going to happen either way.
The executive team can make them proactively, or the organization can make them accidentally.
AI Doesn't Eliminate the Need to Prioritize
AI adds an interesting dimension to this conversation because organizations understandably see technology as a way to create additional capacity.
And it absolutely can.
If AI reduces a task from five hours to one, the organization has potentially recovered four hours of capacity. That's valuable.
But watch what happens next.
Organizations have a remarkable ability to immediately fill every bit of newly created capacity. We save five hours and promptly add seven hours of new expectations.
Employees become more productive, yet somehow nobody feels as though they have more capacity.
This can create an organizational treadmill where efficiency improves but workload expands at the same pace. Every productivity gain simply creates room for another “and.”
Technology should help organizations accomplish more. But it doesn't answer the strategic question of what is worth accomplishing.
That remains leadership's responsibility.
Maybe We Need a Stop-Doing Process
Organizations usually have formal mechanisms for approving new work, but very few have equally disciplined mechanisms for retiring old work.
Perhaps strategic planning needs both.
Alongside the annual discussion about what the organization will do next should be an equally serious conversation about what no longer deserves capacity.
Which initiatives have served their purpose? Which reports no longer influence decisions? Which meetings exist primarily because nobody has canceled them? Which projects once mattered but have been overtaken by more important priorities? Which processes could disappear?
Stopping something doesn't necessarily mean it failed.
Sometimes it simply means the organization has made a strategic choice.
There is maturity in being able to say, “This was valuable. It served us well. And our capacity now belongs somewhere else.”
Constraints Have a Way of Creating Clarity
Here's an interesting thought experiment.
Imagine your organization suddenly lost 20 percent of its available capacity.
What would you protect?
Which customer commitments absolutely must continue? Which strategic initiatives would remain? Which meetings would suddenly seem unnecessary? Which reports could disappear? Which projects would be postponed? Which activities would everyone quietly admit weren't that important after all?
A constraint like that would force difficult choices very quickly.
The challenge for leaders is creating that level of clarity before a crisis creates it for them.
We shouldn't need a financial emergency, staffing shortage, or unexpected disruption before deciding what actually matters most.
Doing Less Can Produce More
There can be discomfort in narrowing priorities. Leaders worry about missing opportunities or sending the message that something isn't important.
But there is also a substantial cost to pretending everything can receive equal attention.
Focused organizations move differently.
Employees understand what matters. Managers know what should win when priorities conflict. Resources align more naturally. Decision-making becomes easier because people have a clearer filter for determining what deserves attention.
And execution gets faster.
There is a certain irony in this.
Organizations often add priorities because they want to accomplish more.
But at some point, doing fewer things may actually allow them to achieve more of what matters.
Take Another Look at Your Strategic Plan
Pull out your organization's strategic plan and look at it with a slightly different question in mind.
Where have expectations accumulated without a corresponding decision about capacity? Where has new work been added while old work remained? Which initiatives are competing for the same people? Where are managers expected to maintain today's operations while simultaneously building tomorrow's organization?
Then ask perhaps the most revealing question of all:
What has leadership explicitly decided not to do?
If that's difficult to answer, the strategic plan may contain more aspiration than strategy.
Because strategy isn't simply deciding what matters.
A lot of things matter.
Strategy is deciding what matters most, especially when two good things compete for the same limited resources.
So the next time another attractive strategic initiative enters the conversation, don't immediately ask whether it's a good idea.
It probably is.
Ask instead:
If we say yes to this, what are we willing to say no to?
That's where strategy becomes real.
And it may be the best way to keep one tiny word from quietly overwhelming the entire organization.
