Initiatives approved without resources can lapse when the manager who holds those resources declines to staff them and says so when asked, so they end without a formal refusal.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Doubts about dynamic pricing came early for the senior vice president of operations at a midscale hotel group: the general managers were already absorbing a loyalty system rebuild, and the summer peak was the worst time to change how rooms were priced. The executive committee approved the head of revenue management's proposal in principle in January, with no date or budget, leaving staffing to operations. The senior vice president assigned the group's two developers to the loyalty rebuild, which had a contractual deadline, and said in the March status meeting that pricing would wait until they were free. In April the head of revenue management asked directly whether operations would support a summer launch. The senior vice president said no, and why. The summer passed at existing rates. In the fall the committee scheduled the proposal for the next year with its own budget.
Why it works
A decision that needs resources can be stopped where the resources are assigned, without a vote. Letting the initiative lapse is the easy path for the manager, who never has to argue against it in front of the committee. Each month without staff erodes the initiative's value as its window passes, which makes it look worse, and pushing it forward costs its champion escalations and re-justifications. It works when the approval left staffing to the manager's discretion, competing priorities are genuinely urgent, and the initiative has a time window.
The thinking behind it
William Samuelson Status Quo Bias in Decision Making (1988), by Samuelson and Zeckhauser, found that people chose an option disproportionately often when it was framed as the status quo, and named transition costs, loss aversion, and commitment to past choices among the causes. An initiative that needs resources to start leaves the status quo in place until someone acts. The manager who holds the resources need not win an argument, since doing nothing keeps the default, which is why sponsors should ask for owners and dates at approval.
Jeffrey Pfeffer Jeffrey Pfeffer's Power in Organizations (1981) locates power largely in structural position: control of resources, information, and the decision process. Approval and execution are separate positions. A committee can approve an initiative, but whoever assigns the developers decides whether it happens. The clean form uses that position openly, and the sponsor's counter is to bring the resourcing decision back to the forum that approved the initiative.
When it fits
Discretion over resources is what makes it available: an initiative approved without the staff or budget it needs, and you holding the staff. It needs genuinely competing priorities, a willingness to say plainly where you stand when asked, and enough standing that your prioritization will hold.
How to use it well
Use the discretion you were given, and be candid about it.
- Assign resources to the priorities you believe matter most, and record why.
- If you do not support the initiative, avoid endorsing it in public; say you have concerns and what they are.
- When asked directly whether you will staff it, answer directly.
- Offer the terms on which you would support it, such as a later date or its own budget.
Expect the sponsor to escalate, and be ready to defend your priorities to whoever can overrule you.
What it costs and where it backfires
Letting work lapse spends goodwill with its sponsor and can make you the scapegoat if the opportunity was real. Executives who overrule you will remember. Candor is what keeps it clean: agreeing in public while privately withholding resources, or pretending to support an initiative you are starving, is deception, and the pattern becomes visible within a few status cycles.
When it is used on you
Shift the conversation from the decision to delivery. Ask for named owners, staff, and milestone dates in the minutes, set the declared support next to the resourcing record, and ask a program office to monitor the milestones so the absence of progress becomes the item discussed.