Underneath, this is the same shape as juggling a project: every move leaves the system in some state, a few states are disasters, and you have to find a path that never lands on one. The biggest trap is forgetting the boat has to come back, and that 'wasted' return trip doubles your moves. Real plans have that same hidden step.
The habit that wins these is writing down where everything stands after each move and checking it against the rules, instead of trusting your gut. That exact discipline shows up in software deployments, surgical checklists, and any rollout where a wrong order breaks things. For more on planning like this, see Problem Solving.