Projects

Why some Critical Chain implementations fail, and others transform

Mohit Saini · 22 Sept 2024 · 4 min read

Why some Critical Chain implementations fail, and others transform

The logic of Critical Chain Project Management is easy to accept. Anyone who has watched bad multitasking and deadline-driven behaviour wreck projects nods along in a workshop. CCPM doesn’t need a hard sell.

Yet implementations vary widely. Some deliver dramatic gains. Others produce no measurable improvement at all. What separates them?

How to tell them apart

In the disappointing implementations, ask for results and you hear about intangibles: “better visibility”, “more planning discipline”. Ask about concrete improvements (shorter lead times, more projects completed) and the answer is that the product mix is too varied to measure. The people using the system see it as extra paperwork, while priority conflicts still disrupt their day. Top management has mixed feelings: plans and updates look systematic, but problems still surface too late, and people still don’t seem proactive enough.

In the successful implementations, the best evidence comes from the most junior people, say, a designer in the engineering department. They describe a different working life: fewer interruptions, not being pulled in several directions, issues resolved much faster. They feel more productive. The numbers show improvements well beyond any noise from product mix. Top management feels genuinely in control: work is ready well before customer deadlines, and the last-minute rush has largely disappeared.

These differences have nothing to do with the type of industry or the ability of the people involved. The logic of CCPM holds in product development, software, engineer-to-order manufacturing and construction alike.

The real cause: cherry-picking and wrong sequence

The difference lies in which parts of the solution are implemented, and in what order.

CCPM’s components build on each other. Each one works only when the one before it is in place. Pick some and skip others, or implement them in the wrong order, and the whole delivers little.

Two common mistakes:

Planning before reducing multitasking. In an environment of rampant multitasking, no plan stays reliable. Building Critical Chain plans with buffers in such an environment creates a lot of work maintaining plans that help nobody.

Common priorities and full-kit rules without limiting work in progress. People like the idea of one priority list for everyone and of not starting work without its inputs. But without a limit on open work, pressure from stakeholders soon forces changes to the priority list, and within weeks it is meaningless.

The step people skip: freezing

Look at failed implementations, and a pattern emerges even in what they skip. Most skip the first step: reducing work in progress in the starting departments, such as design, by freezing open work according to an agreed priority, and then letting new work in only as other work is completed.

Freezing feels risky, so managers avoid it. Sometimes even consultants avoid it.

Is freezing really risky?

Try this test. Ask each department in your organisation to name its top three priority projects right now. The lists will almost certainly differ, often widely. That shows how little agreement there is on what is truly important.

Now consider: every department already has more work than it can handle. So each one already has a short list of things it is actually working on, and a longer list of things it isn’t. A “frozen list” already exists everywhere. The difference is that today each department decides its own, at the lowest level, and the lists change daily. Projects fall out of step, and every project slips.

Freezing doesn’t create new risk. It replaces many hidden, conflicting, ever-changing lists with one agreed, centrally managed list of active and waiting work. That alignment is what makes the later steps (planning with buffers, gating with full kits, managing by buffer status) possible.

In practice, the sequence that works looks like this:

Step What it does Why it must come first
1. Freeze and limit work in progress One agreed active list, one out one in Without it, no priority or plan holds
2. Full kit before starting Work starts only when inputs are complete Needs step 1 to free time for preparation
3. Daily flow meetings Obstacles cleared within a day Needs few enough open tasks to discuss
4. Plans with buffers Safety pooled at the end of each project Plans are reliable only once flow is stable
5. Buffer management Priorities and escalations by buffer status Needs steps 1–4 to give meaningful signals

Skipping to steps 4 and 5 is tempting, because they look like the “real” Critical Chain. They are the last steps, not the first.

Knowing the full solution and knowing the order in which to implement it are two different skills. Success needs both.

The icing (buffered plans, fever charts) can go on only when the base (frozen, limited work in progress) is in place.

Related reading

Mohit Saini

Strategy, supply chain & sales transformation consultant. About · Book a discussion