Skip to content
marigold quay
Open menu
Priorities

Your Old Rotation Has New Owners

Your team reaches the next objective together, yet somehow arrives unprepared. The player who normally watches the flank is now carrying the objective item. The former initiator is covering the rear. Someone takes the familiar forward route, discovers nobody can support them,…

Your team reaches the next objective together, yet somehow arrives unprepared. The player who normally watches the flank is now carrying the objective item. The former initiator is covering the rear. Someone takes the familiar forward route, discovers nobody can support them, and retreats through teammates moving in the opposite direction. This is not necessarily a movement problem. When a team changes roles, its old rotation habits can survive longer than the responsibilities that made those habits useful. The solution is to plan how control passes between players, not simply where everyone should go.

Start by diagnosing the first moment the rotation becomes unstable. Review a failed move from the point where the team decided to leave, rather than from the final lost fight. Who stopped watching an entrance? Who moved before a teammate could replace their coverage? Who assumed someone else would scout? A useful diagnosis describes an observable gap: “We abandoned the upper passage before the rear player reached the central doorway.” That gives the team something it can change. “Our rotations are slow” does not explain whether the problem is hesitation, poor information, mismatched routes, or missing protection.

Role changes expose these gaps because players often associate duties with names rather than positions. If Maya has always checked the next area, teammates may keep waiting for her information even after she switches to a slower support role. Meanwhile, the new scout may assume that reaching the front is enough. Before planning routes, describe the jobs the move requires: gaining information, protecting the group during travel, holding an escape route, and establishing control at the destination. One player can perform several jobs, but none should depend on an unspoken assumption.

Build the rotation around three states: preparation, transit, and arrival. During preparation, the team gathers enough information to choose a route and decides what it can afford to leave behind. During transit, players preserve useful spacing and protect vulnerable teammates. On arrival, they claim positions from which they can contest the objective without immediately becoming trapped. This distinction matters because responsibilities can change during a single journey. The player guarding the departure point might become the last arrival, while the first player through the destination must temporarily protect the others instead of chasing an opponent.

The most useful planning technique is a conditional handoff: one player keeps a responsibility until a teammate confirms that its replacement is ready. Suppose a squad is moving from a lower courtyard toward an upper control point. The rear guard should not leave merely because the scout reaches the stairs. Instead, the scout reports that the landing is usable, the support player reaches a doorway covering the courtyard exit, and only then does the rear guard advance. The plan connects movement to a visible condition. It is more dependable than asking everyone to rotate after an arbitrary countdown.

Keep the language short enough to use during play. A planning note labeled s8 could read: “Scout checks landing; support holds exit; rear moves on confirmation.” The label is not the useful part; the sequence is. Agree on what confirmation means before the match becomes hectic. “Ready” might mean a player has reached cover and can watch the relevant approach, not merely that they are running toward it. Avoid lengthy scripts with many dependent steps. A good handoff plan identifies the current owner, the next owner, and the condition that allows the transfer.

Next, choose a primary route and one fallback based on the team's new capabilities. A lineup with less mobility may need a route offering intermediate cover, even if its fastest player prefers the open shortcut. A team whose information-gathering role has changed may need an earlier scouting step before committing to a narrow corridor. Compare routes by asking what happens if the group is interrupted halfway through. Can players stop safely? Can they support one another? Can they reverse direction without crossing an exposed area twice? The shortest path is not always the path that gets the team into useful positions soonest.

Plan the departure trigger separately from the destination. “Go to the next objective” leaves too much room for interpretation. A stronger call might be: “Leave when our forward player can cover the bridge, unless the side passage becomes contested.” That gives the group both a trigger and an exception. Where a game has timed objectives, work backward from the arrival position the team needs, allowing time for scouting and regrouping. Do not assume those allowances remain unchanged after a role swap. A different player may take longer to clear an approach or need protection while moving.

Give the team a recovery rule as well. If the scout encounters resistance before the rest of the squad commits, the answer might be to hold at the previous cover and assess the fallback. If contact occurs after most players have crossed, the answer may instead be to finish the move and secure the destination together. The exact choice depends on the game and situation, but the planning principle stays consistent: avoid having half the team retreat while the other half advances. Name a rally position that everyone can recognize, and make clear who calls a reset.

Test the revised rotation in a small number of attempts, changing one element at a time. First check whether coverage remains intact during the handoff. Then examine spacing and arrival order. Only after those work should you try to make the move faster. In a replay or post-round discussion, ask whether each player knew their responsibility at departure, during the crossing, and on arrival. A successful test need not end in a won fight. If the team reaches the destination with information, support, and a viable retreat, the rotation may have improved even when a later execution mistake loses the objective.

The goal is not to make every player follow a fixed route forever. It is to give a changing team a shared model that still works when familiar responsibilities move to different people. Diagnose the first uncovered responsibility, assign its owner, and define the condition for handing it over. Then choose routes and timing that fit the current lineup rather than the previous one. Once those decisions are explicit, rotations become easier to adapt: players can change where they go without losing track of what the team needs protected along the way.

Start a conversation

What are you planning?

Tell us what is on your mind, from a planning question to an idea for the publication.

Send a message

Partner features

Explore clearly marked collaborations related to celebrations.

esc
Rebuilding Rhythm Game Timing QuietlyPrioritiesResetting Turn Order After ReturnPrioritiesHelping a Friend Learn the Controls in a First SessionPrioritiesStockpile or Schedule? Planning Resources for a Survival TeamPrioritiesTest Your Team’s New Look Before Changing RolesPriorities