Improving Business Performance- Discussion 9 Response

Colleague 1

Femi Owoeye

Hello everyone.

Chapters 17 through 28 of The Goal vividly demonstrate the effectiveness of applying systems thinking, as Alex Rogo's team implements the Theory of Constraints (TOC) to revolutionize the Bearington plant. This section reveals how to manage constraints and why defying traditional business rules is essential for optimizing an entire system. The novel's accessible format powerfully illustrates how these abstract concepts translate into tangible, real-world improvements, reinforcing their direct relevance to effective business management.

The techniques employed by the team prove successful precisely because they fundamentally shift focus from isolated efficiencies to the holistic flow of the system, challenging conventional management wisdom. Goldratt and Cox highlight the crucial need for quality control before the bottleneck, explaining, "Make sure the bottleneck works only on good parts by weeding out the ones that are defective. If you scrap a part before it reaches the bottleneck, all you have lost is a scrapped part. But suppose you scrap the part after it's passed the bottleneck. In that case, you have lost time that cannot be recovered" (Goldratt & Cox, 2014, p. 67). This "breaks the rule" of inspecting all parts equally, prioritizing pre-bottleneck quality to prevent the most constrained resource from wasting precious time on defects, which align with Noga, Pant & Shaw (2011) discussion on how "fixes that fail" often miss the critical point of intervention, thereby safeguarding the system's throughput.

The practical application of exploiting the bottleneck and subordinating non-bottleneck resources is detailed through the "red tag" system: "A red marker means the work attached to it has priority. The red tags go on any materials needing to be processed by a bottleneck. When a batch of parts with that color marker arrives at your workstation, you are to work on them right away" (Goldratt & Cox, 2014, p. 75). This "breaks the rule" of typical first-in, first-out (FIFO) or local departmental scheduling. By visually mandating immediate priority for bottleneck-bound work, it ensures the constraint is continuously supplied, disciplined subordination, which is a key reason why the team's techniques begin to work so effectively (Stroh, 2014), resulting in the team's improved throughput.

Finally, strategies for elevating the bottleneck's capacity are outlined by Jonah: "Then make the bottlenecks work only on what will contribute to throughput today… not nine months from now," says Jonah. "That's one way to increase the capacity of the bottlenecks. The other way you increase bottleneck capacity is to take some of the load off the bottlenecks and give it to non-bottlenecks" (Goldratt & Cox, 2014, p. 68). This quote challenges the conventional focus on rigid, long-term scheduling. It advocates "breaking the rule" of producing based solely on distant forecasts, instead directing the bottleneck to focus on immediate throughput-contributing orders. This flexibility in scheduling and strategic load-balancing ensures the plant's current output is maximized and responsive to market demand, optimizing the system's revenue generation. This aligns with Hernández et al.'s (2017) highlight of systems thinking for strategic improvement.

If I had only known this while managing a software development team, our approach to releasing new features would have been very different. We prioritized individual developer "utilization," ensuring everyone was coding, but our constraint was the quality assurance (QA) and deployment pipeline. This created a backlog of untested features ("inventory") while developers pushed more code. I would have strategically slowed upstream coding if I understood the principle of prioritizing the bottleneck and ensuring it only processed "good parts" (error-free code submitted for QA). This "breaking of rules" for individual productivity would have ensured the QA/deployment teams were never overwhelmed, dramatically increasing the throughput of thoroughly tested and deployed features, delivering value faster and more predictably.

References

Goldratt, E. & Cox, J. (2014). The goal: A process of ongoing improvement (3rd ed.) [VitalSource Bookshelf version]. North River Press. vbk://9780884272755.

Hernández, A., Ruano, A. L., Marchal, B., San Sebastián, M., & Flores, W. (2017). Engaging with complexity to improve the health of indigenous people: A call for the use of systems thinking to tackle health inequity. International Journal for Equity in Health, 16(1), 26–31. https://doi.org/10.1186/s12939-017-0521-2Links to an external site.

Noga, T., Pant, L. W., & Shaw, L. (2011). Recalibrating ethical dilemmas using the "fixes that fail" archetype. Journal of Business Ethics Education, 8(1), 115–118.

Stroh, D. P. (2014). Systems thinking for social change: Making an explicit choice. Reflections, 14(3), 35–42.

Colleague 2

Angela Eaker

In The Goal, Eliyahu M. Goldratt (1984) presents a transformative approach to business management through the Theory of Constraints (TOC), particularly evident in the middle chapters of the book (pp. 124–236). One of the most compelling insights during this section is the structured five-step process for improving system performance: “Step 1. Identify the system’s bottlenecks… Step 2. Decide how to exploit the bottlenecks… Step 3. Subordinate everything else to the above decision… Step 4. Elevate the system’s bottlenecks… Step 5. If, in a previous step, a bottleneck has been broken go back to step 1” (Goldratt, 1984, pp. 127–130). This framework is revolutionary because it shifts the focus from maximizing efficiency in every department to optimizing the entire system. The team’s success in the novel stems from applying these steps, even when it means breaking traditional rules—such as skipping lunch breaks for bottleneck machines or using outdated equipment to relieve production pressure.

Another critical passage that underscores the importance of systems thinking is: “The capacity of the plant is equal to the capacity of its bottlenecks” (Goldratt, 1984, p. 135). This statement challenges the conventional wisdom that improving any part of the system will improve the whole. Instead, Goldratt emphasizes that only improvements at the bottleneck will increase overall throughput. This realization leads the team to focus their efforts where it matters most, rather than spreading resources thinly across all operations. Their ability to prioritize bottlenecks results in significant gains in productivity and delivery performance.

A third essential concept is the distinction between activation and utilization: “Utilizing a resource means making use of the resource in a way that moves the system toward the goal. Activating a resource is like pressing the ON switch… it runs whether or not there is any benefit” (Goldratt, 1984, p. 197). This insight is particularly relevant in modern business environments where busy work is often mistaken for productivity. The team in The Goal learns that keeping machines or people busy does not necessarily contribute to the organization’s goal. Instead, they begin to measure success by how effectively each action contributes to throughput, inventory reduction, and operational expense control.

Reflecting on these lessons, I find myself thinking: “If I had only known this back when I was coordinating adult education programs with limited instructors and high enrollment, I would have focused on identifying and managing the real constraints—like classroom space and instructor availability—instead of trying to optimize every part of the process equally. That would have allowed us to serve more students effectively without overwhelming the system.” Goldratt’s work remains a powerful reminder that sometimes breaking the rules of traditional management is the most effective path to achieving meaningful results.

References
Goldratt, E. M. (1984). The Goal: A Process of Ongoing Improvement. North River Press.