System Thinking · Book Summary

Book Summary: Thinking for a Change

Mohit Saini · 12 Nov 2026 · 9 min read

Book Summary: Thinking for a Change

Most books on the TOC Thinking Process are written for people who already know the trees. Thinking for a Change: Putting the TOC Thinking Processes to Work by Lisa J. Scheinkopf (St. Lucie Press / APICS, 1999) is different. It is a practitioner’s handbook. It explains each tool step by step, with stories from factories, distributors, schools and even the author’s own kitchen table.

Lisa Scheinkopf worked with Dr. Goldratt at the Goldratt Institute on developing and refining the Thinking Processes, and later taught them as a consultant for many years. What I like most about the book is that it treats the Thinking Processes not as diagrams to be drawn, but as a way of learning: a disciplined way to surface, question and change our own assumptions.

The book is in three parts:

  • Part One: the TOC view of a system, and the two kinds of logic behind every tool;
  • Part Two: the five application tools, one chapter each;
  • Part Three: how the tools combine into a full analysis, and how to present a problem without putting people on the defensive.

Part One: see the whole system first

The book opens with a simple exercise. Imagine you are showing a new employee around your company. You walk through Sales, Customer Service, Accounting, Purchasing and finally the shop floor. At every stop people describe “the constraint”, and every one of them describes a problem in their own function.

Nobody is lying, but nobody can see the whole. The advice the author borrows from her colleague John Covington is short:

“Make the box bigger!” (1)

Look at the organisation from 40,000 feet, as a flow from inputs to outputs, and ask what limits the rate at which the whole system achieves its goal.

From there the book classifies constraints into three kinds:

  1. Physical: a resource, a market or a supplier that limits throughput.
  2. Policy: a rule or measure that stops the system from improving.
  3. Paradigm: the belief that makes us create and follow that rule.

Paradigms cause policies, and policies decide where the physical constraints sit and how badly they are managed.

The example that stayed with me is a high-tech electronics company whose constraint was its software design engineers. When the team watched them work, the engineers were spending only about half their time on design work. The rest went into data entry, copying, faxing and long meetings. The policy was “the engineer does every task in the engineering job”. The paradigm behind it was that one person doing all the tasks is the most efficient way. Off-loading that work, and later starting an apprenticeship programme instead of hiring only degree holders, raised the constraint’s capacity without hiring a single engineer.

The author applies the same Five Focusing Steps to her daughter’s homework, which shows how general the logic is.

Two prerequisites come before any improvement effort:

  • define the system and its purpose;
  • agree on its fundamental measures.

When these are unclear, as she finds in many non-profits, people end up improving the numbers that are easy to count rather than the purpose.

Put on your learning hat

Before any tool, the book asks for a change in mindset. From school onwards we are rewarded for having the right answer, so we defend our proposals instead of testing them. The Thinking Processes only work if we turn our exclamation marks into question marks.

The author suggests three first steps:

  1. Formulate the question you are trying to answer.
  2. Choose the tool that suits that question.
  3. Put on your learning hat. If you already know the answer, don’t bother with the tools.

Two kinds of logic

Every tool in the book rests on one of two thought patterns.

Sufficient cause (if… then…). One thing exists, and so another must exist. The arrow between cause and effect is where hidden assumptions live, and hidden assumptions are the source of most disagreements and failed plans. The book’s key advice is to try to prove yourself wrong, not right.

To check a cause-and-effect claim, the book uses the Categories of Legitimate Reservation:

  • Clarity: is it understood?
  • Entity existence: does it really exist?
  • Causality existence: does this cause really lead to this effect?
  • Additional cause: is something else also causing it?
  • Cause insufficiency: what else must exist alongside the cause?
  • Predicted effect: if the cause is real, what else must we see?

The examples here are memorable:

  • A hotel lamp “that doesn’t work” turns out to be unplugged. Check that the problem exists before solving it.
  • A manufacturer blames its parts shortages on late vendors. The shortages only happen when late deliveries combine with its own policy of ordering just in time, so part of the problem is in its own hands.
  • An electronics distributor blames falling sales on a price rise. It then finds customers leaving for more expensive competitors, because of relationships and better service. The predicted effect showed that price was not the main cause.
  • The author’s own family moved to a new state after looking only for evidence that the move was right. Less than three years later they moved back.

She also gives a useful guideline on how hard to check. The higher the risk, the more you check. And when everyone agrees immediately, or everyone is arguing, that is exactly when to look hardest for hidden assumptions.

Necessary condition (in order to… we must…). These are the requirements, rules and laws we believe stand between us and a goal. The book shows that many of them are not real necessities at all. The nine-dots puzzle makes the point: you fail it only because you assume a boundary that doesn’t exist.

Part Two: the five tools

The author presents the tools in the order they are easiest to learn, not the order they are usually taught.

Tool Logic Question it answers
Transition Tree Sufficient cause What exactly do we do, step by step, and what should each step achieve?
Future Reality Tree Sufficient cause Will this idea achieve what we want, and what could go wrong?
Current Reality Tree Sufficient cause What single cause lies behind many of our problems?
Evaporating Cloud Necessary condition What conflict keeps this problem alive, and which assumption breaks it?
Prerequisite Tree Necessary condition What obstacles stand in the way of an ambitious goal, and in what order do we overcome them?

Transition Tree. Plans are usually lists of things to do. A transition tree adds the reason for each step: the new condition that each action creates, which makes the next action possible.

The book’s example is a group of managers planning meetings to “change the plant culture”. They were busy writing the agenda without ever saying what they wanted employees to do once the meetings were over. Another reader planned a complaint letter to an expensive resort by first deciding what he wanted the management to do after reading it. He got a $500 credit.

Future Reality Tree. This tool tests an idea (an injection) before it is implemented. Connect it to the objectives, look for undesirable side effects and block them, and add reinforcing loops so the improvement sustains itself. It is also a constructive way to tell a colleague that you have concerns about their idea.

Current Reality Tree. Start with five to ten undesirable effects, connect them by cause and effect, and look for the few causes that drive most of them.

In the Display Manufacturing case, a maker of display racks wanted to help its customers sell more in stores. The tree pointed to stores hiring low-skilled staff to keep costs down, something the company couldn’t change. The cause-insufficiency check changed the picture: the problem only appeared because putting the displays together needed more than minimal skill. That pointed to the company’s own product design, which it could change.

Evaporating Cloud. This is the most widely used tool and, as the book says, the easiest to learn. The author says she has never met a problem that couldn’t be expressed as a conflict, and has only seen problems people were unwilling to solve. Map the five boxes, surface the assumptions under each arrow, and find the one that isn’t valid in your situation.

My favourite story in the book is about the name itself. Many consultants, including the author, had started calling the tool a “dilemma tree” because “evaporating cloud” sounded unprofessional. Dr. Goldratt objected, because the name honours Richard Bach, whose novel Illusions has characters thinking storm clouds away. So she drew a cloud of the dilemma on a napkin at dinner. Working through the assumptions, she realised the obstacle was not Goldratt’s ego but the consultants’ own discomfort; clients had no problem with the name. She went back to calling it the evaporating cloud.

Prerequisite Tree. For goals that seem out of reach, list every obstacle and the intermediate objective that overcomes it, then sequence them. The book uses the Apollo moon landing to show the kind of ambitious goal the tool is made for. It is the tool for when all you can see are the reasons something can’t be done.

Part Three: putting the tools together

The full analysis links all five tools to answer the three questions of change:

  • What to change? Current Reality Tree, then the core conflict as a cloud.
  • What to change to? Future Reality Tree.
  • How to cause the change? Prerequisite Tree, then Transition Trees.

The author warns against one paradigm that grew from the way the tools were first taught: that you must always do the full sequence. Use only the tools you need to answer the questions you still have.

The last chapter, the Communication Current Reality Tree, is very practical. To present a problem to someone who feels responsible for it, begin with the objective you both share, show the conflict that both of you are caught in, and only then walk through the problems. The issue becomes the system’s, not the person’s.

My takeaways

  1. The Thinking Processes are a learning method, not a diagramming exercise. Their real output is a changed assumption.
  2. Try to prove yourself wrong. The predicted effect check is the scientific method applied to everyday management.
  3. Most constraints are policies, and most policies come from paradigms. Find the belief and you find the leverage.
  4. Start with the question, not the tool. You rarely need all five.
  5. Disagreement is information. A reservation from a colleague is a gift that points to an assumption you should check.

If you have read It’s Not Luck and wondered how to actually build the trees, this is the book I would recommend next.

Notes

  1. Advice of John Covington, quoted by the author in Chapter 1.

Summary of Thinking for a Change: Putting the TOC Thinking Processes to Work by Lisa J. Scheinkopf (St. Lucie Press / APICS, 1999), written in my own words. The Thinking Processes were developed by Dr. Eliyahu M. Goldratt.

Go deeper

Mohit Saini

Strategy, supply chain & sales transformation consultant. About · Book a discussion