Strategy 24 (Plan All the Way to the End) presents a specific planning methodology: think backward from the endpoint. Not "What do I want to do?" but "What's the final state I need, and what must precede it?"
This is distinct from goal-setting (which names a destination) and distinct from strategic thinking (which identifies principles). Backward planning is a specific methodological approach to sequencing.
The principle: every outcome requires prerequisites. Every prerequisite requires its own prerequisites. By mapping backward from endpoint, you create a causal chain that must be executed in order.
Example: Your endpoint is "win contract." What's the prerequisite for that? "Client signs agreement." What's prerequisite for that? "Client commits verbally." What's prerequisite for that? "Client trusts solution." What's prerequisite for that? "Client sees proof it works." Working backward, you've identified the sequence: 1) Proof, 2) Trust, 3) Verbal commitment, 4) Agreement.
This is different from forward planning ("First I'll do X, then Y, then Z"). Forward planning is sequential but loose. Backward planning is causal—each step must precede the next or the chain breaks.
Forward planning asks "What should I do first?" This invites do-whatever-you-can thinking. You execute Phase 1, see what happens, then plan Phase 2. This is reactive.
Backward planning asks "What must be true for the outcome to occur?" This is prescriptive. You work backward from necessity.
Example: A startup wants "become market leader." Forward: "Let's build product, get customers, scale." Backward: "What must be true for market leadership? Network effects. What creates network effects? Critical mass of users. What creates critical mass? Something so useful people must use it. What creates must-use? Solves a pain nobody else solves." Now you're working from necessity instead of assumption.
Forward planning assumes you know what matters. Backward planning discovers what matters by working from outcome.
1. Define the endpoint clearly. Not vague ("be successful") but specific ("client signs NDA, agrees to pilot, commits budget.") The more specific, the more backward-planning works.
2. Identify the direct prerequisite. What must be true immediately before the endpoint? Not "I'll be great at sales"—specific fact like "Client must believe solution reduces their costs by 30%."
3. Recursively work backward. For each prerequisite, ask what must precede it. Keep asking until you reach something you can actually control right now.
Example in negotiation:
Now you have a causal sequence instead of guessing.
Often, working backward reveals that you're missing a prerequisite you didn't anticipate.
Example: "I want promotion." Backward:
The backward chain reveals: promotion isn't about being good at current job (you already assumed that). It's about visibility of added value. This insight came from working backward.
Creative Practice → Narrative Structure Writers use backward planning naturally: start with ending, work backward to understand what must happen to make that ending inevitable. Narrative Architecture teaches this—the ending determines the beginning.
Psychology → Outcome-Oriented Thinking In therapeutic contexts, backward planning is outcome-focused therapy: define the desired state (no anxiety, stable relationships, purposeful work), then work backward to current moment and identify prerequisites for that state.
Diagnosis: Define your actual endpoint, not your aspirational one. ("Get meeting with CEO" is endpoint; "become influential" is not.)
First backward step: What must be true immediately before that endpoint? Be specific.
Recursion: For each prerequisite, ask what must precede it. Write it down—don't trust memory.
Stop point: Stop when you reach something you can do this week.
Verification: Once you have the chain, verify each step actually causes the next. Weak links break the whole chain.
Execution: Execute in reverse order—earliest prerequisite first.
Example in career:
Execute from bottom up. The project -> demonstrates leadership -> gets you team -> lets you prove management -> positions you for division lead.
R.G.H. Siu's Craft of Power (1979) names the same backward-planning logic this page describes, in the specific context of conflict.
The Chinese Communist maxim Siu opens the chapter with: "ta-ta, t'an-t'an — fight-fight, talk-talk."siu1 Conflict and negotiation alternate. The operator who plans only the fighting and figures out the talking when it arrives has skipped the prerequisite. "What is essential is your being sufficiently well buttressed to undergo the particular exchange with all of its rules and traditions and come out ahead in your own clearly defined objectives."siu2
Read the structural move. The endpoint is the post-conflict state — the shape of the eventual settlement, the terms the operator will hold after the dust clears. The fighting is one of the prerequisites for that endpoint, not the endpoint itself. Plan from the projected peace backward, not from the available weapons forward.
Siu walks through the failure mode. "Do not go into a negotiation, therefore, unless you have something under your control that the other side wants very much. If you do not, you should develop it ahead of time. Some of the stronger nations have invaded or bombed territories to possess the bargaining chips of military withdrawal and bombing cessations. Some of the richer nations have driven the opposition into financial chaos in order to possess the bargaining chips of financial assistance. Some of the corporations have held back on increasing health benefits to the workers which they can afford in order to give in at the negotiations later on."siu2
Read each example as backward-planning at scale. The operator works backward from the negotiation table. What concession is the operator going to make? That concession must already be created and held in reserve. What pressure is the operator going to relieve? That pressure must already be built up and applied. The military invasion is a prerequisite for the eventual withdrawal-as-concession. The financial squeeze is a prerequisite for the eventual financial-assistance-as-concession. The held-back health benefits are prerequisites for the eventual concession-at-the-bargaining-table. "You cannot negotiate unless you have something to negotiate with."siu2
Siu's instruction on when to switch from confrontation to negotiation completes the loop:
"Your moves toward cessation of active confrontation should be initiated as soon as you feel that the course of events have assured high probability of your obtaining more than your minimum objectives at the negotiation table."siu3
The operator is not asking am I winning the fight? The operator is asking have I built up enough material at the table to walk away with more than my minimum? Conflict is a means of building negotiation-material. The negotiation is where the material gets cashed in. The peace is where the operator has to live.
The page above is methodologically clean: define the endpoint, identify the prerequisite, recurse, find what you can act on this week. Siu's Op#70 specifies one of the most operationally important applications. When the endpoint is living in a peace settlement, the prerequisites include (a) creating bargaining chips you can give up, (b) building pressure you can relieve, and (c) timing the cessation of fighting to the point where your negotiation material exceeds your minimum-objective need. Forward-planning from "we should fight them" makes none of this visible. Backward-planning from "what do I want the peace to look like" makes all of it explicit.
Most people fail because they don't understand prerequisites. They want outcome Z but skip prerequisite X. They wonder why things don't work. Backward planning forces you to confront prerequisites. You can't skip them; the chain breaks if you do.
What's one outcome you want but haven't achieved? Work backward from it. What's the immediate prerequisite you're actually missing?
Where are you trying to skip a prerequisite? What would happen if you actually executed the missing step first?
What outcome could you achieve by working backward from it instead of forward-planning toward it?