Generated by GPT-5-mini| Theory of Constraints | |
|---|---|
| Name | Theory of Constraints |
| Caption | Eliyahu M. Goldratt |
| Introduced | 1984 |
| Founder | Eliyahu M. Goldratt |
| Field | Operations management |
| Notable works | The Goal |
Theory of Constraints is a management approach developed to identify the most limiting factor impeding an organization from achieving a goal and to systematically eliminate that constraint to improve performance. Originating in operations and production, it has been applied in manufacturing, project management, healthcare, and services, influencing practitioners associated with major firms, universities, and consultancies.
The approach was introduced by Eliyahu M. Goldratt and promulgated through works associated with organizations such as the North River Press and consultants influenced by the Goldratt Institute. It gained attention alongside movements led by figures at Toyota Motor Corporation, General Electric, Procter & Gamble, Ford Motor Company, and General Motors that sought efficiency breakthroughs. The methodology intersects historically with developments connected to Frederick Winslow Taylor, Henry Ford, W. Edwards Deming, Joseph M. Juran, Armand V. Feigenbaum, Peter Drucker, Michael Porter, and organizations like MIT and Stanford University where research on constraints and throughput was pursued. Early case studies involved plants associated with IBM, Boeing, Lockheed Martin, Siemens, and Honeywell, and the approach spread through practitioners in consultancies such as McKinsey & Company and Boston Consulting Group.
Core concepts articulate the focus on throughput, inventory, and operating expense as financial measures to be balanced when addressing a single system constraint. The notion of a bottleneck mirrors analyses in studies by Henry Gantt, Frank and Lillian Gilbreth, and later queueing theory work by Agner Krarup Erlang and Leonard Kleinrock. The idea of elevating a constraint is discussed in contexts similar to capacity planning used by Eliyahu Goldratt contemporaries at University of Michigan and practitioners in Fordism-era production. Associated constructs include the buffer concept comparable to buffer stock policies in analyses from Adam Smith-influenced supply debates and inventory models explored by William Edwards Deming-linked circles. The distinction between constraint, synchronizing resource, and non-constraint parallels systems thinking advanced by Donella Meadows, Jay W. Forrester, and research groups at Carnegie Mellon University.
The formal sequence—identify, exploit, subordinate, elevate, and repeat—was formulated to create iterative improvement cycles. These steps resemble improvement cycles used by W. Edwards Deming and are implemented in environments overseen by executives like those at Samsung, Intel, 3M, ABB Group, and Philips. Identification of the constraint often uses tools akin to value-stream mapping promoted by James P. Womack and Daniel T. Jones, or line-balancing techniques employed by engineers at Rolls-Royce plc and General Dynamics. Exploitation and subordination involve operational redesigns similar to cellular manufacturing pioneered in Nissan and workflow synchronization practices used at UPS and FedEx. Elevation examples include capital projects comparable to expansions by ArcelorMittal and ExxonMobil, while repeating the process aligns with continuous improvement traditions at Nestlé, Unilever, and PepsiCo.
Applications span manufacturing, project management, sales, distribution, healthcare, and software development. In project management, the approach informed Critical Chain Project Management used on projects at NASA, European Space Agency, Bechtel, and Fluor Corporation. Healthcare pilots occurred in institutions like Mayo Clinic, Johns Hopkins Hospital, and Cleveland Clinic to reduce patient wait times and resource idle time. Supply chain programs implemented constraint-focused scheduling at Walmart, Target Corporation, Tesco, Carrefour, and logistics operations at DHL. Software teams adapted the approach in agile environments alongside frameworks used by Atlassian, Microsoft, Google, and Amazon to resolve development bottlenecks. Training and dissemination were carried out by institutions and consultancies such as Goldratt Consulting, Accenture, KPMG, Deloitte, and management programs at Harvard Business School and INSEAD.
Critics note potential oversimplification when a single constraint framework is applied to complex socio-technical systems and point to empirical debates in literature from scholars at London School of Economics, Oxford University, Columbia University, Yale University, and University of Chicago. Economists and operations researchers from Carnegie Mellon University and Georgia Institute of Technology have contrasted constraint-focused interventions with optimization models used by practitioners at Bell Labs and algorithmic scheduling research at MIT Lincoln Laboratory. Limitations include difficulties when multiple interacting constraints exist as seen in analyses of global supply shocks studied by International Monetary Fund and World Bank teams, and when cultural or regulatory factors in organizations like World Health Organization-affiliated hospitals impede simple elevation strategies. Measurement debates involve contrasting throughput accounting with traditional accounting methods taught at London Business School and Columbia Business School.
The approach relates to lean manufacturing movements associated with Taiichi Ohno, Shigeo Shingo, and the Toyota Production System while differing in emphasis from total quality management advocated by W. Edwards Deming and strategic positioning theories from Michael Porter. It complements agile methods advanced by authors like Kent Beck and Mike Cohn and shares systems thinking roots with works by Russell L. Ackoff and Peter Senge. Its project adaptations intersect with critical path techniques developed by James E. Kelley Jr. and Morgan R. Walker and portfolio practices used in organizations such as BlackRock and Goldman Sachs.
Category:Management theories