Sequencing the 2026 Spend: Budget Season Reality

The budget is approved, or nearly, and now comes the part the spreadsheet does not help with: the list of things to fund is longer than the money, and everything on it has a champion. The instinct is to split the difference, a little for everything. That is how a year produces twelve half-finished projects.

The alternative is sequencing: fund fewer things, in the right order, all the way to done. The order is not politics. It comes from two questions asked of every item: what risk does it retire, and what does it depend on?

Key takeaways

• Splitting the budget evenly produces half-finished projects, not fairness.

• Sequence by risk retired first, dependencies second, enthusiasm last.

• Fund things to done: a finished small project beats a started large one.

• Hold back a contingency line; the year always adds something.

• Tell the champions the order and the reasons, or the sequence will not hold.

Step 1: Rank by risk retired, not by loudness

The first question for every item: what risk does this retire if it works? The aging server, the unsupported software, the single point of failure. These rank ahead of the improvements and the nice-to-haves, because they are the items whose cost of waiting is not flat.

This ranking is defensible in front of anyone, including the board. Risk first is a principle; whoever shouted loudest is not.

Step 2: Respect the dependencies

Some items cannot go first no matter how worthy they are, because they stand on other work. The new system that needs the network upgrade. The migration that needs the cleanup. Draw the arrows before setting the order.

Dependencies also reveal the genuinely urgent item: the one everything else is waiting for. It may not be glamorous, but the project that unblocks five others earns its place at the front of the line.

Step 3: Fund to done, and keep a contingency

Each funded item gets enough to finish: the licenses, the implementation help, the training, the little tail of costs that projects always have. An item funded to ninety percent is an item that will be back asking in June.

Then hold back a slice, ten or fifteen percent, untouched. The year always adds something: the failure nobody predicted, the opportunity that cannot wait. We argued for the experimental version of this in the pilot budget; the contingency line is its prudent cousin.

Step 4: Sell the sequence to the champions

A sequence only holds if the people whose projects are second and third accept it. Tell them the order and the reasons, in person, before the rumor version circulates. "Yours is third because it depends on the network work" is an answer people can live with.

The champions are also your early warning. When the sequence starts slipping, they are the first to know, and the ones who accepted the order are the ones who will tell you.

Frequently asked questions

What if everything is high risk?

Then the budget and the risk are mismatched, which is a board-level finding, not a sequencing problem. Say so plainly rather than pretending the money stretches.

How do we handle a mid-year emergency?

That is what the contingency line is for. Without it, every emergency raids a funded project, and the sequence collapses by summer.

Should the board see the sequence?

The shape of it, yes: what is funded first and the principle behind the order. It is one of the clearest windows into how the business thinks about technology risk.

A practical next step

Take the funded list and order it by risk and dependency before the year's spending starts. If the list exceeds the money and the trade-offs are uncomfortable, a Decision-Clarity Call is built for exactly that conversation.