Reverse and Rearrange

Ask: what if the sequence were inverted, the roles were swapped, or the normal order were reversed?

Why it works

Most systems have an implicit sequence that feels natural — so natural that the reverse is never considered. Reversal breaks this by forcing the thinker to simulate the system running backward or inside-out. This is how "inverse" thinking works in design: starting from the desired end state and working backward identifies paths that forward planning misses.

How to do it

1. Map the sequence or structure of your process, product, or argument.
2. Reverse it entirely: last step becomes first, the provider becomes the receiver, the input becomes the output.
3. Ask: "What new possibilities does the reversed version create? What problems does it solve that the original version couldn’t?"
4. Also rearrange: reorder components and ask what changes.

Evidence

Backward reasoning and inversion are recommended heuristics in mathematical problem-solving and engineering design. The strategy of inverting a problem is associated with finding solutions missed by forward-thinking approaches. (mechanistic)

The Reverse and Rearrange lens is most productive for sequential processes; for highly interdependent or network-structured systems, simple reversal may not produce coherent alternative configurations.

Common mistake

Treating reversal as an exercise in identifying why the original order is correct — which defeats the purpose. Commit to the reversed version as a real scenario before evaluating it.