Current Reality Tree

Definition

The Current Reality Tree (CRT) is a diagnostic tool for finding a "core driver" — one underlying cause that produces many of a system's separate-seeming problems — by connecting a short list of pertinent entities (usually undesirable effects) with sufficient-cause logic until the causal structure among them becomes visible. Unlike root-cause methods that drill straight down from one symptom, the CRT works laterally first: it documents the cause-effect web across five to ten named symptoms, and only in the final steps does it apply a "so what test" to identify the common cause underneath them.

In the Book

Chapter 8 opens with a diagnostic checklist of symptoms — an endless problem list, difficulty prioritizing among screaming projects, "the same old problems with the same old solutions," an inability to name the system's constraint or even its purpose — as the signal that a CRT is warranted. The chapter's running example is Display Manufacturing, a metal display-rack maker that assembled a cross-functional team (manufacturing, accounting, engineering, sales, marketing, plus former employees of a customer and a store) to find what was really limiting their customers' perceived value. Their initial pertinent-entity list included things like "installed costs are too high from the customers' perspective" and "display installation is difficult for the customer" — the team explicitly guarded against smuggling in a pet solution disguised as a problem (e.g., "we haven't implemented the XYZ quality program" is not an entity that exists, it's an absent solution). Building the tree meant connecting entities pairwise — either a "V Connection" (one common cause for two listed entities) or a "Linear Connection" (one entity causing another) — while applying the Categories of Legitimate Reservation to each link, without adding new entities except where a connection genuinely required one.

Why It Matters

Long problem lists paralyze organizations because every item looks equally urgent and independently caused, which sends effort in ten directions at once. The CRT's discipline — state the symptoms as real existing entities (not missing solutions), connect them with tested cause-effect logic rather than intuition, and let the core driver emerge from the pattern of connections — gives you a principled way to find the one lever that, if moved, collapses several problems simultaneously, in any domain where a scattered list of complaints actually traces back to a shared cause.