# The Logical Thinking Process **H. William Dettmer**  --- _Before optimising anything, know where you're going and why you're not already there._ Dettmer takes the Theory of Constraints and turns it into a problem-solving method built around four questions, asked in order: Why should I change? What should I change? What should I change to? How do I make the change happen? Five interconnected logic trees answer these questions, each building on the previous one, all written in plain-language complete sentences with if-then relationships. The rigour is in the structure. The most common management error is jumping straight to the fourth question while skipping the first three. It is more important to know where you're going than to get there quickly. Do not mistake activity for accomplishment. That instinct, reaching for action before understanding, is the [[Execution trap]] in a sentence. --- **The Goal Tree answers the first question and sets the entry point for everything that follows.** It has three layers. At the top: one measurable goal, the long-term visible indicator of mission accomplishment. Below that: three to five critical success factors, the high-level outcomes that collectively constitute goal attainment. Below those: the necessary conditions required to realise each success factor. Mission and goal are different things: mission is a high-level purpose that survives indefinitely; a goal is a measurable outcome that, when achieved, clearly demonstrates the mission is being fulfilled. Building a Goal Tree is a forcing function for [[Real choices]]. Most organisations can list what they want. Few can articulate the limited set of outcomes that, collectively, constitute getting there. The tree forces that articulation, and in doing so it makes the tradeoffs visible. Without clarity on where you want to be, you cannot diagnose why you're not already there. The Goal Tree is the most important tree in the process because every subsequent tree takes its bearings from it. --- **The Current Reality Tree diagnoses the gap between where you are and where the Goal Tree says you should be.** Any competent manager can list symptoms. The tree forces you to trace the causal chain backward, in structured if-then logic, until you reach the real root causes rather than convenient ones. An effective Problem Tree does two things: it identifies the critical root causes of the adverse effects you're observing, and it provides the logical rigour to substantiate that identification. Without the second part, the first is just opinion. The Conflict Resolution Diagram handles why you're not already doing what the diagnosis suggests. Conflicts can be resolved three ways: imposed by power, compromised so neither side gets what it wants, or crafted so both sides are fully satisfied. The third route is hard because parties rarely understand what the other side actually wants, and often don't fully understand their own requirements either. The diagram doesn't represent reality. It represents assumptions about reality. Most significant conflicts are founded on mistaken assumptions. Expose the assumptions, find the ones that don't hold, and the conflict dissolves. Resistance to change almost always results from people's concern for their own welfare, dressed as rational objection. This is what [[Psycho-Logic]] describes as identity protection. The diagram anticipates these objections before they surface in implementation. --- **The Future Reality Tree tests the solution before you commit.** Map what happens if the fix is applied. Find the negative branches, the places where the fix creates new problems. Prune them at the logic level before pruning them in the real world. The sequence matters. Why change, then what to change, then what to change to, then how. Each question answered honestly makes the next question answerable. Skip one and you're guessing. The four questions in order are a discipline against the gravitational pull of action, which is always toward question four. The pull feels productive. It usually isn't. ---