Funded at a small fraction of what it needs, an opponent's initiative is left to fail, while the budget owner can say it was supported and blame the project when it does.
An example
On the approved list for the year, the patient adherence program at a specialty pharmacy chain had its own line: $140,000. Its head, who reported to the chief clinical officer, had submitted a plan requiring at least $600,000 for pharmacist time, outbound calling, and a data feed from insurers. The allocation came from the chief commercial officer, who ran the budget committee and had argued that adherence work belonged in his team. Asked about it, he said the program had been "fully supported in a tight year." The head ran a pilot in two states with three pharmacists and no data feed. Refill rates moved by a point. At the year-end review, the chief commercial officer presented the result as evidence that the clinical approach did not work and proposed moving the program under commercial.
Why it works
A line item, however small, lets the budget owner claim to have backed a peer, which makes their position look better, and "it was funded and failed" is an easy verdict for reviewers, who need not ask whether the funding was adequate. The paper trail of support undercuts the counter-story, so investigating the link between funding and failure seems pointless. Anyone who argues the funding was too small by design must accuse a colleague of bad faith against a documented allocation, which looks like sour grapes and requires forensic budget work. All it needs is a review culture that never compares allocations with scope, and a sponsor who will not refuse the token amount.
The thinking behind it
Murray Edelman Edelman's The Symbolic Uses of Politics (1964) argues that official gestures can reassure a public while the tangible benefit goes elsewhere. A token line item is a symbolic gesture of support: it lets the budget owner say the initiative was funded, while the money needed to succeed never arrives. Comparing each allocation with the plan's stated minimum scope is the defense that separates the symbol from the substance.
Jonathan Baron Baron and Hershey's Outcome Bias in Decision Evaluation (1988) found, across five studies, that people rate the same decision as better and its maker as more competent when the outcome happens to be good. Reviewers of an underfunded initiative see only the poor result and judge the initiative and its leader by it. Recording what was given against what was needed, before results arrive, protects against being graded on an outcome the funding decided.
Warning signs
An initiative appears on the approved list funded at a fraction, often a tenth to a third, of its stated minimum scope. The budget owner describes it as supported. Nobody compares the allocation with what the plan said it required. Whoever made the allocation has an interest in the initiative failing, or in taking it over. The post-mortem cites results and never mentions the funding.
How to defend yourself
Decide at allocation time, because that is when the trap closes. If the amount cannot deliver the plan, say so in writing before you accept it:
- state the minimum viable budget and what the allocation can and cannot deliver
- offer the decision-maker a clear choice: fund the minimum, cut the scope formally with revised targets, or cancel
- if you proceed, get the revised targets approved in writing
Declining token funding in public is costly, and it breaks the trap. Over time, push for reviews that compare each allocation with the plan's minimum scope, so any post-mortem records what was given against what was needed. Keep your own record of the request, the allocation, and the reply.
How a leader shuts it down
Insist that any allocation below a plan's stated minimum comes with formally revised scope and targets, or with a decision not to fund. Have post-mortems record funding against requirement before judging results. Be wary of allocations made by someone who stands to inherit the program if it fails.