Strategy and Tactics Tree (S&T Tree) §

Pattern: A named solution to a recurring problem.

A hierarchical Thinking Process tool that connects an organization’s strategy to the tactics, assumptions, sequence, and lower-level changes required to achieve it.

Also known as: S&T Tree; Strategy and Tactic Tree; Transformation S&T Tree.

Reasoning mode: mixed — strategy-tier nodes follow necessity-based logic (an objective’s lower strategies are jointly required); tactic-tier groupings follow sufficiency-based logic (the tactics under a strategy are together enough to produce it).

TOC uses a Strategy and Tactics Tree when organizational change is too large for a single Future Reality Tree, Prerequisite Tree, or Transition Tree. At every level, strategy answers “what for?” and tactic answers “how?” The assumptions state why the tactic should achieve the strategy and why another level of detail is needed.

Understand This First §

Context §

The S&T Tree carries the Thinking Processes to organizational scale. The Current Reality Tree diagnoses what to change. The Evaporating Cloud and Future Reality Tree test what to change to. The Prerequisite Tree and Transition Tree map implementation. The S&T Tree combines that logic when a change must align executives, managers, functions, measures, policies, and daily work.

Goldratt’s definitions are deliberately plain. Strategy answers “what for?” Tactic answers “how?” The tree applies both questions at every level. A tactic at one level becomes a strategy for the level below it, which adds only enough detail to make the higher step implementable without losing its connection to the system goal.

The tool is most visible in Viable Vision work. Ferguson’s Handbook chapter treats Viable Vision S&T Trees as plans for building, capitalizing on, and sustaining a Decisive Competitive Edge without exhausting cash, management attention, or the organization’s capacity to absorb change. The same structure applies to other large changes that must keep local action synchronized with system purpose.

Problem §

Strategic plans often separate ambition from execution. The executive page says what the organization wants. Project plans say what departments will do. Between them lies the causal logic: why those actions should produce the strategy, which assumptions must hold, which order protects the constraint, and which lower-level changes must precede the next step.

That gap creates two failures. First, people can work hard on tactics that no longer connect to the goal. Second, managers can defend a strategy while leaving the people below them to infer the operating changes. The result is a plan that looks aligned in a slide deck and fragments in execution.

Forces §

Solution §

Build a hierarchy of strategy-and-tactic steps. State the goal or ambitious target at the top, then add the necessary lower steps that make it achievable. Continue downward only until the tactic above is clear enough for the people who must act.

Each S&T step has five parts:

The handoff between levels carries the logic. A tactic at Level 2 may become the strategy that Level 3 explains; at Level 3, that tactic becomes the strategy that Level 4 turns into functional change. Local action stays tied to system purpose without requiring every person to read the whole tree.

Read the tree in two directions. Vertically, each lower step exists because a higher step requires it. Horizontally, steps at the same level must fit together so one function’s implementation doesn’t damage another’s. The tree can inform a schedule, but it is a logic structure: what must be done, why, and how much detail the next level needs.

Implementation normally proceeds one step at a time. After implementing a tactic, the team checks whether its strategy is now true in reality. A miss points to one of three faults: the tactic was incomplete, the parallel assumption was false, or a relevant condition was absent from the tree. The team repairs the logic before continuing.

How It Plays Out §

In the generic Viable Vision structure, the top step is an organization solidly on a Process of Ongoing Improvement. The next major target is a demanding profit goal reached within a few years without taking real risks or exhausting the organization’s resources. Its high-level tactic is to build a decisive competitive edge, capitalize on it in large enough markets, and sustain it. The S&T Tree then specifies the edge, the market proof, the operating changes that make the promise real, and the measures that keep the edge from eroding.

Ferguson’s retailer example shows the pattern clearly. The strategy is not “improve retail operations.” It is to make availability so high that the market knows it, while price, selection, and quality remain acceptable. The tactic is to move from forecast-driven push to consumption-driven replenishment, supported by buffer management and supplier coordination. Lower levels then detail internal pull distribution, stock-buffer target adjustment, supplier ordering cadence, and the proof mechanism that lets managers see the profit gain came from the initiative rather than noise in sales.

A small S&T fragment of the retailer example shows both tier defaults. At the strategy tier, both lower strategies are necessary for the objective, so bare multi-in edges mean AND. At the tactic tier, either tactic is modeled as sufficient for its strategy, so bare multi-in edges mean OR. No explicit junctor is needed:

flowchart BT
    Tac1["Tactic: shift internal distribution from push to pull"] --> StratB["Strategy: consumption-driven replenishment is in place"]
    Tac2["Tactic: tune stock-buffer targets to actual demand variance"] --> StratB
    StratA["Strategy: market knows availability is high"] --> Goal["Objective: profitable growth from a sustained availability edge"]
    StratB --> Goal

The default form applies only when the bare-edge reading matches the claim. The companion fragment makes two exceptions explicit: an AND-junctor makes tactics jointly sufficient, and an OR-junctor makes lower strategies alternative paths to the same objective.

flowchart BT
    TacX["Tactic: distribution shifts to pull"] --> AndTac(("AND"))
    TacY["Tactic: stock-buffer targets are tuned to demand variance"] --> AndTac
    AndTac --> StratC["Strategy: consumption-driven replenishment is in place"]
    StratC --> OrObj(("OR"))
    StratD["Alternative strategy: exclusive-supplier reliability contracts are in place"] --> OrObj
    OrObj --> ObjB["Objective: availability is consistently high"]

    classDef andjunctor fill:#A6894B,stroke:#3a2f1a,color:#fff,stroke-width:1.5px;
    classDef orjunctor fill:#A6894B,stroke:#3a2f1a,color:#fff,stroke-width:1.5px;
    class AndTac andjunctor;
    class OrObj orjunctor;

In the second diagram, the pull shift and buffer tuning must occur together to produce consumption-driven replenishment. The two strategies above them remain alternatives: either can produce consistently high availability. The junctors override the tier defaults rather than decorate the convergence.

The same structure applies outside retail. A make-to-order manufacturer may build an S&T Tree around reliable rapid response. A project organization may use one to define which projects to accept and how to protect their critical chains. A hospital may use one to connect patient-flow goals to ward, emergency-department, diagnostic, and discharge policies. The content differs, but the form stays stable: each local move has a stated purpose, stated assumptions, and a place in the larger logic.

The S&T Tree can also absorb work from the other Thinking Processes. PRT obstacles become necessary assumptions and lower-level strategies. Transition Tree sequences become lower-level tactics. Negative Branch Reservations modify the tree before implementation. The S&T Tree doesn’t replace those tools; it coordinates their outputs across the organization.

Warning: Do not treat an S&T Tree as a prettier strategic plan. If the assumptions are not written as testable claims, and if each tactic is not checked against the strategy it is supposed to achieve, the tree has lost the TOC part of the method.

Consequences §

Benefits. The S&T Tree makes organizational alignment auditable. People can see why their work is needed, how it contributes to the higher step, and which failed assumption would require a different tactic. The tree also exposes cross-functional dependencies before execution, rather than leaving sales, operations, finance, and management to reconcile tactics after each function has optimized locally.

The tree can be presented from Level 1 downward, giving each audience enough context to understand its work without losing the system purpose. That supports the Six Layers of Resistance: people can examine the target, the need for each proposed step, and the implementation concerns separately.

Liabilities. An S&T Tree is demanding to write. Weak assumptions make the artifact look more certain than it is, and a bad tree can spread a flawed strategy faster than an ordinary project plan. The team must also distinguish necessary assumptions, parallel assumptions, tactics, and sufficiency assumptions. Otherwise, the tree becomes a vocabulary exercise.

The other liability is over-detailing. The S&T Tree should add a lower level when inertia, ambiguity, or likely misuse would prevent the higher tactic from being implemented correctly. It should not decompose every action until the tree becomes a task database. A schedule, a Critical Chain network, or a Transition Tree can carry the final action detail after the S&T Tree has done its work.

Related Articles §

Sources §