Reverse the Arrow

When reasoning forward produces too many branches, begin at a concrete endpoint and work backward. Ask what must have been true just before it, preserving alternative routes and distinguishing necessary conditions from guarantees.

Endpoint → immediately before → prerequisites → alternatives → check forward.

Reverse the Arrow changes the direction of reasoning. Start from a desired result or a specific failure and ask what conditions would need to precede it. Repeat only far enough to clarify the live question. Label necessities, possible routes, and unknowns separately: a plausible backward story is not proof that the endpoint happened or will occur.

Try this when…

Every possible first step creates ten more branches.

What would have to be true before that result is possible?

Could looking backward make the missing dependency easier to see?

I'm worried we're treating a familiar route as the only route.

What you can use it for

Expose prerequisites

Separate necessary conditions from optional tasks in a large possibility space.

Inspect a failure pathway

Work backward from a possible failure while keeping rival routes and uncertainty visible.

Clarify creative structure

Use an ending to explore what earlier information or development it requires.