Management Dilemmas - Part Two

I've made a very little amount of headway on the book I'm reading now, Management Dilemmas: The Theory of Constraints Approach to Problem Identification and Solutions. Time has been tight with work, school, and family but I'm trudging through slowly.


The case studies continued in the chapters I've read since the first post about this book. One concerns a situation with a purchasing manager who is trying to deal with a complete product change that has an uncertain implementation date. There are constraints around how much can/should be ordered, and the premiums required for smaller batches. The problem here is to not fall short of materials for production of the old product, and at the same time not have a huge amount of waste after the change, because all the existing materials will be obsolete when the change occurs. Upper management is incenting conflicting actions, and traditionally the purchasing manager has to try and 'balance' them. I like the TOC approach.

Another chapter goes into a scenario where a company founder split his company into profit centers in order to incent his managers to perform. The case study analyzes the situation and some of the resulting problems that have come to light over a period of two years. The plants have fixed transfer costs built into their outputs when they are provided to the other plants, and again this is a question of whether or not the right things are being incented, in the right way. The TOC solution presented resolves the conflict and acheives the founder's original vision.

I will do another post on this book when I've completed it. Cheers!

Please leave comments about this post!

Management Dilemmas - Part One

I'm about half way through the book I'm reading now, Management Dilemmas: The Theory of Constraints Approach to Problem Identification and Solutions. It was difficult to get into it at first, perhaps because the author made an appropriate introductory section going into the conceptual aspects of the TOC thinking processes, the Throughput world versus the Cost world, etc. which I've already read extensively about. Overall, good content in the beginning but a little slow and university textbook-like reading.

Then it gets good.

The author continues with several case studies to highlight various management problems in different industries, and very different causes and circumstances. In the first section a case study is used too, but plays a minor role in the content. These later chapters dive into the scenarios presented and I'm finding myself quite engaged with them. It's as if you are playing the part of a consultant, and need to correctly diagnose the core problems that are causing the evident symptoms. It's like detective work and I'm working through my own TOC diagrams to practice after I read the case, and see if I come up with the answer the author does. My diagnoses have been similar thus far.

The case studies so far have included problems in a hotel, office supply company, a high-end desk lamp manufacturer, the Army's Central Communications Laboratory, and a hospital. It's been great for showing examples of using TOC to solve problems in this eclectic mix of situations, and giving me practice at the TOC concepts. I hope as I internalize more about TOC, CCPM, and EVM I will be better suited to figure out the CCEVM solution.

I will do another post on this book when I've completed it. Cheers!

Please leave comments about this post!

CCEVM Evaporating Cloud Diagram

A Goldratt technique came in handy to map out where I see the conflict between CCPM and EVM that I referred to in my last post. Please excuse it's sloppiness, I will try to make a cleaner computer-generated version later on, but I think I may be refining this later on anyway.

I've never seen an evaporating cloud with more than 1 requirement for each of the prerequisites, but I found it necessary to have a requirement which stems from both CCPM and EVM. The conflict indicated between employing Critical Chain and EVM stems from different behaviors being driven by the two. Critical Chain supports behaviors that focus on efficiency with tasks on the Critical Chain , thus improving the outcome of the project. EVM supports behaviors that make it appear overall cost efficiencies are good, even if those efficiencies are being achieved on tasks that aren't critical to the completion time of the project. Project managers might decide to work on some easier non-critical tasks if their EVM is going to fall short and get a short-term EVM win, but if that happens it throws EVM's predictive power regarding schedule out the window.



















The resulting direction from this is to modify the budgeting and cost control tools in the Critical Chain body of knowledge. It needs to use buffer management methods for cost, to control the project that is implemented in such a way to make it compatible with existing EVM metrics. There would be a single project cost buffer which is already part of the CCBOK. Cost buffer management would be used for controlling project costs, in addition to an accurate EVM translation based on cost buffer utilization compared to planned utilization.

Note: from a cost perspective, all tasks are on the Cost Critical Chain (CCC) because cost over run in any task will make the project over budget unless other tasks have under runs. It makes no difference if they are on the schedule's critical chain. That's why there's only 1 cost buffer, the project cost buffer.

Please leave comments about this post!