
Why TOC for Projects is more difficult and what to do about it
This book is about applying TOC to project management. After reading this book I understood why TOC for project management is not as straight forward as it might first appear. Not only are projects not repeatable like production assembly lines buts in a multi-project environment you need to take shared resources into account. This is even more difficult when the managers for each project are different people. Lessons learned are:
- Estimates should be “In X days with 50% chance of completion”
- Cut estimates in 2 or 3 if suspect that tasks have padding
- All the padding should go for the project but less than sum of padding
- Add time buffers (at no cost) when paths merge with critical path
- If a resource is shared between projects then it may be a bottleneck
- Resource bottlenecks should be treated as such: identify, exploit, subordinate, elevate...
- No due dates (at least not until the work begins) so as not to encourage the “student syndrome”
- Prioritize according to amount of remaining buffer when conflict occurs
Of all the business novels by Eli Goldratt, I think that this is the one that I have learned the most from. As with all his novels, it’s easy and fun to read with the added benefit that you will have learnt to better manage your projects. A must.








