When Small Initiatives Create Large Strategic Costs
Before adding resources, leaders should understand where their existing resources are going—and whether those choices still reflect the strategy.
A company I worked with believed it had a resource problem.
Growth was falling short of expectations. Innovation was central to the company’s strategy, but its most important new-product initiatives were not progressing quickly enough.
The initial conclusion was understandable:
We need more resources.
But a closer look revealed a different problem. The company did not necessarily have too few resources. It had allowed its resources to become spread across too many competing priorities.
The issue was not the strategy itself. It was the management system required to translate that strategy into investment decisions, resource allocation, and execution.
When reasonable decisions add up to the wrong outcome
The company competed in a fast-growing category. New competitors were entering the market, and existing competitors were introducing new products.
Leadership viewed these developments as legitimate threats. In response, the company began launching products of its own—slightly different in positioning, but largely designed to match competitive offerings.
Individually, each decision seemed reasonable.
The initiatives required relatively modest investment. Each promised incremental sales. And doing nothing appeared to carry competitive risk.
But collectively, the decisions were undermining the company’s larger strategy.
The competitive-response launches were:
Producing relatively small incremental sales gains
Cannibalizing some of the company’s existing products
Reaching the market after the competitors they were intended to answer
Pulling critical people and management attention away from higher-priority innovation
No single initiative appeared large enough to cause the problem.
The cost became visible only when the initiatives were considered as a portfolio.
The business cases did not tell the full story
The company’s financial analysis reinforced the problem.
Each initiative had its own business case, and most appeared to generate a positive return. But those calculations did not fully reflect the economic consequences of the decisions.
Expected revenue was included. Cannibalization of existing products was understated.
Direct investment was included. The cost of “borrowing” people from more important projects was not.
Projects were evaluated primarily on whether they cleared an internal financial threshold. They were not consistently compared with one another or with the company’s limited capacity to deliver them.
At the same time, some of the company’s larger innovation projects were being treated as if their projected returns were assured. Their market, technical, and execution risks were not adequately reflected in the analysis.
The result was an inconsistent standard:
Smaller projects looked more attractive because some of their hidden costs were excluded.
Larger projects looked more certain because their risks were understated.
Resource conflicts became visible only after projects had been approved.
Delays were interpreted as evidence that more people were needed.
This was not simply a budgeting issue. Strategy, financial evaluation, resource allocation, and execution had become disconnected.
A better business case is necessary—but not sufficient
The first step was to improve how the company evaluated individual investments.
The analysis needed to distinguish between gross sales and truly incremental sales. It needed to account for cannibalization, execution risk, and the resources required to deliver the work.
But improving the spreadsheet would not solve the entire problem.
Even an attractive initiative can be the wrong priority when another opportunity offers greater strategic or economic value—or when the organization lacks the capacity to execute both effectively.
Leadership needed a way to compare initiatives across the business, make tradeoffs explicitly, and revisit those decisions as conditions changed.
That required a practical portfolio-management process.
Creating a portfolio view of the business
We created a common framework for evaluating the company’s major initiatives. Instead of reviewing each project in isolation, leadership could compare projects using a consistent set of questions.
1. How does the initiative support the strategy?
Every project needed a clear connection to one of the company’s strategic choices.
This did not mean that the original plan could never change. The competitive environment had evolved, and some response was warranted.
But leadership needed to distinguish between deliberately revising the strategy and gradually drifting away from it through a series of reactive decisions.
2. What is the truly incremental economic value?
The financial analysis needed to go beyond projected revenue.
It considered:
Cannibalization of existing products
Required capital and operating investment
Ongoing support costs
Timing and probability of the expected returns
Market, technical, and execution risks
The economic effect of delays or underperformance
This created a more realistic view of both the smaller competitive responses and the larger innovation projects.
3. What resources will the initiative require?
Funding was only one constraint.
The analysis also considered the people, capabilities, leadership attention, and cross-functional support required to deliver each initiative.
This was particularly important because the same critical people were often assigned to multiple projects. On paper, every project appeared adequately staffed. In practice, the organization was relying on the same people to satisfy several “top priorities” simultaneously.
4. What will not happen if we proceed?
This became one of the most valuable questions in the process.
Resources allocated to one initiative cannot be treated as free merely because those resources already exist. If approving a project causes another priority to slow down, that consequence is part of the decision.
The opportunity cost needed to be visible when the project was approved—not discovered months later through missed milestones.
5. What evidence would cause us to accelerate, change, or stop?
Approval was no longer treated as a permanent commitment.
Leadership identified the assumptions behind each initiative and the evidence it expected to see over time. This created defined points at which the company could increase investment, modify the approach, pause the work, or stop altogether.
The objective was not to eliminate uncertainty. It was to manage it deliberately.
Turning the analysis into an operating process
The portfolio analysis provided an initial answer. The larger value came from turning it into a recurring management discipline.
Leadership established a regular review to:
Reassess priorities as market conditions changed
Compare actual results with the original investment assumptions
Identify resource conflicts across projects
Increase support for initiatives demonstrating traction
Modify or stop work that no longer justified the investment
Make explicit decisions about which opportunities would not be pursued
The review was not intended to become another reporting meeting.
Its purpose was decision-making.
That distinction matters. A status review asks whether projects are on schedule. A portfolio review asks whether the company should still be doing those projects at all—and whether they remain the best use of scarce resources.
The answer was not to ignore the market
The company ultimately concluded that a competitive response was necessary.
But it did not assume that another series of copycat launches was the only response. It identified lower-investment ways to address some competitive threats and reconsidered the timing, resource requirements, and risks of its largest innovation projects.
The resulting portfolio was more focused and more realistic.
Just as importantly, leadership had a better way to respond when the next unexpected opportunity or competitive threat emerged.
Instead of asking only, “Is this a good idea?” the company could ask:
Is this a better use of our resources than the priorities already underway?
Why this matters for middle-market companies
This challenge is especially relevant for middle-market businesses.
Resources are finite. A small number of additional initiatives can spread key people too thin. The same executive may be responsible for running today’s business, solving an immediate operating problem, and leading an important growth initiative.
Informal decision-making may have worked when the company was smaller. As the business grows, however, the number of opportunities and dependencies increases. Projects accumulate more quickly than the organization’s capacity to deliver them.
The answer is not necessarily more staff, more meetings, or a complex corporate process.
It is a simple management system that helps leadership answer four questions:
What matters most now?
Where are our resources actually going?
Do the economics still justify the investment?
What should we accelerate, change, defer, or stop?
Strategy becomes real through operating decisions
A company rarely announces that it is abandoning its strategy.
More often, the strategy is diluted through a series of individually reasonable decisions. Each new initiative appears manageable. Each exception seems justified. Each request consumes only a little more capacity.
Eventually, the organization concludes that it lacks resources—when the deeper issue is that it has not made clear enough choices.
Before adding people or funding, leaders should examine the full portfolio of work already underway.
Where is the organization investing its money, talent, and management attention?
What is the real economic contribution of that work?
Which priorities are being delayed to support it?
And which initiatives should no longer be competing for resources?
The answers may reveal that the company does not have a resource problem.
It has a prioritization and management problem—and one that can be solved.