How to repair failed Critical Chain Implementations? Before it is too late?

Sometimes even the best strategy fails;-(

This post and ebook are about “How to repair failed Critical Chain implementations? Before it is too late!”

Productivity and efficiency

Because Critical Chain Project Management is probably one of the best project management strategies. Powerful for boosting productivity by 20% – 50% and making teams more efficient in a very short time. But this also sometimes fails.

Personal Credibility

When that happens, there is a lot at stake. You’ve got to take the loss and rule it out for the future. You’re back to the drawing board again and thrown back one or two years. And when you are the instigator, you’re losing personal credibility. I know what you’re going through.

Project Pipelines

I discovered that just managing project pipelines alone are sufficient to deliver on the promise of Critical Chain. It is a systems theory phenomenon, you can do this without knowing the project schedules, how resources are shared, or taking external dependencies into account. This may sound weird. But what it means that is you can have it up and running in a few days or weeks. Practically without having to change anything for anybody.

Advanced planning software

For implementing Critical Chain typically a number of obstacles must be overcome.

The quality of project schedules must be upgraded. All project managers must learn critical chain and buffer management. They must learn CCPM planning software. Setup the staggering and pipeline management. To keep everything up to date requires lots of administrative overhead. This all requires culture changes, new processes, and people changing how they organize their work. Anticipate one to two years for this.

When implementing Critical Chain just failed, then do you want to have the same uphill battle again? Is that what you want?

Project Pipeline App

Instead of complex planning software, a simple project pipeline app is sufficient.

Bottleneck Analisis

Repairing a failed Critical Chain implementation starts with performing a bottleneck analysis. Because the bottlenecks will help to find the pipelines (they already exist, you only need to manage them). Collecting the data you need for this analysis takes 10-30 minutes per project and the bottleneck analysis is straightforward and can be done in half an hour.

Then there is a part you need my helps with: configuring the project pipeline app. This brings you beyond the point where implementations tend to fail and you’ve repaired your implementation.

And you are ready to go this time. With a little help, you can do this yourself!

Free Download

To help you to learn how to repair a failed Critical Chain implementation, I’ve written a 50-page book you can download for free.

About the content: You learn this (proven) strategy, plan of action to start right away, core principles, and tooling. You can use it to repair practically any failed CCPM implementation, and start delivering on the promise of Critical Chain Project Management in a matter of days or weeks.