Transition Tree

Definition

The Transition Tree (TT) is a sufficient-cause diagram for building detailed action plans: each planned action is an injection that, combined with a condition already present, is meant to create a specific new condition — which then combines with the next action to create the next condition, and so on until the stated objective exists. Its four entity types are injections (the actions), entities that already exist in the present, entities the plan predicts will exist in the future as intermediate results, and the final objectives. The discipline forces you to state, for every step, exactly what reaction that action is supposed to produce — not just what to do next.

In the Book

Chapter 6 opens with a scene the author observed directly: a group of middle managers planning small-group meetings to change their plant's culture, drafting talking points about productivity trends and overtime costs without ever having defined what changed behavior they expected to see, or what they expected the groups to do once the meetings ended. A facilitator stops them — "putting the cart before the horse" — and redirects them to define the objective before drafting content, which is exactly the gap the Transition Tree exists to close: "we forget that for every action there's at least one reaction," and a plan that skips stating the intermediate condition each step is supposed to create can't be checked for whether the next step actually depends on anything real. The chapter frames the tool through a manufacturing analogy — raw material transitioning step by step, each resource changing it a bit further toward the finished product — and lists concrete use cases: designing a workshop's flow, planning a client meeting, prepping for an emotionally charged conversation, or defining the actions inside a strategic plan. It is explicitly the tool for when you already have a good idea what to do; when you don't, the book directs you to the Prerequisite Tree first (Chapter 10). In the Full Analysis, Transition Trees are the last tool applied, turning a Prerequisite Tree's intermediate objectives and injections into the concrete, delegable step-by-step plans that managers can review with the people who will execute them.

Why It Matters

Plans usually fail not because the final step was wrong but because an early step's assumed effect never actually landed — the meeting happened, but the condition it was supposed to create in people's heads didn't. Forcing every action in a plan to name the specific condition it's supposed to produce, and confirming that condition truly exists before the next action depends on it, is a general defense against "we did all the things on the list but nothing changed" — applicable to any sequenced plan, not just manufacturing or organizational change.