W8.05.3Simplification must preserve decision rightsdesign

Simplification must preserve final decision rights

Aliases: decision authority · agency preservation · assisted autonomy · decision rights

What it is

The correct division for simplification and auto-execution: the system takes over "how to execute," the player keeps "what to do and when." A simplified input still triggers the player's choice (pressing attack means I decided to attack; the system just executes it more reliably), rather than the system deciding for the player (auto-battle choosing targets). Preserving decision rights is the line between accessibility assist and "playing for you": assists remove execution barriers and keep agency—the player's intent still drives what happens in the game.

Why it happens

Decision rights form the core of player agency. The psychological essence of game experience is "my choices produce perceivable consequences"—competence (my actions work) and autonomy (the actions are mine) both depend on the decision chain's integrity. Assist design erodes decision rights in hidden forms: over-strong aim assist swallowing target selection (lock-on decides who gets shot), auto-combos erasing tactical choice of which move (the system outputs its optimal sequence), auto-pathing letting the algorithm decide the route. These lower the execution threshold while demoting the game to watching; participation drains, and long-term this becomes another form of quitting ("nothing I press matters"). The check standard for decision-preserving assist: with assists on, does every player input still correspond to a consequential choice? If yes, the assist only improved execution reliability; if inputs became a "next scene" button, agency has been removed.

Where it stops holding

Decision preservation is a spectrum, not binary: full preservation (assist only tunes execution parameters), partial sharing (system proposes, player confirms—auto-aim locks but the player decides when to fire), minimal preservation (the player only starts and stops, as choosing an auto-path destination). The right position varies by game type and content layer: narrative-layer decisions must be fully preserved (story choices are a narrative game's substance), execution-layer decisions can be heavily assisted, and strategy-layer assistance needs care (auto-loadouts erasing build choice damage the RPG's core loop). Players also stratify in what they want: some want assist only where they stall (playing the rest themselves), others want comprehensive assist (focusing on story)—per-item configurable assist matches individual differences better than global tiers. Preservation also does not forbid defaults—default assist + anytime off + decision rights kept is the best starting point for most who need it.

Applying it

  • Run a decision-rights audit per assist feature: list what the assist takes over, marking execution (transferable) versus decision (must be kept); assists that swallow decisions need redesign or a confirmation step.
  • Under assists, give clear feedback at decision points (auto-aim's lock-on target visible, auto-path's destination confirmable) so players always know what they have authorised.
  • Verification: observe assisted players' decision-behaviour frequency (actively choosing targets, switching strategies) versus unassisted play. Near-equal frequency means decision rights held; a marked disappearance means the assist overreached—return the swallowed decisions.

Related

  • Same group: W8.05.1 Action simplification merges multi-step operations into one input · W8.05.2 Auto-execution lets players skip precision and play the strategy · W8.05.4 Over-automation makes some players feel the core play was taken
  • Nearby: P2.02 Autonomy and sense of control · W8.05 Action simplification and auto-execution · W8.04 One-handed and switch access
  • Search terms: player agency · assist mode design · decision making · accessible autonomy

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/W8.05.3