Move guide
R · Relations
Change how the parts connect.
Choose a move in the practical Guide →Explore the moves and parts
- RESEQUENCEMake the order of events explicit, because the same ingredients in a different sequence produce a different outcome.Expand branch →
- RECOMPAREChange the baseline or comparison class behind a judgment, because every evaluation secretly depends on what it is being compared to.Expand branch →
- REDEPENDMap which tasks must come before which, so the real bottleneck and critical path stand out from the pile of visible work.Expand branch →
- REHIERARCHIZESort your ideas into their proper levels (goals above functions above mechanisms) so you stop comparing things that were never peers.Expand branch →
- RECAUSALIZEReplace 'these things go together' or 'this person is to blame' with a testable mechanism of what would change what.Expand branch →
- REFLOWTrace how something scarce (money, attention, information, work) actually moves through the system, so leaks, queues, and overloaded handoffs become measurable.Expand branch →
- RECONSTRAINTState what you're improving, what must not get worse, and what limits you're under, so the real feasible options become explicit.Expand branch →
- RENETWORKDraw the problem as nodes and connections, because indirect paths, hubs, and bridges explain behavior that straight-line thinking cannot.Expand branch →
- RELOOPTrace how an outcome feeds back into its own causes, so you can see why the problem keeps recreating itself after every fix.Expand branch →