01 · Purpose and boundaries
Purpose and boundaries
Theory of Constraints focuses improvement on the constraint that limits a system's progress toward its goal. In a warehouse the goal may include reliable shipment throughput and financial contribution, subject to safety and quality requirements. A resource with high utilization is not automatically the system constraint; its capacity must be considered relative to demand, routing, and the effect on completed customer work.
Distinguish throughput from local activity. In TOC financial terminology, throughput is the rate of generating money through sales, commonly sales revenue less truly variable costs. A warehouse may use shipped orders as an operational proxy, but that proxy is not the same financial quantity. Inventory and operating expense provide additional perspectives. Improving a nonconstraint can increase work in process without increasing shipments.
02 · How the method works
How the method works
Identify the constraint using queues, starvation patterns, actual effective capacity, and customer completion. It may be equipment, skills, a policy, a supplier, or market demand. Verify that changing its capacity or availability changes the system outcome.
Exploit the constraint: use existing capability better. Prevent avoidable idle time, feed it ready and acceptable work, sequence jobs intelligently, and move suitable preparatory work elsewhere. This is not permission to skip breaks, maintenance, safety, or necessary quality checks. Subordinate other activities to that decision. Upstream release and priorities should support the constraint rather than flood it; downstream resources must be available to carry away completed work.
Elevate the constraint if exploitation and subordination are insufficient. Add capability, redesign work, develop skills, or invest where the evidence supports it. Then repeat the cycle. A constraint can move before an investment is made, so reassess after every material change. Do not let yesterday's rules become today's limiting policy.
03 · Worked logistics example
Worked logistics example
Fictional Meridian Distribution has demand for 420 export orders daily. Picking can complete 500, export verification 360, and loading 450. All figures represent effective daily capacity for the same order mix and staffed period. A growing verification queue and unused loading capacity suggest export verification is the constraint.
Observation finds 40 minutes daily spent requesting missing documents and 20 minutes searching tariff references. Preparing complete document packs upstream recovers 60 minutes. At six verified orders per ten minutes, this adds 36 orders, raising verification to 396. Picking releases only work with complete documentation and protects a small ready queue ahead of verification. It does not pursue its own 500-order utilization target.
Demand still exceeds 396. A trained cross-functional colleague adds 30 orders of daily verification capacity at peak times, taking it to 426. The system can now meet 420 orders under these conditions; loading at 450 has enough capacity. If demand rises to 470, verification at 426 remains the first capacity concern, rather than loading automatically becoming the next constraint.
04 · Interpretation and decisions
Interpretation and decisions
The 36-order gain from recovering time is a capacity estimate. Actual shipment improvement depends on demand, order readiness, and downstream availability. Track completed exports, lead time, constraint idle reasons, and late orders. If shipped orders fail to rise, investigate another limiting factor or a flawed capacity estimate.
Subordination may lower picker utilization. This is reasonable if it reduces queues without harming output. Do not judge workers solely on local utilization after deliberately changing release rules. For product mixes with different constraint time and contribution, compare contribution per constraint minute where applicable, while respecting customer commitments and strategic priorities. The result should guide system decisions, not automatically reject a customer.
05 · Common misapplications
Common misapplications
A large queue may reflect a temporary outage rather than the enduring constraint. An empty queue may hide a demand shortage or excessive upstream filtering. Avoid declaring a bottleneck from a single average cycle time without availability, mix, and routing information.
Elevating first is another common error: buying capacity before protecting existing capability can be expensive and ineffective. Overproducing at nonconstraints increases inventory and makes priorities harder to see. Finally, TOC is not a justification for exposing people to unsafe loads or reducing necessary maintenance. The system goal includes the constraints and conditions under which performance is acceptable.
06 · Advanced adaptation
Advanced adaptation
Use a drum-buffer-rope design where appropriate. The constraint's workable schedule sets the drum, a time or material buffer protects it from variability, and the rope controls upstream release. Size the buffer from observed disruptions and service needs, and track which causes consume it.
For shifting bottlenecks, analyze demand classes and time horizons separately rather than forcing one permanent answer. A morning loading window can be the constraint even when daily aggregate capacity looks adequate. Policy constraints, such as releasing exports before documents exist, may dominate physical capacity. After the constraint changes, deliberately review measures, priorities, staffing, and release rules to prevent inertia.
07 · Implementing and sustaining the change
Implementing and sustaining the change
Introduce theory of constraints within a clearly named operating boundary. Identify the product family, shift, equipment, and handoffs affected; record what happens immediately before and after that boundary. A change that improves one task while exporting its delay to another department has not established an improvement. Agree who can stop the trial, who handles exceptions, and which customer commitment takes priority when the normal rule cannot be followed.
Establish a baseline from actual work rather than a single demonstration. Include normal variation in order mix, replenishment timing, staffing, and workload. Keep the denominator visible: minutes per order, defects per shipment, or completed lines per available hour answer different questions. Record the workload and conditions alongside each observation so that a quiet trial period cannot masquerade as better performance. Observe the process with the people who do it; their explanation of interruptions often changes the proposed design.
Start with a reversible pilot large enough to expose handoff problems. Explain the expected mechanism before launch: which action changes, which delay or failure it removes, and which result should respond. Train all affected shifts and support roles using the same operating definition. During the pilot, capture exceptions as information about the design. Do not conceal them through unofficial stock, unrecorded overtime, or a specialist who quietly repairs every failure.
Review customer service, safety, quality, work content, and inventory together. A faster average with more severe late orders may be unacceptable; a lower inventory level with repeated emergency deliveries may have displaced the cost. Investigate variation before declaring success. If the expected mechanism does not appear, revise the design or return to the baseline rather than defending the idea. A promising observation is a reason to test more conditions, not proof that every operating context will behave identically.
After a successful trial, make the new rule part of daily work. Give an accountable owner responsibility for the operating standard, change control, training, and periodic review. Specify the abnormal condition that requires escalation and the person who responds. Check whether the improvement remains effective when a trained colleague is absent or demand changes. Sustain the mechanism through routine management and learning; documentation is useful only when it describes the process people actually follow.
Connections
Related methods and phase use
Placed under Improve because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.