Critical Chain (Paperback)

In CRITICAL CHAIN, Goldratt builds upon the teachings found in THE GOAL. He quickly describes of constructs of TOC, while spending more time addressing some specific phenomenon of project management versus process management. This is where the "Aha"s come into play.

Goldratt's characters debate and learn why projects often run overdue and over budget, or finish with less completed than originally specified. The characters debate critical path vs. non-critical path tasks, early vs. late start, resource conflicts, safety buffers in each task, negotiating with subcontractors and suppliers, as well as the erroneous progress accounting/measurement techniques that give everyone a false sense of progress toward completion.

Each of these topics were useful in challenging the conventional wisdom of project management. Each presented some new techniques for managing projects more aggressively. In my job, I indirectly manage a large number of construction project managers, and this was useful in understanding some of the reasons we struggle to deliver on time and on budget.

For those of you looking for the same enlightenment that you probably derived from THE GOAL, you will be mildly disappointed. For those of you who have not yet read THE GOAL, I highly recommend reading it, because it will provide the foundation material (TOC) in much more depth and clarity.

For me, TOC completes the loop of operational concepts that I have pondered over my career, namely how to improve processes and improve overall organizational productivity, while eliminating "fire fighting" and bottlenecks in production. CRITICAL CHAIN furthers the progress of this thinking relative to a project vs. a process environment.

Recommended reading approach: read once through and then revisit the chapters where our hero is in class and also the one where he is enjoying the TOC lecture (ie. on the second pass, ignore the fictional dialog regarding our hero's fight for tenure). Read SLOWLY at this point, and have a notepad handy to apply the ideas to your world. Think! I learned a heck of alot more the second time through.

Having now read two of Mr. Goldratt's books, it appears that to him every management issue is a scheduling and coordination problem. While that's true, product development management of difficult tasks is also sensitive to many other things like getting competent resources, having the right amount of input from each function early in the process, and developing the ability to produce the finished product efficiently and effectively. Those other issues are essentially untouched in this book.

Think of this book as applying the system coordination and optimization concepts of Mr. Goldratt's famous novel, The Goal, to project management.

If you have already read The Goal, this book will be much easier to understand than if you have not. Although many of the same concepts are explained here as in The Goal, the explanations in this book are not nearly as thorough and clear. Also, the plot and plot line in this book will probably not be as enjoyable to you as The Goal. I rated the book down two stars for these kinds of weaknesses.

If you have read The Goal, Mr. Goldratt basically substitutes scheduling safety margins for work-in-progress inventory, and then applies the same debottlenecking concepts as in The Goal.

If you have not read The Goal, Mr. Goldratt's argument is that schedules are put together with too much slack. Everyone wants to be almost sure they can meet a deadline. The deadkube date they pick usually relates to the most they can get away with. Usually, that much time is not needed and people start late. If they end early, they never tell anyone. So any delay puts the whole project back because there is no project scheduling slack. With many tasks going on simultaneously, often none of them get done well.

The solution is to cut back on each individual schedule in favor of having all of the slack managed for the whole project, and communicating frequently about when the work really will be done so the next step can be ready to take up the baton. Then focus all measurements on project completion, rather than task completion. Give priority to whatever can hold the whole project back. Add resources there, too, if possible. In doing this, focus on both activities and resources as potential bottlenecks.

The book also has some good sections on how to negotiate with external suppliers to improve performance, and how to think about the tradeoffs between speed and cost as a supplier and as a purchaser of supplies and services.

Without changes in top management policies, most project managers will not be allowed to use all of these principles. So be sure to share this book upward, as well as sideways, and downward in the organization. If you are in a small company, it will be much easier to do.

After you have finished reading this book, I suggest that you look at the last 20 projects that your organization has done. What was done well? What was not? Which of these issues can be helped by Mr. Goldratt's ideas? Which cannot? For these latter, I suggest you look for best practices and imagine what perfection could look like to design a simple, but effective, alternative with better communications. The new book, It's Not the BIG etc., may be helpful to you in this regard.

May you continuously improve your effectiveness in project management!