The Logical Thinking Process A Systems Approach To Complex Problem Solving With Cdrom H William Dettmer

Using Dettmer's Thinking Processes When the Theory Isn't Enough

I ran into a real problem a few years back with a Current Reality Tree that kept collapsing under its own weight. We were mapping out bottlenecks in a mid-size manufacturing operation, and the tree branched into so many undesirable effects that nobody could agree on which one was actually driving the others. The standard approach from The Logical Thinking Process A Systems Approach To Complex Problem Solving With Cdrom H William Dettmer assumes your cause-and-effect chains will stay reasonably linear, but on the shop floor they rarely do. What ended up working was stopping the CRT altogether and switching to an Evaporating Cloud for the central conflict first, which let us identify the actual assumption blocking resolution, then going back to the tree with a much narrower scope. It took about twenty minutes to resolve what would've taken two days of arguing over branch ordering. The book lays out several logic trees. Most people think these are just fancy flowcharts. They aren't. Each one answers a specific question about a system. The Current Reality Tree diagnoses the problem. You start with a list of Undesirable Effects and work backward through cause-and-effect to find the core conflict or bottleneck. The assumption is that most symptoms trace back to one or two root causes, which is why you should never build a CRT with more than about fifteen UDEs or it becomes unreadable garbage. I've seen consultants build trees with forty-plus branches and then claim they "found the root cause," which is just noise dressed up as analysis.

The Evaporating Cloud resolves conflicts by identifying the assumptions that create the dilemma. You map out two opposing demands, trace them to a common prerequisite, and then challenge the assumption that makes the conflict seem necessary. This is the most frequently misunderstood diagram. People treat it as a debate tool instead of a structured way to expose false dichotomies. Once you strip away the wrong assumption, the conflict disappears. It evaporates, hence the name. The Future Reality Tree tests whether your solution actually works before you implement it. You take your injection — the change you're proposing — and chain it forward through cause-and-effect to see if it produces the desired outcomes without creating new undesirable effects. This is where most teams skip ahead, but skipping it is how projects fail. A proper FRT usually takes an afternoon to build for a medium-complexity problem. The Prerequisite Tree identifies all the obstacles standing between your current state and the desired future, then breaks them into implementable steps. It's essentially a planning tool disguised as logic. The key insight nobody mentions is that you should build this before the Strategy & Tactics diagram. Too many people jump straight to strategy and realize later they never accounted for a critical obstacle.

The Strategy & Tactics diagram turns the prerequisite tree into an action plan. You distinguish between critical actions that must happen and nice-to-have actions that don't block progress. This is where project managers spend most of their time, and where most slippage happens because nobody actually enforced the difference between the two categories. The Transition Tree fills in the implementation detail. It walks through each step sequentially, checking that every action leads to the next outcome. It sounds trivial until you try to execute a multi-step change without one and discover that three of your steps were predicated on something that never actually happened.

What the CD-ROM part is and isn't

The CD-ROM that came with the book is Think & Decisions software from Goldratt Institute. It's not a magic solver. It's a diagramming tool that enforces the structure of each thinking process. You can build the trees by hand on paper, and many people do, but the software catches formatting mistakes and keeps your cause-and-effect links consistent. The old version that shipped with the book is Windows-only and hasn't been updated in years. The concepts remain valid; the software is just a crutch for people who want cleaner diagrams faster. Here's the thing that slows teams down more than anything else: the Current Reality Tree makes it easy to mistake correlated symptoms for causal chains. You'll link two undesirable effects together because they appear together, not because one causes the other. The book tells you to validate every "if-then" link by asking whether the cause is sufficient and necessary. In practice, people rush through this validation. I've read trees where half the links were built on gut feeling rather than evidence. The fix is simple but tedious: each link needs a written justification, and someone who wasn't involved in building the tree needs to review every single one. It adds about two hours of work for a standard five-level tree, and it saves you from wasting a week on a solution that addresses the wrong problem. This method assumes the problem is knowable and that stakeholders can agree on cause-and-effect relationships. That assumption fails in environments where people have conflicting incentives and will deliberately misrepresent causality to protect their position. I dealt with this in a supply chain restructuring where two department heads produced two different Current Reality Trees for the same problem, and neither was wrong from their perspective because their data sources were filtered through different assumptions about how the other department operated. Logic trees don't resolve political problems. In cases like that, you need stakeholder mapping and incentive alignment before you even open the software. Otherwise you're just building an elegant diagram that no one will act on.

The method also struggles with high-velocity environments where the problem changes faster than you can build the tree. If you're running a crisis response team and conditions shift every hour, spending four hours on a Future Reality Tree is a waste. Use the thinking processes when you have time to think. Don't use them when you need to act immediately.

Getting started without drowning in theory

Don't try to master all six diagrams at once. Pick one problem you've been sitting on for weeks and build a Current Reality Tree for it. You'll understand the method in practice faster than reading another chapter about it. Start with a short list of five to seven UDEs. Don't inflate it. Work backward from the most painful symptom and follow the causal chain. When you hit a branch point, stop and verify the link before proceeding. The discipline of validating every connection is what separates a useful analysis from a decorative one. The book itself is dense and occasionally repetitive, but the diagrams are the real value. If you can get your hands on a copy of the CD-ROM software, it's worth using even if the original installation is archaic on modern systems. The logic structure it enforces is harder to maintain by hand than most people expect.

A note on the DVD/CD-ROM situation

That software is obsolete. Goldratt Institute released updates, but they're tied to the TOC ecosystem and require licensing. You can find older versions scattered across various file-sharing sites, but I wouldn't recommend chasing them down — the free alternatives like Visio or even draw.io can replicate the diagramming function well enough if you follow the book's conventions. The methodology doesn't depend on the software. The software just removes the friction of redrawing diagrams repeatedly as your understanding evolves.