Five Shapes — script v1
Five Shapes — script v1
Stage 1 of 3. Pure narrative. No visual direction. Judged as writing only.
Answers: what the Logical Thinking Process actually is. This is where the method is finally named.
Sources: Dettmer ch3 (IO Map), ch4 (CRT), ch5 (Evaporating Cloud), ch6 (FRT), ch7 (PRT and the retirement of the Transition Tree).
~1,200 words.
The clinic now has something it didn't have: a map of why it is stuck, that five people built and none of them could break.
It says the ten-minute appointment rule is doing most of the damage. Ten minutes was introduced to see more people. It means histories get re-taken, notes go unwritten, and a third of patients come back a second time for the same complaint — which consumes the appointments the rule was created to protect.
Good. Now what?
Because why are we stuck is only one of the questions you need answered, and it isn't even the first one.
Here is the first one, and skipping it is the most expensive mistake in this whole business.
What should be happening?
Not what's wrong — what does success actually look like, and what must be true for it to happen at all? Dettmer calls the failure to ask this the Nero syndrome: fiddling while Rome burns. Rearranging deck chairs with great diligence.
Because until you have written down what the clinic is for, "the problem" is whatever irritates whoever is talking. Every person measures the place against a private, unstated idea of what it should be, and then argues about the gap. You cannot have a useful argument about a gap when nobody has agreed where the far side is.
So: the goal. Then the three or four things that are non-negotiable for reaching it — not things you'd like, things without which it simply cannot happen. Then what those rest on.
It is an unglamorous document. It is also the ruler. Nothing downstream means anything without it.
Why isn't it happening?
Now the symptoms. Waits too long. Staff exhausted. Same patients returning. Referrals late.
The instinct is to fix these, one by one, and that instinct is the whole trap. They aren't four problems. They are four fingerprints, and if you treat the fingerprints you will be back here in a year with the same four.
So instead you work backwards. What would have to be true for waits to be this long? And what would have to be true for that? Keep going, and the four symptoms start converging on a much smaller number of causes — often one or two, sitting somewhere nobody was looking.
That convergence is the point. If a dozen complaints trace back to two causes, then most of what's wrong is fixable with two changes rather than a dozen. The tangle was never as big as it looked.
So why hasn't somebody fixed it?
This question is doing more work than it appears to.
The ten-minute rule has been unpopular for years. Everyone can see the damage. Nobody has changed it. When a problem is well known, obviously harmful, and still there, that is information: something is holding it in place.
Usually a conflict. Not a personality clash — a structural one, where the thing hurting you is protecting something else you also need.
Draw it out. The clinic needs to see enough people to serve its population, and it needs each consultation to be good enough that people don't come back. Ten-minute slots serve the first. Longer slots serve the second. Both requirements are real. Both actions are reasonable. They point in opposite directions, and so nothing moves.
Then comes the move that makes this tool worth the trouble. You do not pick a side. You ask what has to be true for these two to be genuinely opposed — and you write those assumptions down.
That consultation length is the only lever on quality. Is that true? Or does a consultation overrun because the history was taken twice and the notes weren't there — in which case the fix isn't longer appointments, it's the notes.
Break one assumption and the conflict doesn't get resolved. It stops existing. That's why Goldratt called it an evaporating cloud.
Will it actually work?
You have an idea. Before you spend a year on it, walk it forwards.
If we do this, then what? And if that, then what? Follow it until it either arrives at the thing you wanted or doesn't. This is where a surprising number of good ideas quietly die, on paper, for free.
And then the question people skip because they don't want the answer: what else does it do? Every change enters a system of interdependencies, and the system talks back. The fixes in this story all worked on the thing they targeted and broke something adjacent.
You are looking for those breakages now, while they are hypothetical and cost nothing.
What do we do on Monday, and in what order?
Ideas are not solutions. An idea becomes a solution when it is implemented and doing what it was supposed to do, and the road between those two states is where most good ideas are buried.
So: what stands in the way? List the obstacles honestly — money, skills, permissions, sequence, and the fact that a change obvious to you is a threat to someone whose numbers currently look fine. Then, against each obstacle, the thing that would have to exist to get past it. Then put them in the only order they can happen in.
Not a plan of tasks. A plan of obstacles.
Five questions. Five differently shaped answers.
What should be happening — a hierarchy of necessity: the goal, and what it stands on. Why isn't it — a web of cause and effect, symptoms at the top, roots at the bottom. What holds it in place — a small diagram of a conflict, and the assumptions underneath. Will it work — the same cause-and-effect logic, run forwards. What do we do — obstacles, answers, sequence.
Together they are called the Logical Thinking Process. Goldratt built them; Dettmer spent decades teaching and refining them.
That's it. That's the method. It has a reputation for being forbidding, and it is really five questions asked in a particular order, with the arrows checked.
There were six.
The sixth was a step-by-step implementation map, and in the 2007 edition Dettmer largely removed it — writing that over ten years of teaching he had found it "the least valuable of the Thinking Process tools for nearly all practitioners."
That is worth pausing on. The person who spent his career on this method looked at his own toolkit and took a tool out of it.
You should trust the remaining five more, not less, for that.
One last thing, and it is the thing that actually matters.
The diagrams are not the product. Nobody needs more diagrams.
What they do is convert reasoning from something happening privately inside a head into an object sitting on a table — where it can be read, tested, disagreed with in a specific place, and repaired. The tree is to thinking what written notation is to music: not the performance, but the thing that lets the performance be shared, criticised and improved by people who weren't in the room.
Which produces the property that makes any of this worth the effort. Claims get addresses. A vague unease about strategy becomes an objection to a specific node, which can be found, argued with, and fixed. Disagreement stops being weather and starts being work. And the map keeps what the argument concluded, so the same discussion doesn't have to be held again in March, warmly, from the beginning.
That is the actual promise. Not better diagrams. A group whose thinking accumulates.
Back at the clinic, someone has just noticed that if you fix the notes, the ten-minute rule might not need changing at all.
Somebody else thinks that's wrong.
For the first time, they can find out.