STATE MATRIX

Game UI State Matrix

Define what players see and can do when a system changes state.

Why it matters

Players rarely see a system in its perfect state. Data loads, connections drop, inventories empty, and actions fail. Each of those states needs a clear message and a sensible next action. A state matrix makes sure every situation is designed rather than left to whatever the code happens to show.

Workflow

Make columns for state, entry trigger, visible signal, available action, focus target, recovery, and exits. Include initial, loading, empty, partial, stale, error, and success as relevant. Describe precedence when states overlap and guard against repeating a destructive or state-changing action.

Worked example

A crafting panel keeps usable cached recipes visible during a refresh, labels stale quantities, and gates crafting when required materials cannot be verified. If refresh fails, show Retry and retain the selected recipe. If the recipe was removed, move focus to another recipe or the empty state.

Try it

Build a matrix for one panel. Simulate opening offline, losing connection after selection, and receiving a delayed success. Confirm each transition has a player-facing signal and a valid next action.

Common mistakes to avoid

Designing only the success state. Using a spinner with no explanation for long waits. Showing an error without a way to recover. Letting players repeat a purchase or other important action while the first one is still processing. Losing the player’s selection after a refresh.

Use it in your portfolio

Show the matrix next to two or three of the state screens it produced, such as stale, error, and empty. This shows reviewers you can handle the unglamorous parts of UX that make a game feel reliable.

Keep going

Pair this with the Player Flow Worksheet and the Motion Spec, or practice on a real brief in the Bi-Monthly Challenges. Want feedback from working game UX/UI designers? Explore the UI Peeps Masterclass.

Copyright 2026