The Polite Optimism Tax: Six Kick-Off Beliefs That Inflate Your 2026 Budget

There is rarely a villain in a project that drifts over budget. Most of the time, the people involved are competent, the plan is sensible, and the numbers were put together in good faith. The trouble is that good-faith plans are built on assumptions. In UK project teams, those assumptions tend to cluster around six beliefs. None of them involve anyone lying. All of them can add cost.

Call it the polite optimism tax. It is the extra time, money and disruption that comes from treating a hope as a plan. The fix is not a longer spreadsheet. It is a short, honest audit in the first week.

Belief one: approvals will move at the speed of the meeting

Most kick-off packs show a neat approval route. Real approval chains are messier. A finance business partner is on leave. Procurement wants a supplier check. Legal has a queue. The board paper misses the deadline by a day and the next meeting is a fortnight away. None of this is sabotage. It is just the difference between the policy and the practice. The cost shows up as idle teams, supplier holds and a mobilisation date that slips before anyone has done any work. Ask: who signs off, in what order, and what was the actual turnaround for the last three similar decisions?

Belief two: the people we need will be free when we need them

Kick-off plans often assume named people will be available at the exact moment the plan needs them. In reality, those people are already committed to business as usual, another project or a client deadline. The cost is either delay or expensive cover. Sometimes it is both. Ask: who specifically is doing this work, on which days, and what will be dropped to make room? If the answer is we will find someone, treat that as a risk, not a resourcing plan.

Belief three: supplier lead times have settled down

Supplier lead times are not a rumour. They are a number, and they move. A quote from six weeks ago may not hold. A UK supplier may be quoting from stock it does not have. A specialist component may come from overseas with a customs step nobody has costed. The cost lands as expedited freight, a more expensive alternative or a team waiting for something to arrive. Ask: what is the quoted lead time, what was the last actual lead time, and what triggers an escalation? Add a simple check: has the supplier confirmed the date in writing this month?

Belief four: a small change is a small change

Small changes are rarely small once they pass through design, build, test and approval. A minor tweak to a report can mean new data fields, a revised interface, extra testing and a fresh sign-off. The cost is not just the change itself. It is the rework around it and the decisions that get delayed while the change is absorbed. Ask: what counts as a change, who prices it, and what is the smallest change we have seen take a week? The point is to agree the threshold before the first request arrives.

Belief five: this will run alongside business as usual

Projects are often planned as if the day job politely steps aside. It does not. The same people who keep the lights on are also meant to deliver the new thing. Something has to give, and it is usually sleep, quality or a different deadline. The cost appears as overtime, burnout, missed BAU targets or a project that is technically on time but practically exhausted. Ask: what work stops if this starts? If nothing stops, the plan is probably borrowing capacity it does not have.

Belief six: contingency will cover it

Contingency is not a magic wallet. It is a finite buffer for identified risk. When it is used to absorb optimistic assumptions, it disappears early and leaves nothing for the genuine surprises. The cost is not just the money. It is the loss of options later. Ask: what is the contingency for, who owns it, and what would we do if it were gone by March? If nobody can answer, the contingency is probably already spoken for.

The first-week audit

Run a 45-minute session with the people who actually do the work. Put the six beliefs on a page. For each one, write down the assumption, the evidence, the owner and the date you will check it again. Rate each one red, amber or green. Red means we are guessing. Amber means we have some evidence but not enough. Green means someone has confirmed it in writing. Do not aim for green everywhere. Aim for honesty. A red assumption that is visible is much cheaper than a green assumption that is wrong.

Keep the output short. One page or one simple spreadsheet is enough. The value is in the conversation, not the document. Review it at the end of week one and again before the first major commitment.

The point is not pessimism

An assumption audit is not about refusing to start. It is about starting with your eyes open. UK teams are often very good at being polite about uncertainty. We say things like should be fine, usually quick and not a problem. Those phrases are not lies. They are hopes. The audit simply asks which hopes have evidence behind them.

No one has to mislead anyone for a budget to be wrong. They only have to assume. The polite optimism tax is avoidable, but only if someone puts the assumptions on the table before the work gets moving.