Arc — the illustrated introduction (draft v1)

Beads reasoncommons-bnl.6. Inputs: evaluation, voice guide, Co-Star teardown, Dettmer's The Logical Thinking Process (library/logical-thinking-process-dettmer/), the current pieces (explainers/_process/*/article.md, second-renaissance-plain). Story first, form second.

The reader

Someone who runs or cares about something complex — a team, an organization, a movement — and has felt that effort isn't adding up. Smart, busy, not a management-science reader, often on a phone. Arrives from a link, a talk, or the Second Renaissance forum. Has never heard of the Theory of Constraints or the Logical Thinking Process (LTP).

What they should be able to say afterwards

1. Most effort in a system doesn't move the goal; one constraint does, and it is rarely where people are busiest.
2. You can't agree on the constraint by arguing. You can by drawing the cause and effect and checking each arrow with a few fair questions.
3. Five questions any real change has to answer (what should be happening, why isn't it, why hasn't it been fixed, will the fix work, what do we do first), each answered by a differently shaped tree.
4. A group's thinking only accumulates if each claim has an address, and AI now makes it affordable to give it one without making contributors do the filing.

1–3 are the method (the book). 4 is why Reason Commons exists (the 2R story).

Shape: two short series, cross-linked

The evaluation found two stories in one page. They want to be separate, each short enough to finish in one sitting (Co-Star's eight chapters take about fifteen minutes).

• Series A — Thinking in trees (the LTP basics). Follows the book's order. Running example: Ashfield clinic (already built, composite, arithmetic checkable). 10 chapters in two parts.
• Series B — Where does the thinking go? (the Second Renaissance story). Motivation for Reason Commons. Running character: Maren. 6 chapters.

Either can be read first. The explainers index lists both, B first for readers coming from the Second Renaissance, A first otherwise — see open question 1.

Cross-links: B4 ("give every claim an address") → A7 (the goal tree); B5 (the dilemma) → A9 (the cloud); A10 → B as "the method on a real movement".

Series A — Thinking in trees

Each line: number · title — teaser (the chapter's one point) · source · kept/reshaped from.

Part one · Constraints

1. A clinic with sixty people waiting — Every system exists to achieve a goal, and how much of it gets achieved is set by one part: the constraint. · Dettmer ch. 1 (the system's goal, the concept of system constraints) · reshaped from The Wrong Queue opening: the clinic, Maria's desk, twenty a day for four years. Figure: five stations with their daily capacities; output set by the smallest (animated: patients flowing, piling before the doctor).
2. The wrong queue — The constraint is not where people are busiest; improving anything else just makes a longer queue somewhere. · Dettmer ch. 1 (TOC principles) · The Wrong Queue: "Where do you put the one hire?" + "Everybody's busy". Figure: the one hire at the front desk vs the doctor (animated: the queue moves, output doesn't).
3. Squeeze before you spend — First get everything you can out of the constraint and make everything else serve it; only then pay to expand it. · Dettmer ch. 1 (the five focusing steps) · The Wrong Queue: "Don't spend the money yet" (the doctor's day, admin recovered). Figure: the doctor's day as a bar, admin removed (before/after).
4. The constraint moves, and it's often a rule — Fix one constraint and another appears; the stubborn ones are usually policies, not machines or people. · Dettmer ch. 1 (the five focusing steps: repeat; policy constraints), ch. 8 · The Wrong Queue: "It moves" + "Invisible rules". Figure: the constraint migrating along the stations (animated).

Part two · Thinking in trees

5. Five people, five answers — Smart, well-meaning people disagree about causes because they can't see each other's reasoning; drawing it is how you make it visible. · Dettmer ch. 1 (the logical tools), ch. 2 (purpose) · The Arrows Nobody Checks opening + "Diagrams aren't enough". Figure: five heads, five arrows to five different causes.
6. Eight fair questions for any arrow — A cause-and-effect diagram is only as good as its arrows, and there are eight questions anyone may ask of one without it being rude. · Dettmer ch. 2 (Categories of Legitimate Reservation) · The Arrows Nobody Checks: "The rules" + "The social part". Keep the plain-language questions ("Do I understand you?", "Is that a claim at all?", "Is that cause enough on its own?" …). Figure: fire needs fuel, heat and oxygen (cause insufficiency). Possibly split into two chapters if eight questions won't fit in 500 words — see open question 3.
7. What should be happening? The goal tree — Start with the goal, the few things that must be true for it, and what each of those needs; necessity, read top-down. · Dettmer ch. 3 (Intermediate Objectives map) · Five Shapes §1. Figure: the clinic's goal tree (animated: grows from the root). This is also where a tree is first explained as a thing with addresses.
8. Why isn't it happening? The current reality tree — The many things going wrong trace back through cause and effect to a few root causes. · Dettmer ch. 4 · Five Shapes §2. Figure: undesirable effects at the top, arrows converging on one root cause.
9. Why hasn't somebody fixed it? The cloud — A problem persists when fixing it seems to cost something else we need; name the assumption behind that conflict and it can often be dissolved. · Dettmer ch. 5 (Evaporating Cloud) · Five Shapes §3. Figure: the five-box cloud, the assumption cracking.
10. Will it work, and what do we do first? — Before acting, check the fix for side effects (future reality tree), then work out the obstacles and their order (prerequisite and transition trees). · Dettmer ch. 6–7 · Five Shapes §4–5 + "Five questions, five shapes" + "At Ashfield". Ends on the five questions as one picture, then the hand-off to Series B: "Here is the method used on a real movement."

Lineage — Goldratt, Dettmer, the name "Logical Thinking Process", Minto where relevant — is stated in A1 (one line) and A5, where it is the subject.

Series B — Where does the thinking go?

1. The comment that vanished — Maren posts a good suggestion, nine people reply, and a year later nothing the movement believes has changed. · Figure: thread-live → thread-lost as one animation (post arrives, replies gather, it greys into the run). Movement introduced after the story, in two plain sentences.
2. People learn, groups don't — Individual understanding compounds; a group's shared understanding keeps resetting, so it has the same conversation again and again. · The research circle + compounds. Figure: three rise-and-fall peaks beside a climbing staircase (animated), labels on the lines.
3. Nowhere to put it — Forums file by date and papers by paragraph, so a single claim has no address, and what you can't point at you can't improve. · "No address". Figure: no-address, redrawn.
4. Give every claim an address — A tree of claims gives every claim, and every link between claims, a place you can point to; Maren's suggestion now has somewhere to land. · "A tree of claims" + "A destination" (with the logic fixed: her claim as a missing sub-condition). Figure: the 2R goal tree with Maren's card landing (animated). Links to A7.
5. Why nobody does the filing — Structure takes effort, which makes it look like a choice between easy and cumulative, but that rests on one assumption: that the person contributing has to do the filing. · "The catch" + "A dilemma", merged into one chapter. Figure: the stairs; the assumption in one line, not a full cloud diagram. Links to A9.
6. Talk first, file later — AI reads the conversation afterwards and proposes where each point belongs; people decide what goes in; and the tree can point the forum back at what's already been said. · "Separate the acts" + "It works the other way, too". Figure: a sentence travelling conversation → AI → people → tree → back (animated). Must show a worked example (a real thread and three proposed placements) or say plainly that it's a prototype. Close: the honest status line, the invitation ("find the claim you disagree with"), and the gardeners image only if it answers a stated objection.

Kept, reshaped, dropped

Scale

16 chapters × ~300–500 words ≈ 6,500 words total, against ~10,500 in the five current pieces. Each chapter one idea, one to three figures, at most one animation.

Open questions for Rufus

1. Two series, or one? Two is the recommendation (the evaluation's finding). The alternative is one series where B is a four-chapter coda to A. Which comes first on the index?
2. Running example for A. The clinic is built and concrete. The alternative is a team or movement closer to the reader, which would tie A to B but lose the clean arithmetic. Recommendation: keep the clinic.
3. Series A length. Ten chapters. Chapters 3 and 4 could merge ("Squeeze before you spend; the constraint moves"), and 6 could split into two. Is ten about right?
4. Where AI enters Series A. Currently not at all; A is the method, B is the AI turn. An alternative is a short A11 on "why this is suddenly practical".
5. Titles. "Thinking in trees" and "Where does the thinking go?" are working titles.