# The Theory of Constraints Atlas > A pattern-language reference to the Theory of Constraints — every named tool, concept, and canonical case, for TOCICO candidates and working practitioners. This is the The Theory of Constraints Atlas, curated by Simon M. White. It collects 115 articles organized as a pattern language across 11 sections. Updated 2026-10-20. Canonical URL: https://tocatlas.com/. Append `.md` to any article URL below for a clean Markdown copy (e.g. https://tocatlas.com/.md). ## Introduction - [What's New](https://tocatlas.com/whats-new): A running record of recent additions and revisions to the book, newest first, with per-checkpoint coverage metrics. - [Article Map](https://tocatlas.com/article-map): An interactive graph of every pattern, concept, antipattern, and case in the book and how they connect through their typed Related Articles links. - [About the Curator](https://tocatlas.com/about-curator): Simon M. White, the TOC Atlas’s first curator. (draft — not yet reviewed) - [Learning Tracks](https://tocatlas.com/learning-tracks): Six study paths toward the TOCICO certification exams — a shared Common Trunk plus a colored path for each certification, each ordered the way its exam is scoped. ## Foundations - [System](https://tocatlas.com/system): A collection of interdependent components whose owners set its purpose and against whose goal every TOC tool is calibrated. (draft — not yet reviewed) - [Constraint](https://tocatlas.com/constraint): The single element whose limit caps what the whole system can achieve, distinct from a bottleneck and the term every TOC tool is calibrated against. (draft — not yet reviewed) - [Throughput](https://tocatlas.com/throughput): The rate at which a system generates money through sales, not through production; an item made but unsold contributes nothing. (draft — not yet reviewed) - [Inventory (TOC Definition)](https://tocatlas.com/inventory): All the money a system has invested in things it intends to sell, counted with no labor or overhead absorbed into the figure. (draft — not yet reviewed) - [Operating Expense (TOC Definition)](https://tocatlas.com/operating-expense): All the money a system spends converting inventory into throughput, reported at the system level and never allocated to individual products. (draft — not yet reviewed) - [The Goal (concept)](https://tocatlas.com/goal): The purpose for which a system was created, stated precisely enough that any improvement effort can be judged for or against it. (draft — not yet reviewed) - [Five Focusing Steps](https://tocatlas.com/five-focusing-steps): The five-step cycle that turns a stated goal and an identified constraint into an unending discipline of system improvement. (draft — not yet reviewed) - [Process of Ongoing Improvement (POOGI)](https://tocatlas.com/poogi): The discipline of repeatedly identifying and elevating the current constraint so goal-unit output keeps rising across periods; a property of the implementation, not a finished project. (draft — not yet reviewed) - [Constraint Type Identification](https://tocatlas.com/constraint-type-identification): Name a constraint's type before acting on it, because whether it is physical, policy, paradigm, or market determines which intervention applies. (draft — not yet reviewed) - [Subordination](https://tocatlas.com/subordination): Aligning every non-constraint resource and policy to the rate the constraint can consume; the third focusing step, and the one practitioners most often skip. (draft — not yet reviewed) - [Exploitation Without Elevation](https://tocatlas.com/exploitation-without-elevation): Wring the most throughput from the constraint as it stands before spending any money, headcount, or calendar to expand its capacity. (draft — not yet reviewed) - [Policy Constraint](https://tocatlas.com/policy-constraint): A rule, measurement, procedure, or mandate that holds a system below the throughput its physical configuration could deliver; a constraint that costs nothing to change. (draft — not yet reviewed) - [Strategic Constraint](https://tocatlas.com/strategic-constraint): The resource, market, or factor that leadership deliberately chooses to make and hold the system's binding limit over the long run, distinct from whichever current constraint the Five Focusing Steps happen to target now. (draft — not yet reviewed) - [Local Optimization](https://tocatlas.com/local-optimization): Improving individual parts of a system in ways that do not improve, and often actively harm, the performance of the whole. (draft — not yet reviewed) - [Improving Non-Constraints](https://tocatlas.com/improving-non-constraints): Committing capital, time, or attention to a resource that is not the constraint, then treating the resulting local gain as if it were a system gain. (draft — not yet reviewed) - [Breaking the Wrong Constraint](https://tocatlas.com/breaking-wrong-constraint): Elevating a resource that only looks like the constraint while the true constraint stays unchanged, so the expense is real but the throughput never moves. (draft — not yet reviewed) - [Antipatterns Index](https://tocatlas.com/antipatterns-index): A single index of the recurring traps TOC practitioners need to recognize, grouped by the section where each trap corrupts the practice. (draft — not yet reviewed) ## Performance Measures - [Throughput Accounting](https://tocatlas.com/throughput-accounting): A management-accounting frame that judges every action by its effect on throughput, inventory, and operating expense, and refuses to allocate fixed costs to product units. (draft — not yet reviewed) - [Cost-World vs. Throughput-World Thinking](https://tocatlas.com/cost-throughput-thinking): The named paradigm conflict between cost accounting's view of a system as optimizable parts and TOC's view of a chain set by one constraint. (draft — not yet reviewed) - [Product Mix Decision Under Constraints](https://tocatlas.com/product-mix-decision): Rank products by throughput per unit of constraint capacity, fill the scarce capacity in that order, then verify the full throughput, inventory, and operating-expense effect. (draft — not yet reviewed) - [Traditional Financial Measures and Their Dilemmas](https://tocatlas.com/financial-measure-dilemmas): The inherited measures — unit cost, gross margin, ROI, utilization, inventory, due-date performance, budget and purchase-price variance — whose local targets conflict in constrained systems. (draft — not yet reviewed) - [Continuous Improvement Auditing](https://tocatlas.com/continuous-improvement-auditing): Audit every TOC change against its measured system effect, then decide whether to continue, correct, stop, or return to the constraint. (draft — not yet reviewed) - [Throughput Dollar-Days and Inventory Dollar-Days](https://tocatlas.com/tdd-idd-measures): Operational dollar-day measures that turn late commitments and unnecessary early inventory into comparable time-weighted signals. (draft — not yet reviewed) - [Throughput-Accounting Decision Cases](https://tocatlas.com/ta-decision-cases): A Throughput Accounting pattern for make-or-buy, capital, outsourcing, and price-floor decisions using the total change in throughput, investment, and operating expense. (draft — not yet reviewed) - [Throughput Economics](https://tocatlas.com/throughput-economics): The two-scenario decision method that extends Throughput Accounting to larger moves under uncertainty, reporting a conservative-to-optimistic range of net-profit impact instead of a single number. (draft — not yet reviewed) - [Holistic ToC Implementation](https://tocatlas.com/holistic-toc-implementation): Roll out TOC as a synchronized organization-wide change rather than a string of local successes the old measures can later erase. (draft — not yet reviewed) - [Cost-World Thinking](https://tocatlas.com/cost-world-thinking): Judging every operating decision by per-unit or local cost in a constrained system, where a cost ranking cannot register the throughput the constraint sets. (draft — not yet reviewed) - [Efficiency Trap](https://tocatlas.com/efficiency-trap): Driving every resource toward high local utilization even though only constraint-protecting work can raise throughput; mistaking activation for utilization. (draft — not yet reviewed) ## Production and Operations - [The Four Concepts of Flow](https://tocatlas.com/four-concepts-flow): The four production principles Goldratt extracted from Ford and Ohno: improve flow as the primary objective, build a mechanism for when not to produce, abolish local efficiencies, and run a focusing process to balance flow. (draft — not yet reviewed) - [Drum-Buffer-Rope (DBR)](https://tocatlas.com/drum-buffer-rope): TOC's production method for make-to-order operations with an internal capacity constraint: schedule the constraint, protect it with a time buffer, release work only at its pace. (draft — not yet reviewed) - [Simplified Drum-Buffer-Rope (S-DBR)](https://tocatlas.com/s-dbr): TOC's production method for make-to-order operations constrained by market demand: quote a reliable due date, protect it with one production buffer, release one buffer ahead. (draft — not yet reviewed) - [Buffer Management](https://tocatlas.com/buffer-management): The execution discipline that turns a static time buffer into a live signal: read consumption by color zone, expedite the red, trace repeat reds to their cause. (draft — not yet reviewed) - [VATI Plant-Type Analysis](https://tocatlas.com/vati-plant-analysis): TOC's classification of plants by material-flow shape: V diverges, A converges, T explodes into end items, and I runs linear, guiding where DBR applies. (draft — not yet reviewed) - [Capacity-Constrained Resource (CCR)](https://tocatlas.com/ccr): A resource tight enough that the planning system must watch its load, protect its sequence, and hold slack so it does not become the constraint. (draft — not yet reviewed) - [Protective Capacity](https://tocatlas.com/protective-capacity): The non-constraint capacity reserve TOC keeps available so ordinary variation does not starve the constraint or break due-date commitments. (draft — not yet reviewed) - [Transfer Batch vs. Process Batch](https://tocatlas.com/transfer-process-batch): The batch-policy distinction that lets a resource process economically sized lots while downstream work starts on smaller transfers, cutting lead time without adding capacity. (draft — not yet reviewed) - [Constraint Buffer](https://tocatlas.com/constraint-buffer): A time reserve positioned immediately upstream of the constraint, sized to absorb upstream variability so the system never loses throughput the constraint cannot recover. (draft — not yet reviewed) - [Assembly Buffer](https://tocatlas.com/assembly-buffer): A time reserve at an assembly convergence point, used when non-constraint feed paths must arrive in time to meet parts that have flowed through the constraint. (draft — not yet reviewed) - [Shipping Buffer](https://tocatlas.com/shipping-buffer): A time reserve between the constraint's output and the customer-commitment point, sized to protect the quoted due date from variability after the constraint's work is done. (draft — not yet reviewed) - [Israeli Air Force F-4 Phantom Maintenance](https://tocatlas.com/iaf-f4-maintenance): Goldratt-lineage maintenance case used to teach exploit-before-elevate discipline, with its source trail treated cautiously. (draft — not yet reviewed) - [Mabe Mexico Manufacturing](https://tocatlas.com/mabe-mexico): A large Mexican appliance-maker's TOC production program, used in the field as a scale case for DBR, buffer visibility, and subordinated measurement. (draft — not yet reviewed) ## Supply Chain and Distribution - [Replenishment Pull](https://tocatlas.com/replenishment-pull): Restock each location from what was actually consumed, hold most protection at the highest useful aggregation point, and use buffer status to keep availability high. (draft — not yet reviewed) - [Buffer Aggregation in Distribution](https://tocatlas.com/buffer-aggregation): The statistical reason TOC distribution holds less total stock yet raises availability: demand varies less at an aggregation point than at the consumption points it serves. (draft — not yet reviewed) - [Distribute-to-Availability (DTA)](https://tocatlas.com/dta): Hold the bulk of finished-goods inventory at a central warehouse, let downstream links carry small buffers replenished daily from actual consumption, and sell the resulting availability-with-fewer-turns as an inventory-turns offer. (draft — not yet reviewed) - [Dynamic Buffer Management](https://tocatlas.com/dynamic-buffer-management): The feedback loop that resizes TOC stock-buffer targets from repeated red and green behavior instead of freezing availability around the first estimate. (draft — not yet reviewed) - [Actively Synchronized Replenishment (ASR)](https://tocatlas.com/actively-synchronized-replenishment): Place stock buffers at selected material and distribution points, replenish from actual demand, and use visible buffer priority so complex MRP-dependent chains protect flow without returning to forecast-push. (draft — not yet reviewed) - [Make-to-Stock vs. Make-to-Availability (MTS vs. MTA)](https://tocatlas.com/mts-mta): The distinction between producing stock against a forecast and committing to reliable availability for chosen repeat items, where buffer status and replenishment priority replace forecast-push. (draft — not yet reviewed) - [Cash Constraint and Cash Buffer](https://tocatlas.com/cash-constraint-buffer): The financial-constraint case where cash availability limits material supply, product mix, and survival time, managed through cash velocity and a protective cash buffer. (draft — not yet reviewed) - [Supply-Chain Collaboration](https://tocatlas.com/supply-chain-collaboration): Coordinate replenishment, buffer status, and constraint decisions across company boundaries so the chain protects customer availability instead of each link protecting its own local measures. (draft — not yet reviewed) - [DDMRP and TOC](https://tocatlas.com/ddmrp): The demand-driven materials-planning method that carries TOC replenishment and ASR logic into MRP-dependent supply chains, with strategic decoupling points, dynamic stock buffers, and execution priority based on actual demand. (draft — not yet reviewed) - [Procter & Gamble Distribution](https://tocatlas.com/pg-distribution): The field-cited Procter & Gamble distribution case, useful as a consumer-goods scale example for TOC replenishment and VMI-adjacent availability claims, with the source boundary kept explicit. (draft — not yet reviewed) ## Critical Chain Project Management - [Critical Chain](https://tocatlas.com/critical-chain): The longest sequence of dependent tasks and dependent resource assignments in a project, accounting for both precedence and resource contention; a project's constraint. (draft — not yet reviewed) - [Project Buffer](https://tocatlas.com/project-buffer): A single aggregated time reserve at the end of the critical chain, built from safety stripped out of its tasks, protecting the project's external commitment date. (draft — not yet reviewed) - [Feeding Buffer](https://tocatlas.com/feeding-buffer): A time reserve where a non-critical path joins the critical chain, protecting the chain's next start from variation on the feeding path. (draft — not yet reviewed) - [Resource Buffer](https://tocatlas.com/resource-buffer): A warning signal before a critical-chain task so the assigned resource drops other work and is ready when the chain needs it; an alert, not a reserve. (draft — not yet reviewed) - [Full Kitting](https://tocatlas.com/full-kitting): The release-readiness discipline that keeps project tasks, manufacturing orders, and service work from starting until the inputs needed to finish are available. (draft — not yet reviewed) - [Fever Chart](https://tocatlas.com/fever-chart): A Critical Chain control chart that compares project-buffer consumption with chain completion to distinguish expected variation from conditions that need recovery action. (draft — not yet reviewed) - [Student Syndrome](https://tocatlas.com/student-syndrome): Delaying the start of a task because its due date still looks distant, consuming the task's local safety before real work begins. (draft — not yet reviewed) - [Bad Multitasking](https://tocatlas.com/bad-multitasking): Switching a scarce resource among active tasks when the switching helps no project finish earlier, while the critical chain waits. (draft — not yet reviewed) - [Parkinson's Law in Projects](https://tocatlas.com/parkinsons-law): Work expanding to consume the time a padded task estimate allows, so local safety disappears before it can protect the project. (draft — not yet reviewed) - [Padding Without Aggregating](https://tocatlas.com/padding-without-aggregating): Adding safety to every task estimate instead of moving it into shared buffers, so the reserve is consumed task by task rather than protecting the project. (draft — not yet reviewed) - [Multi-Tasking Cascade](https://tocatlas.com/multitasking-cascade): The CCPM antipattern in which too many active projects force scarce resources to switch among tasks, so each delay creates more switching and the whole portfolio slows. (draft — not yet reviewed) - [Pipeline Management and Pipeline Planning](https://tocatlas.com/pipeline-management-planning): The multi-project CCPM discipline that chooses the portfolio drum, staggers releases, and resets priorities as conditions change. (draft — not yet reviewed) - [Agile CCPM](https://tocatlas.com/agile-ccpm): Ujigawa and Updegrove's software-specific CCPM variant: keep the critical-chain commitment discipline while using relative size, velocity, and a scope buffer where absolute task estimates break down. (draft — not yet reviewed) - [Boeing CCPM Implementation](https://tocatlas.com/boeing-ccpm): Boeing Integrated Defense Systems' award-recognized Critical Chain adoption, useful for the scale claim but thinner in public evidence than many practitioners imply. (draft — not yet reviewed) ## Thinking Processes - [Goal Tree (IO Map)](https://tocatlas.com/goal-tree): A necessity-logic map of the goal, critical success factors, and necessary conditions that gives TOC analysis its system-level target. (draft — not yet reviewed) - [Current Reality Tree (CRT)](https://tocatlas.com/current-reality-tree): A cause-and-effect map connecting a system's undesirable effects to the few core problems behind most of them; the Thinking Process tool for what to change. (draft — not yet reviewed) - [Core Problem](https://tocatlas.com/core-problem): The convergence point in current reality that accounts for the most significant UDEs: the target a Current Reality Tree identifies before the rest of the Thinking Processes design a change. (draft — not yet reviewed) - [Evaporating Cloud (Conflict Resolution Diagram)](https://tocatlas.com/evaporating-cloud): A five-box necessity-logic diagram that turns an apparent conflict into testable assumptions, then finds the injection that lets both requirements be met without compromise. (draft — not yet reviewed) - [Future Reality Tree (FRT)](https://tocatlas.com/future-reality-tree): A sufficiency-logic map that tests whether a proposed injection will replace today's undesirable effects with desirable ones, without creating worse side effects. (draft — not yet reviewed) - [Negative Branch Reservation (NBR)](https://tocatlas.com/negative-branch-reservation): A sufficiency-logic test for predicted undesirable effects of an injection, used to trim a proposed change before implementation creates new UDEs. (draft — not yet reviewed) - [Daily Management with TOC](https://tocatlas.com/daily-management-toc): A compact Thinking Processes sequence for turning daily managerial problems into short-term repairs that also support longer-term system improvement. (draft — not yet reviewed) - [Prerequisite Tree (PRT)](https://tocatlas.com/prerequisite-tree): A necessity-logic map that turns a tested injection or ambitious target into the intermediate objectives required to overcome the obstacles blocking implementation. (draft — not yet reviewed) - [Transition Tree (TT)](https://tocatlas.com/transition-tree): A sufficiency-logic action map that sequences the steps from the present condition to a chosen objective, with the need, condition, and rationale for each step visible. (draft — not yet reviewed) - [Strategy and Tactics Tree (S&T Tree)](https://tocatlas.com/strategy-tactics-tree): A hierarchical Thinking Process tool that connects an organization's strategy to the tactics, assumptions, sequence, and lower-level changes required to achieve it. (draft — not yet reviewed) - [Conditional Reality Tree](https://tocatlas.com/conditional-reality-tree): A sufficiency-logic Thinking Process tree that maps expected future UDEs under named starting conditions, especially when inaction or external change would make today's reality worse. (draft — not yet reviewed) - [Necessary Cause (Necessity Logic)](https://tocatlas.com/necessary-cause): The logic of preconditions — 'to achieve A, we must have B' — underlying the Evaporating Cloud, the Prerequisite Tree, and the Strategy and Tactics Tree. (draft — not yet reviewed) - [Sufficient Cause (Sufficiency Logic)](https://tocatlas.com/sufficient-cause): The logic of cause and effect — 'if A, then B' — that underlies the Current Reality Tree, Future Reality Tree, Transition Tree, and negative branches. (draft — not yet reviewed) - [Intermediate Objective (IO)](https://tocatlas.com/intermediate-objective): The transitional condition that must exist before a higher objective can be reached — the entity an Intermediate Objectives Map sequences and a Prerequisite Tree pairs with the obstacle blocking it. (draft — not yet reviewed) - [Categories of Legitimate Reservations (CLR)](https://tocatlas.com/categories-legitimate-reservations): Goldratt's seven-category, three-level set of logic rules for scrutinizing cause-and-effect statements; the audit protocol that turns a Thinking Process drawing into a defensible claim. (draft — not yet reviewed) - [Inherent Simplicity](https://tocatlas.com/inherent-simplicity): Goldratt's claim that an apparently complex system is governed by a few cause-and-effect relationships, so focused improvement is possible once the right cause is found. (draft — not yet reviewed) - [Undesirable Effect (UDE)](https://tocatlas.com/undesirable-effect): A negative symptom of current reality, stated relative to the system's goal: the raw material a Current Reality Tree traces to a core problem and a Future Reality Tree converts into a Desirable Effect. (draft — not yet reviewed) - [Injection](https://tocatlas.com/injection): A proposed future state, condition, or action that changes a system's causal logic: the building block of a Future Reality Tree that turns Undesirable Effects into Desirable Effects, breaks a cloud's conflict, or trims a negative branch. (draft — not yet reviewed) - [Assumption](https://tocatlas.com/assumption): The statement, condition, or belief that explains why a logical relationship holds between two entities in a Thinking Process diagram: the inspectable rationale under every arrow, and the place where a cloud evaporates. (draft — not yet reviewed) ## Strategy, Marketing, and Sales - [Market Constraint](https://tocatlas.com/market-constraint): The condition where demand at the current offer caps throughput more than internal capacity, changing the exploitation move from operations to market strategy. (draft — not yet reviewed) - [Marketing Core Conflict Cloud](https://tocatlas.com/marketing-conflict-cloud): A pricing conflict cloud that separates the customer's perceived-value basis from the supplier's cost-floor need, then resolves the clash through a TVC floor and isolated market segmentation. (draft — not yet reviewed) - [Decisive Competitive Edge (DCE)](https://tocatlas.com/decisive-competitive-edge): A market advantage created when TOC-driven operational capability satisfies a significant customer need better than any serious competitor can. (draft — not yet reviewed) - [Reliable Rapid Response (RRR)](https://tocatlas.com/reliable-rapid-response): The B2B manufacturing S&T Tree template that turns reliable due-date performance into a market offer, then sells rapid response at a premium where urgent delivery has real value. (draft — not yet reviewed) - [Mafia Offer (Unrefusable Offer)](https://tocatlas.com/mafia-offer): Goldratt's term for a market offer built from a real operational edge, strong enough that customers must buy and competitors cannot quickly match it. (draft — not yet reviewed) - [Viable Vision](https://tocatlas.com/viable-vision): Set an ambitious organization-wide growth target, then use TOC logic to show the necessary and sufficient changes that reach it without exhausting cash, capacity, or attention. (draft — not yet reviewed) - [Technology Questions (Goldratt's Six Questions)](https://tocatlas.com/technology-questions): Goldratt's six-question sequence for assessing whether a new technology creates real value, by tracing it from raw capability to the limitation it removes to the old rules that must change. - [Six Layers of Resistance](https://tocatlas.com/six-layers-resistance): A sequenced buy-in framework that treats resistance to change as unresolved agreement about the problem, the solution, its consequences, the obstacles, or the commitment to act. (draft — not yet reviewed) - [Applying Flow to Sales](https://tocatlas.com/sales-flow): Herman and Goldratt's pattern for managing sales opportunities as a constrained flow, limiting open opportunities, abolishing funnel-load measures, and running POOGI on delay and dropout causes. (draft — not yet reviewed) ## ToC in Services - [Services Management (TOC)](https://tocatlas.com/services-management): The TOC discipline for service organizations: prepend goal and global-measure steps to the focusing loop, name the permanent bottlenecks, and run them under a time-and-flow vocabulary. (draft — not yet reviewed) - [ToC in Services](https://tocatlas.com/toc-services): Translate TOC from goods-world assumptions to service work: manage resource buffers, capacity response, service deliverables, and client value rather than inventory and cost-plus pricing. (draft — not yet reviewed) - [ToC for Customer Support Services](https://tocatlas.com/toc-customer-support): Apply TOC to technical support by separating necessary service from avoidable demand, gating field dispatch behind remote diagnosis, and measuring throughput protected rather than calls handled. (draft — not yet reviewed) - [ToC for Healthcare](https://tocatlas.com/toc-healthcare): The TOC discipline for healthcare: find the binding constraint in patient flow, exploit it against the time commitment, subordinate surrounding workflows, and elevate before adding capital. (draft — not yet reviewed) - [ToC for Education](https://tocatlas.com/toc-education): TOC for Education translates the Cloud, Logic Branch, and Ambitious Target Tree into classroom tools so learners can reason with explicit needs, causes, obstacles, and objectives. (draft — not yet reviewed) - [ToC for Prisons](https://tocatlas.com/toc-prisons): Teach correctional-system participants simplified TOC Thinking Process tools so release readiness is treated as a reasoning constraint, not only as job placement. (draft — not yet reviewed) - [Unique Features of Government](https://tocatlas.com/unique-features-government): Adapt TOC to public agencies by defining the public-value goal unit, measuring quality throughput against operating expense, and treating authority, regulation, and demand as design conditions. (draft — not yet reviewed) - [Justice in Time](https://tocatlas.com/justice-time): Apply TOC to court congestion by treating judicial attention as the constraint, protecting trial-phase flow, and subordinating scheduling policy to case-level completion. (draft — not yet reviewed) - [Oxfordshire Radcliffe Hospital A&E](https://tocatlas.com/oxfordshire-radcliffe-ae): The mid-2000s buffer-management work at two Oxfordshire hospitals that lifted four-hour A&E compliance from the 50-to-60-percent range into the 90s without added resources. (draft — not yet reviewed) ## Knowledge Work and Software - [ToC for Software and DevOps](https://tocatlas.com/toc-software-devops): Apply TOC to software delivery: read the pipeline as a flow system, find and protect the constraint, subordinate other work, and keep it visible. (draft — not yet reviewed) - [Flow Metrics for Knowledge Work](https://tocatlas.com/flow-metrics): A measurement vocabulary for intangible work: cycle time, WIP, delivery throughput, flow efficiency, aging work, and blocked time, used to identify and protect knowledge-work constraints. (draft — not yet reviewed) - [Throughput Economics for Software Organizations](https://tocatlas.com/throughput-economics-software): Evaluate software roadmap, pricing, platform, and capacity moves by their expected effect on throughput, investment, and operating expense across conservative and optimistic scenarios. (draft — not yet reviewed) ## Complex Environments and Change - [TLS Integration (TOC + Lean + Six Sigma)](https://tocatlas.com/tls-integration): The integration in which TOC supplies the focusing logic, Lean removes waste at the few places that matter, and Six Sigma reduces throughput-limiting variation; sequence is decisive. (draft — not yet reviewed) - [ToC in Complex Organizations](https://tocatlas.com/complex-organizations): Coordinate many interdependent units with a common throughput-relative measurement system and shared flow-control rules, rather than pretending the enterprise has one local schedule. (draft — not yet reviewed) - [S&T Trees in Organizations](https://tocatlas.com/st-trees-organizations): Deploy Strategy and Tactics Trees as organizational management artifacts: each level validates the logic it owns, receives authority for its tactic, and sees how its work supports the goal. (draft — not yet reviewed) - [Management Attention Constraint](https://tocatlas.com/management-attention-constraint): The claim that the limit on an organization's rate of strategic improvement is the finite capacity of senior managers to focus and decide, not cash, equipment, or market demand. (draft — not yet reviewed) - [ToC for Personal Dilemmas](https://tocatlas.com/personal-dilemmas): A personal-scale use of TOC Thinking Processes for resolving chronic conflicts, setting life goals, and protecting focus with the same logic used in organizational change. (draft — not yet reviewed) - [The Change Matrix](https://tocatlas.com/change-matrix): A six-box TOC diagnostic for testing whether a proposed change is worth choosing from the other party's current, transition, and future reality. (draft — not yet reviewed) - [Magic Druids](https://tocatlas.com/magic-druids): Powell and Cronin's teachable Thinking Process shortcut: a figure-eight sufficiency diagram that captures recurring conflict loops and can be expanded into a Current Reality Tree or Evaporating Cloud. (draft — not yet reviewed) - [The ProConCloud Method](https://tocatlas.com/proconcloud): Alan Barnard's five-step decision method that combines the Pros-Cons list, the Change Matrix, and the Evaporating Cloud to resolve chronic change conflicts without compromise. (draft — not yet reviewed) - [Fundamental Structure of ToC](https://tocatlas.com/fundamental-structure-toc): Schragenheim and Updegrove's 2024 attempt to organize the Theory of Constraints by logical dependency: seven high-level qualities, three breakthrough insights, and the tools that follow. (draft — not yet reviewed) - [Management by Criticalities (MBC II)](https://tocatlas.com/management-criticalities): Dan Trietsch's MBC II reformulation of constraint management: balance resource criticalities for stochastic, economically valued systems rather than treating one constraint as the permanent planning center. (draft — not yet reviewed) ## Optional - [Colophon](https://tocatlas.com/colophon): Publication credits, the reference-not-advice notice, and the conflict-of-interest disclosure for The Theory of Constraints Atlas.