A new strategy changes what an organization intends to achieve. The consequential decision is what will change in the commitments that govern its money, people and time. If leaders add a material priority while leaving every competing claim in place, the organization may approve the strategy without making it possible to pursue.
That does not mean every strategic shift needs a larger budget or a dramatic transfer of headcount. It means leaders must establish how the new work will get the capacity it needs. If existing capacity is genuinely available, they can use it. If it is already committed, they must decide which claim will yield—or change the new promise. Resource allocation is part of making the strategic choice, not a scheduling task that begins afterward.
Why the old strategy keeps its resources
An annual budget gives existing work a legitimate claim on future activity. Customers still need service, teams have projects in progress and some obligations cannot be set aside. A new priority enters that system with an approved objective, but it may have no authority to change the assignments on which delivery depends. Adding a project budget does not, by itself, free a specialist, reserve technology capacity or make a senior leader available to settle conflicts.
OutcomesLab’s Resource Gravity describes the tendency for people, capital and leadership attention to flow toward established activities, powerful stakeholders and visible short-term demands. Much of that pull is reasonable. An operating team can point to a customer commitment due this month; a new initiative may offer a less certain benefit next year. The problem arises when those established claims prevail by default, rather than through a decision about their relative value.
Joseph L. Bower and Clark G. Gilbert sharpen this distinction in their discussion of From Resource Allocation to Strategy, the volume they edited. They distinguish an intended strategy from the pattern of proposals that people across an organization sponsor, fund and put into action. In their retrospective account of Intel, manufacturing capacity moved toward microprocessors while senior leaders still understood the company principally as a memory business. The example does not prescribe a funding formula. It shows that recurring allocation decisions can shape strategic direction, whether or not they match the current statement of intent.
For a leader announcing a new priority, the implication is immediate: approval is not the same as displacement. A manager may support the new direction and still honor the assignments, measures and customer promises already in force. When leaders leave the conflict unresolved, teams must negotiate it repeatedly as deadlines arrive. OutcomesLab’s Alignment Debt names the accumulated cost of unresolved disagreement, inconsistent interpretation and weak commitment to shared strategic choices. In an allocation decision, that debt builds when different owners leave the room believing their work has first claim on the same capacity.
Compare the commitments, not just the budgets
Consider a hypothetical subscription software company that wants more customers to complete onboarding without a custom integration project. Leaders approve money for a small product team. The decision is whether that team can deliver the change while the company continues to accept requests for custom reports.
The product team needs an experienced integration specialist to make a common onboarding path work. That specialist is assigned to reporting requests. Some reports are promised to customers; others are optional enhancements. Funding the product team creates capacity for design and engineering, but it does not settle when the specialist can contribute. Nor does it determine who can decline a new reporting request when it conflicts with onboarding.
Leaders could preserve every reporting assignment and move the onboarding commitment later. They could seek another qualified specialist, if one can be brought in soon enough at an acceptable cost. Or they could meet the reporting obligations already owed, defer selected enhancements and reserve the specialist’s time for onboarding. None is automatically right. The choice turns on the expected value of the onboarding change, the value lost by delaying reports, obligations to customers and the time required to make another route workable.
This comparison changes the question presented to the leadership team. Instead of asking whether the new project is funded, it asks what the company will forgo to give the project a credible chance—and whether that cost is justified. If leaders decide the reports matter more, they should adjust the onboarding promise. Asking the product team to deliver the original promise while the specialist remains committed elsewhere hides the decision rather than avoiding it.
Make the resource decision explicit
The Resource-Change Test is a proposed OutcomesLab governance test for material priorities. Its purpose is not to prove that a strategy will succeed. It is to establish whether leaders have made a defensible allocation decision and given someone authority to carry it out.
Start with the outcome and its constraints. In the hypothetical company, the intended outcome is that more customers can complete onboarding without custom integration work. The product team is a means to that end. Existing customer promises limit which reports can be deferred. Stating both matters because it prevents leaders from treating all current work as untouchable or all new activity as strategic progress.
Then compare the ways to supply capacity. What money will fund the work? Which people and skills must be available, and when? What technology capacity must be reserved? Which leadership decisions will require time? In the example, an additional product hire might increase engineering output but leave the integration bottleneck unchanged. Deferring elective reporting work could release the needed specialist, while taking on a contractual report would not be an acceptable substitute for that decision.
The test also records the source of any capacity that moves. A claim that reporting work will shrink should name the requests affected and the obligations that remain. A claim that onboarding can use spare time should identify whose time it is and which assignments already have first call on it. Headcount totals or an unspent budget cannot establish that the required skill is available at the point of need.
Finally, name the leader who can enforce the allocation and the evidence that will reopen it. In the hypothetical company, the reporting and product owners may both need the specialist. If neither can settle the trade-off, the leaders who approved the new priority must do so. They can review the decision after an initial group of customers uses the revised onboarding path, or sooner if a customer obligation threatens the reserved time. At review, they should ask whether the time was actually available, what happened to the deferred work and whether the onboarding outcome warrants continued commitment. The options include keeping the allocation, changing it or narrowing the promise.
Moving resources is necessary in some circumstances, but movement alone is not evidence of sound strategy. In Clark G. Gilbert’s study of one newspaper company responding to the Internet, commitment to new work could still be directed through assumptions that favored the existing business. A leader must therefore ask not only whether people and money moved, but whether the assignments, decision rights and review measures let them serve the new choice. A transfer that leaves the old work in place as everyone’s first obligation may change an organization chart without changing its priorities.
When continuity is a considered choice
An incremental strategy may use capacity that is already available. An organization might have a qualified specialist with room in their schedule, technology that can support the new work and leaders able to make the required decisions without displacing another priority. Protecting established work can also be wise when it preserves a capability that would be costly to rebuild. In either case, a conspicuous budget shift would add disruption without making the strategy more deliverable.
The test is whether that apparent room survives a look at actual demand. Capacity needed to meet recurring peaks or existing service commitments is not reliably free simply because it is unused on an average day. Leaders should confirm the relevant skills, assignments and decision windows, then set a trigger to revisit the judgment if delivery shows that the assumed room is not there.
A material priority does not become real when its budget line appears. It becomes a credible commitment when leaders can explain where its scarce capacity will come from, which existing claims they will protect or change, and who will decide again if the assumptions fail. When old and new work compete, that choice should be recorded alongside the strategy—not left for the teams to discover during delivery.