Assumption
Concept: Vocabulary that names a phenomenon.
The statement, condition, or belief that explains why a logical relationship holds between two entities in a Thinking Process diagram — the rationale under the arrow, sometimes written down, always present.
Also known as: the rationale under the arrow; what’s underneath the arrow.
Every arrow in a Thinking Process diagram makes a claim, and behind every claim sits a reason the claim is supposed to be true. That reason is the assumption. It is the answer to the question a scrutinizer asks when pointing at a link and saying “what’s underneath the arrow?” The assumption is not the entity at either end; it is the belief about the world that lets the two entities be connected at all. Naming it is what turns a diagram from a picture of someone’s opinion into something a peer can test, because once the assumption is on the table, it can be checked, argued with, and found wrong. That last possibility is the point. The Thinking Processes are built on the wager that most chronic problems persist because of an assumption nobody has examined, and the entire toolset is machinery for dragging those assumptions into the light.
Context
Assumptions become the active object of attention at the moment a Thinking Process diagram stops being drawn and starts being challenged. A Current Reality Tree asserts that one entity causes another; an Evaporating Cloud asserts that two requirements conflict; a Future Reality Tree asserts that an injection will produce a string of desirable effects. None of those assertions stands on its own. Each rests on a belief about how the system behaves, and the quality of the analysis is the quality of those beliefs.
Most assumptions are never written down, and the literature is clear that this is acceptable. Some are what practitioners call “oxygen”: claims so widely true and well understood that documenting them would only clutter the diagram. “All dogs are animals” is the assumption under the arrow from I have a dog to I have an animal, and no one needs to see it spelled out. The assumptions worth surfacing are the other kind: the ones that feel like oxygen but are not, the beliefs an organization treats as fixed reality when they are actually choices, conventions, or outdated facts. Those are where a system gives way under the lightest push. The conflict in a cloud holds because at least one assumption holding it is invalid, and the practitioner’s job is to find which one.
This is why assumption work sits at the center of TOC’s theory of why systems get stuck. Goldratt’s four fundamental assumptions of TOC include the claim that every conflict can be removed once the erroneous assumption causing it is found and challenged. The assumption is therefore not a minor technical component of the toolset. It is the thing the whole apparatus is designed to expose.
What It Is
An assumption is a statement, condition, or belief about why a logical relationship exists between entities. It lives under an arrow, not in a box. Where the entities name what is connected, the assumption names why the connection holds. The TOCICO Dictionary records that every logical relationship in every Thinking Process diagram has one or more underlying assumptions, whether or not they appear on the page, and whether or not they happen to be valid.
The form the assumption takes depends on the reasoning mode of the diagram it sits in:
• In a sufficiency-based diagram — the Current Reality Tree, Future Reality Tree, or Transition Tree — the arrow reads if A, then B, and the assumption explains why A is enough to produce B. For if I have a dog, then I have an animal, the assumption is all dogs are animals. The assumption is what a scrutinizer disputes when challenging cause-and-effect existence.
• In a necessity-based diagram — the Evaporating Cloud, Prerequisite Tree, or Goal Tree — the arrow reads in order to A, I must have B, and the assumption explains why B is required. For in order to have food to eat, I must have money to buy food, the assumption is I must pay for food. Change the assumption — find food that need not be bought — and the necessity dissolves.
The vocabulary fans out into named variants, each tied to a specific place in the toolset:
| Variant | Where it lives | What it is |
|---|---|---|
| Conflict assumption | Evaporating Cloud | One of the four assumptions answering why each side jeopardizes the other, why the two prerequisites conflict, and why there is no other way to satisfy a requirement. Addressing these directly often breaks the cloud faster than challenging every arrow’s assumption. |
| Necessary assumption | Strategy and Tactics Tree | A statement of why a strategy is needed to achieve the higher-level step above it, typically the undesirable effects or unmet desirable effects that create the need for the change. |
| Parallel assumption | Strategy and Tactics Tree | A statement of why the strategy is possible and why the chosen tactic is the best route to it, given the risks, constraints, and obstacles considered. |
| Sufficiency assumption | Strategy and Tactics Tree | A warning that the lower-level entities, taken together, are enough to cause the tactic above them; the fact of life that, if ignored, leaves the step below insufficient. |
| Fundamental assumption | The TOC method itself | One of Goldratt’s four base beliefs about social systems: people are good, every conflict can be removed, every situation is inherently simple, every situation can be substantially improved. |
The Strategy and Tactics Tree is the one tool that promotes assumptions from rationale-under-the-arrow to named entities on the page, because at strategic scale the reasons a step is needed, possible, and sufficient are too consequential to leave implicit.
How It Is Measured or Recognized
An assumption is recognized by where it sits in the logic: under an arrow, supplying the reason a relationship holds. The practical test is the scrutinizer’s question. Point at any link in a diagram and ask “why does this follow?” The answer, the because clause, is the assumption. If no honest because can be stated, the link is not yet sound; if the because is stated and turns out to be false, the link is broken regardless of how confident the diagram looks.
Assumptions are surfaced, not measured. The work is one of articulation and challenge rather than counting. Three checks separate a load-bearing assumption from oxygen and a valid assumption from an invalid one. First, is it actually doing work? An assumption everyone in the room accepts without hesitation is probably oxygen and can stay implicit. Second, does it hold for this system? An assumption true in general may be false in the specific environment under study, and that gap is exactly where a cloud’s invalid assumption hides. Third, what happens if it’s wrong? The assumptions worth surfacing are the ones whose failure changes the conclusion: invalidate them and a conflict evaporates, a predicted effect disappears, or a cause-and-effect chain collapses.
Warning: The most consequential assumptions are the ones that feel like facts. A team will challenge an assumption it recognizes as a judgment call and wave past the one it treats as the unchangeable nature of reality: “customers won’t wait,” “the regulator won’t allow it,” “we can’t hold that inventory.” Those treated-as-fixed beliefs are usually where the invalid assumption holding a chronic conflict actually lives. Surface the assumptions that nobody thinks need stating, not just the ones that already feel debatable. A cloud that will not evaporate is almost always a cloud whose real assumption has not yet been named.
Why It Matters
Naming the assumption is what makes a Thinking Process diagram falsifiable instead of merely persuasive. A diagram without articulated assumptions asserts that the world works a certain way and dares the reader to disagree without giving them anything specific to disagree with. The moment the assumption under an arrow is stated, a peer can examine it, test it against the system in front of them, and reject it on evidence. The Categories of Legitimate Reservations are the formal protocol for that challenge, and most reservations a scrutinizer raises (cause insufficiency, additional cause, predicted-effect existence) are ultimately disputes about an assumption under an arrow.
Assumption work is also the mechanism behind TOC’s most distinctive claim: that conflicts can be dissolved rather than compromised. An Evaporating Cloud does not split the difference between two requirements. It finds the invalid assumption that makes them appear to conflict and removes it, so that both requirements can be satisfied at once. The breakthrough lives in the assumption, not in the negotiation. Without the discipline of surfacing and testing assumptions, the cloud would be just another way to draw a trade-off; with it, the cloud becomes a way to design a way out of the trade-off entirely.
For Strategy and Tactics Tree work, assumptions carry even more weight because they are written into the structure. The necessary, parallel, and sufficiency assumptions at each node make the reasoning of an entire transformation plan inspectable: why each strategy is needed, why the chosen tactic is the right one, and why the lower steps are enough to deliver the step above. A reviewer can audit the logic of a multi-year change program by reading its assumptions, which is impossible when the rationale lives only in the planners’ heads.
Across the TOCICO Thinking Processes domain, certification work assumes a practitioner can state the assumption under any arrow, classify it by reasoning mode, distinguish oxygen from the assumptions worth challenging, and use the conflict assumptions to break a cloud. The named S&T variants are part of the working vocabulary the certification track expects without confusion.
Common Misunderstanding
“An assumption is the same as a fact.” A fact is true; an assumption is believed true, and may not be. The entire value of surfacing an assumption comes from the possibility that it is wrong. Treating assumptions as facts is how chronic conflicts survive: the belief holding the conflict in place is accepted as the unchangeable nature of reality and never tested.
“If an assumption isn’t on the diagram, it isn’t there.” Every logical relationship has one or more underlying assumptions whether or not they are written down. The undocumented ones, the oxygen, are still load-bearing; they are simply too obviously true to be worth showing. The danger is the assumption that masquerades as oxygen: a belief treated as too obvious to state that is in fact the invalid one. The scrutinizer’s “what’s underneath the arrow?” exists precisely to drag those out.
“An assumption is the same as an opinion.” An opinion expresses a preference; an assumption asserts something about how the system behaves and submits to being tested against that system. “We should hold more inventory” is an opinion. “Customers will not wait longer than the current lead time” is an assumption: checkable, and often false. Collapsing the two lets unexamined beliefs ride into a diagram disguised as analysis, which is the failure the Categories of Legitimate Reservations are built to catch.
“The belief under an arrow and the S&T assumption variants are different things.” They are the same construct at different scales. The necessary, parallel, and sufficiency assumptions of a Strategy and Tactics Tree are assumptions promoted to named entities because, at strategic scale, the reasons a step is needed, possible, and sufficient are too consequential to leave under the arrow. The underlying object, a statement of why a relationship holds, is identical.
Related Articles
Detects: Categories of Legitimate Reservations (CLR) — The Categories of Legitimate Reservations are the protocol for challenging the assumption under an arrow; a faulty assumption is what most CLR reservations are ultimately disputing.
Related: Future Reality Tree (FRT) — A Future Reality Tree's predicted effects rest on assumptions about how the system behaves once an injection holds; a wrong assumption is how a sound-looking FRT fails in practice.
Related: Necessary Cause (Necessity Logic) — Necessity-based links carry an assumption stating why the upstream condition is required for the downstream one; the assumption is the rationale under the necessity arrow.
Related: Sufficient Cause (Sufficiency Logic) — Sufficiency-based links carry an assumption stating why the upstream cause is enough to produce the downstream effect; the assumption is what a scrutinizer challenges as cause-and-effect existence.
Used by: Evaporating Cloud (Conflict Resolution Diagram) — A cloud evaporates by surfacing and invalidating the assumptions under its arrows; the four conflict assumptions are the most direct targets.
Used by: Strategy and Tactics Tree (S&T Tree) — The S&T Tree formalizes assumptions as named entities: the necessary, parallel, and sufficiency assumptions that justify each strategy-tactic node.
Sources
• Cox, TOCICO Dictionary of Theory of Constraints Terms (2nd ed., 2012), entries “assumption,” “conflict assumptions,” “fundamental assumptions (of TOC),” “necessary assumption,” “parallel assumption,” and “sufficiency assumption.” The certification-grade definitions this entry cross-checks against, including the oxygen distinction, the “what’s underneath the arrow?” scrutiny convention, and the S&T Tree assumption variants.
• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 25 (Scheinkopf, “Thinking Processes Including S&T Trees”). The working source for assumptions as the inspectable rationale layer behind the cloud, the Categories of Legitimate Reservations, and S&T construction.
• Scheinkopf, Thinking for a Change: Putting the TOC Thinking Processes to Use (1999). The standard practitioner treatment of surfacing, verbalizing, and challenging assumptions under both sufficiency and necessity arrows.
• Goldratt, The Choice (2008). The narrative source for the four fundamental assumptions of TOC and the claim that every conflict can be removed by finding and challenging the erroneous assumption causing it.