---
title: "The constraint is change capacity, not strategy"
url: "https://vucale.com/blog/the-constraint-is-change-capacity"
description: "Most organisations know what they should do. What they do not have is the ability to absorb another change on top of the four already running, and nobody measures it."
---

# The constraint is change capacity, not strategy

September 1, 2026·2 min read·VUCALE

Ask any management team what the company should be doing differently and you will get a good answer. Ask why it is not happening and you will get a list of reasons that sound like excuses and are mostly accurate.

The binding constraint in almost every transformation is not knowing what to do. It is the organisation’s capacity to absorb change, which is finite, largely invisible, and consumed by things nobody counts.

## What consumes it

**Programmes already running.** Four of them, and the same six people are on all four because those are the six people who understand how anything works.

**Recent failures.** An organisation that has been through a programme that went badly has less capacity than one that has not, and the reduction lasts for years. People conserve effort for changes they believe will survive.

**The day job.** Which does not pause. Every hour spent on transformation is an hour not spent on the thing that generates revenue this quarter, and the quarter has its own targets.

**Middle management.** The layer that has to translate the change into what people actually do, and that is usually the most heavily loaded layer in the company before anything new arrives.

None of these appear on a plan, so plans are built as though capacity were unlimited and the sequencing question were purely logical.

## What running past it looks like

The programme does not stop. It slows, and the slowing is attributed to the wrong causes — a vendor, a technical problem, a resourcing gap — because the actual cause is not measured and therefore cannot be named.

Meanwhile the parts that require no adoption get delivered on time. Infrastructure goes in. Licences are bought. Dashboards are built. The programme reports green on everything except the part where anybody works differently, and that part is not on the plan.

Twelve months later the technology is in place and the behaviour is unchanged, which is the single most common outcome in this field.

## How to work with it instead

**Count what is running.** Every active programme, and specifically who is on more than one. The overlap is the capacity picture and it is usually shocking to the people who commissioned them.

**Sequence rather than parallelise.** Two changes done properly beat five started. This is obvious and almost never done, because stopping a programme requires somebody to say a decision was wrong.

**Make the first one small and real.** Something that visibly works, quickly, restores capacity rather than consuming it — because it changes what people believe about whether this one will survive.

**Budget the change work.** Not as a workstream that gets cut, but as the majority of the effort, because it is.

## The question worth asking first

Not what should we change, but what is the organisation able to absorb this quarter.

The answer is nearly always smaller than the ambition, and hearing it early is what separates a programme that lands from one that is quietly still running two years later, with a new sponsor and a revised roadmap that nobody reads.

-   change management
-   capacity
-   programmes
-   prioritisation

## Keep reading

-   [A consultancy that resells cannot advise you](https://vucale.com/blog/a-consultancy-that-resells-cannot-advise-you)
-   [AI agents in a company that cannot describe its own process](https://vucale.com/blog/ai-agents-and-undefined-processes)