How do I keep a player’s turn from becoming a long sequence of tiny decisions?

Start by mapping one complete turn as a sequence, including choices that seem routine. For each step, note what the player chooses, what information they need, and what changes as a result. A decision may feel tiny because it has little consequence, repeats a choice already made, or interrupts a more important choice.

For example, as a hypothetical starting point, a turn might be: choose a location, choose an action, choose a target, choose how many tokens to spend, choose which token to spend, then choose whether to use a bonus. Don’t edit yet. First mark the steps where different options could meaningfully change the player’s plan, cost, risk, or expression of strategy. Those are candidates to preserve; the others deserve a closer look.

Combine steps when they are really parts of one decision and considering them separately adds handling rather than a useful trade-off. Ask: would a player reasonably want to reconsider the first choice after seeing the second? If not, you may be able to present both together as one selection. If the second choice changes the value of the first, keep them distinct—or show them together while making their consequences clear.

In the hypothetical turn above, if choosing an action automatically determines its target, those steps might become one choice: “Choose an action and its target.” But if the player can first choose an action and then compare several valid targets, that targeting decision may be strategically important. Combining choices should simplify the process, not hide what the player is giving up or make the options harder to compare.

Try grouping, deferring, or making routine choices automatic by default. Group related small choices into one prompt, such as “Choose up to two items to use,” rather than presenting a separate pause for each item. If a choice matters only after a later event, let the player decide then instead of asking them to predict it early. If a rule determines the outcome in most cases, consider using that as the default and asking only when the player wants to override it.

Using the hypothetical turn, suppose the player selects two tokens to spend one at a time, but the order does not affect anything. You could ask them to select both together. If order sometimes matters, make that exception visible: “Choose two tokens; order matters only when [condition].” That wording is a design placeholder, not a rule suggestion for every game. Check that any automatic default is understandable and doesn’t quietly remove a choice players care about.

Compare the old and revised turn maps using the same hypothetical situation. For each version, count the decision points, then note where a player pauses, asks what an option means, or changes an earlier choice. You can test this yourself or with willing playtesters; treat observations as clues, not proof that every player will respond the same way.

For instance, a revised map might read: 1. Choose an action and target. 2. Choose the resources to spend. 3. Resolve the action. 4. Choose whether to use the bonus. Ask whether the removed or grouped steps were genuinely redundant and whether the remaining choices still let the player pursue different plans. If a shorter turn makes choices unclear or removes an important trade-off, restore or clarify that decision. Record the change and the question you’re testing next.