The Projects That Won't Lie Down: A Portfolio Triage for UK SMEs

Most UK SMEs do not suffer from a shortage of ideas. They suffer from an excess of half-remembered ones. A customer portal begun before a change of leadership. A rebrand paused pending a decision that never came. A software implementation that reached 70 per cent and then settled into permanent pilot status. Individually, each looks minor. Collectively, they form a shadow portfolio that consumes management attention, cash and credibility without appearing on any single report.

The problem is rarely visible in the formal project list. It sits in the gaps between strategy away-days and weekly operations meetings, in the apologetic updates that begin with "we have not quite got to that yet". For lean teams, this clutter is often a greater constraint on growth than a lack of new opportunities. Every stalled initiative holds a claim on the same finite pool of leadership bandwidth. Before planning the 2026 operating rhythm, it is worth conducting a deliberate audit of the projects that will not lie down.

Why portfolio clutter survives

Initiatives rarely persist because they are strategically sound. They persist because cancelling them carries a social cost. Someone championed the idea. A supplier was appointed. A customer was told something would arrive. Ending the work can feel like an admission of failure, so it is deferred instead. Deferral is not neutral: it converts a clean decision into a slow leak of resource.

There is also an accounting illusion at work. The original business case may have justified the spend, and the sunk cost is treated as a reason to continue rather than a reason to reassess. But the relevant question is not what has already been spent. It is what the project will still require in cash, staff time and management focus, and whether that commitment is the best use of those resources now.

For UK SMEs, the constraint is particularly acute. A finance director may also be managing HR and IT. A operations manager may be covering sales support. There is little slack to absorb the governance overhead of dormant work. Portfolio clutter therefore becomes an operational issue, not merely a strategic one.

Step one: build the honest inventory

Start with a simple list, but make it broader than the official project register. Include anything that has consumed time or money in the past twelve months and is not yet closed. Sources should include management accounts, supplier invoices, board packs, CRM notes and the calendar of recurring meetings. Ask each department head to name the three pieces of work they are quietly keeping alive without a current decision date.

For each item, record four facts: the original objective, the current status, the named owner, and the next decision date, if one exists. Do not accept "ongoing" as a status. Use plain categories: not started, active, stalled, awaiting decision, or effectively abandoned. The purpose is not to embarrass anyone. It is to make the invisible visible.

A useful discipline is to include inherited projects. New leaders often tolerate legacy work to avoid appearing disruptive. That tolerance has a price. If an initiative cannot be explained in two sentences to a colleague outside the team, it probably needs a formal review rather than another quarter of benign neglect.

Step two: estimate the true carrying cost

The direct cash cost is the easier part. Look for continuing licence fees, retained suppliers, contractor days and rework. These are often small enough to escape scrutiny individually but material in aggregate. A dormant software subscription at £400 a month is not a rounding error; it is £4,800 a year for a capability nobody is using.

The harder and more important cost is management attention. Estimate the hours spent each month in status meetings, preparation, informal catch-ups and the mental switching cost of returning to a complex file. Multiply by a sensible internal day rate. This is not a precise accounting exercise, but it does not need to be. A rough figure is enough to change the conversation from "we should get back to it" to "what else could this attention fund?"

There is also an opportunity cost that should be stated explicitly. If the same leadership hours were redirected to a live customer retention programme or a pricing review, what would the likely return be? The comparison does not need to be exact to be revealing.

Step three: decide, do not defer

Every item should leave the audit with one of four decisions. The first is to kill it. This means closing the file, ending the subscription, informing affected stakeholders and recording the rationale. Killing a project is a legitimate management action, not a failure of persistence.

The second is to complete it. This applies only where the remaining work is genuinely small, the original objective remains valid and the completion cost is clearly bounded. A project at 95 per cent should not be abandoned out of tidiness, but a project at 60 per cent with an open-ended scope should not be called nearly finished.

The third is to restart it with a new mandate. This is appropriate where the objective still matters but the previous approach, owner or budget was wrong. A restart must come with a fresh business case, a named sponsor and a fixed review date. Without those conditions, it is simply a deferral with better wording.

The fourth is to quarantine it. This is a time-limited pause with a specified decision date, usually no more than one quarter away. Quarantine is not a permanent state. If the date arrives without a decision, the default should be closure.

Step four: protect the operating rhythm

The audit should feed directly into the 2026 planning cycle. A simple portfolio dashboard, reviewed monthly, can prevent the same clutter from accumulating. It should show active projects, quarantined items and decisions due. The rule is that no project enters the portfolio without a named owner, a measurable outcome and a scheduled review point.

Leaders should also examine whether their meeting structure rewards activity over completion. If every project gets a standing agenda slot regardless of status, the organisation is quietly signalling that persistence matters more than progress. A better approach is to reserve meeting time for decisions and exceptions, not for narrative updates on work that is not moving.

Finally, make closure visible. When a project is retired, explain what capacity it releases and where that capacity will now go. This turns killing work from a defensive act into a positive reallocation. It also gives managers permission to be honest about what is not working, which is the foundation of any credible operating rhythm.

The discipline of a smaller portfolio

A smaller portfolio is not a less ambitious one. It is an ambition that has been concentrated where it can actually be delivered. For UK SMEs entering a demanding planning cycle, the most valuable strategic question may not be which new initiative to add, but which existing one to stop. The projects that will not lie down are rarely harmless. They are the quiet competition for the attention, cash and credibility that growth requires.