M · MAP
R · Relations
Change how the parts connect.
How does it fit my situation?
Choose a named move in this branch to open its working page and checks.
- Resequence
Make the order of events explicit, because the same ingredients in a different sequence produce a different outcome.
- Recompare
Change the baseline or comparison class behind a judgment, because every evaluation secretly depends on what it is being compared to.
- Redepend
Map which tasks must come before which, so the real bottleneck and critical path stand out from the pile of visible work.
- Rehierarchize
Sort your ideas into their proper levels (goals above functions above mechanisms) so you stop comparing things that were never peers.
- Recausalize
Replace 'these things go together' or 'this person is to blame' with a testable mechanism of what would change what.
- Reflow
Trace how something scarce (money, attention, information, work) actually moves through the system, so leaks, queues, and overloaded handoffs become measurable.
- Reconstraint
State what you're improving, what must not get worse, and what limits you're under, so the real feasible options become explicit.
- Renetwork
Draw the problem as nodes and connections, because indirect paths, hubs, and bridges explain behavior that straight-line thinking cannot.
- Reloop
Trace how an outcome feeds back into its own causes, so you can see why the problem keeps recreating itself after every fix.