Attaching a smaller project to a must-pass program it genuinely serves gets it funded on the host's schedule, without a separate approval fight in the budget contest.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
For two years the chief operating officer of a mid-sized commercial bank had wanted a customer analytics platform, and lost it twice in the annual budget contest. Then a regulatory consent order required the bank to rebuild its anti-money-laundering monitoring by year-end, and the remediation team found it needed better customer data, which the analytics platform would supply. The platform went into the remediation plan as a named $2.6 million line, with a page explaining which consent-order requirements it served and a note that marketing would also use it later. The steering committee, working against the regulator's deadline, approved the plan as a whole. The head of financial planning asked about the line in the second-quarter review. The chief operating officer walked through the dependency and the documents, and the line stayed. The platform went live in the spring as a remediation deliverable.
Why it works
Borrowing the host program's urgency makes the rider look better, and it avoids its own prioritization contest because governance reviews the host's gating criteria, which makes it easier. Removing it mid-cycle is costlier still: it means re-baselining the host and taking the blame for delaying a must-pass program. It works best when the host is urgent and time-bound, when review happens at program level, when the rider is part of the plan from early on, and when reviewers fear exposure for any delay.
The thinking behind it
Richard H. Thaler Richard Thaler's Mental Accounting and Consumer Choice (1985) shows that people sort money into separate mental accounts and judge each expense against the account it falls in, so the same sum can feel trivial in one account and unacceptable in another. A $2.6 million project reviewed on its own competes with every other request. Inside a $34 million must-pass program it is judged against that account and looks small. The clean form keeps it a named line so reviewers can still see it.
Ronald H. Coase In The Problem of Social Cost (1960), Ronald Coase argues that when bargaining is costly, who holds the rights and how expensive it is to negotiate decide what happens. Once the rider is part of an approved program, removing it means reopening the program's scope, schedule, and budget with every party to it, under a deadline. That cost of renegotiation, more than the rider's own merits, is what keeps it in.
When it fits
Suited to a project that genuinely serves a must-pass program's goals and has failed, or would fail, the ordinary budget contest on its own. It needs a host with a real deadline, a sponsor with standing in the host's governance, and a link to the host's requirements that a skeptical reviewer would accept.
How to use it well
Start from the host's requirements and show, item by item, what your project contributes to them.
- Put the project in the plan as its own named line, with its cost.
- Write a short page linking it to the host's requirements, and state openly any other uses it will have.
- Brief the host program's leader first, since they will be asked to defend it.
- Attach early, while the plan is being drawn up, so the project is part of the design and not a late insertion.
When a reviewer questions the line, answer on the merits and offer the documents.
What it costs and where it backfires
You spend the host program's credibility, and its leader's, on your project; if the link looks thin, the host is contaminated and you lose an ally. Reviewers who feel outmaneuvered remember it at the next budget. Everything turns on the link being real: if the project does not genuinely serve the host, or its line is hidden from reviewers entitled to see it, the move becomes misrepresentation, and an audit or regulator will treat it as such.
When it is used on you
If someone attaches a rider to a program you review, skip the merits debate under the host's deadline. Ask for line-item decomposition before the deadline sets in, send items without a standalone case to an independent review, and ask the host program's leader to defend the attachment in public. Many riders detach once named.