The Decision Deficit: Why Unresolved Choices Are Quietly Costing UK Projects Momentum

Most project post-mortems in UK organisations follow a familiar script. The plan was incomplete, the estimates were optimistic, the dependencies were poorly managed. Sometimes those explanations are correct. More often, however, the project was not defeated by a bad plan. It was slowed by a long series of small, unmade decisions that accumulated quietly until the delivery team was working around the organisation rather than through it.

PCPM describes this as decision debt. The term is deliberate. Like technical debt, it is not a moral failure. It is the predictable result of choices being deferred faster than they are resolved. Each deferred decision may seem minor: a scope question, a sign-off, a preference between two workable options, a clarification of who owns an interface. Taken together, they create a backlog that consumes capacity, obscures accountability and makes otherwise sound plans look naive.

How decision debt accumulates

Decision debt rarely arrives through a single dramatic failure. It builds through ordinary behaviour. A steering group asks for more analysis before choosing a supplier. A sponsor wants to consult one more stakeholder. A manager avoids a trade-off because either option will disappoint someone. A meeting ends with an action to 'take it offline', but no one owns the offline conversation. The decision is not refused; it is merely parked. Parked decisions, however, do not stay still. They attract workarounds.

In UK organisations, the pattern is often reinforced by governance design. Approval layers multiply as organisations grow, and each layer may believe it is adding assurance. In practice, overlapping approvals can remove the sense that any single group is accountable. Cross-functional delivery makes this worse. Finance, operations, legal, commercial and technology teams may each hold a legitimate interest in a choice, but no one has been given the authority to resolve the tension between those interests. The result is a decision that is everyone's concern and no one's job.

There is also a cultural dimension. Many teams equate thoroughness with safety. Asking for further information feels prudent, particularly in regulated or reputation-sensitive environments. Yet additional information has a cost, and beyond a certain point it does not improve the decision. It simply delays the moment when the organisation must accept a trade-off. Decision debt grows fastest where uncertainty is treated as a reason to postpone rather than a condition to manage.

Why the backlog erodes momentum

The visible symptom is delay, but the underlying damage is more subtle. When decisions remain open, teams create local workarounds to keep moving. Those workarounds may be sensible in isolation, yet they fragment the delivery approach. One team assumes option A; another builds for option B. Rework follows. Interfaces that should have been simple become negotiated settlements. The plan still looks intact on paper, but the work has begun to diverge from it.

Decision debt also consumes management attention. Every open decision requires a meeting, a chase, a reminder or a status update. None of that effort produces value; it merely prevents the backlog from becoming more visible. The project may appear busy because people are attending governance forums and preparing papers. In reality, a significant portion of the organisation is waiting. The most expensive resource in delivery is often not the team that is working slowly. It is the team that is ready to work but cannot proceed.

Perhaps the most damaging effect is the erosion of trust between delivery teams and decision-makers. Teams begin to plan around anticipated indecision. They pad timelines, avoid dependencies and soften commitments. Sponsors, in turn, interpret cautious plans as evidence that the team lacks confidence. A cycle of defensive behaviour sets in. The plan is not the cause of the problem, but it becomes the place where the problem is argued about.

A weekly decision review that respects people's time

The remedy does not require a new programme office or a heavier governance framework. It requires a short, disciplined routine that makes the backlog visible and forces resolution at the right level. PCPM recommends a weekly decision review of no more than forty-five minutes, chaired by the person accountable for delivery and attended only by those who can resolve the decisions on the list.

The routine rests on a single decision log. It should be simple: a shared spreadsheet or an existing project tool is sufficient. Each entry records the decision required, the owner, the date it was raised, the date by which it is needed, the options under consideration and the current status. The log should not become a record of every conversation. It exists to track choices that are blocking work or creating material risk.

Before the meeting, the chair reviews the log and removes anything that is not genuinely a decision. Some items will be information requests. Some will be delegable. Some will be too vague to resolve and need reframing. This pre-filter is essential. Without it, the review becomes a general status meeting and the backlog continues to grow.

During the review, the group works through the oldest and most consequential open items first. For each item, it confirms the owner, the decision needed and the deadline. It then records one of four outcomes: decide now, delegate with clear authority, schedule a decision by a named date, or close because the decision is no longer relevant. The fourth outcome is often overlooked. Decision debt includes items that have quietly expired; removing them is as valuable as resolving them.

The meeting should not attempt to solve every technical question. Its purpose is to establish who will decide, by when and with what information. If a decision genuinely requires specialist analysis, the review sets a date for that analysis and a date for the decision. This prevents the familiar pattern in which analysis becomes an end in itself.

Making the routine stick

A weekly review will only work if senior leaders treat it as a decision forum rather than a reporting forum. That means attending prepared, accepting trade-offs and avoiding the temptation to reopen settled matters without new evidence. Decision rights should be explicit. If a decision is delegated, the delegate must be able to make it without seeking informal approval from above. If a decision is reserved, the reserving group must turn up and decide.

It also helps to measure the backlog lightly. The number of open decisions, the average age of those decisions and the number that have missed their required date are enough. These measures should be used to improve the system, not to name and shame individuals. A rising backlog is a signal that authority, information or priorities are misaligned.

Decision debt is not eliminated by working harder. It is reduced by making choices at the right level, at the right time and with the right information. UK projects do not need more governance for its own sake. They need clearer delivery. A weekly decision review is a small habit, but it addresses a large and often ignored constraint. The plan may be sound. The organisation must still decide.