WORKSHEET

Game UX Player Flow Worksheet

Map one player task before creating high-fidelity screens. Start with where players are, what they need to accomplish, and what tells them they succeeded.

Why it matters

Most confusing game menus aren’t ugly. They break because a step was never planned: Back lands somewhere unexpected, a full slot has no answer, or a cancel quietly loses the player’s choice. Mapping the flow first lets you find those gaps on paper, where a fix costs minutes instead of a rebuilt screen. It also gives programmers and QA a shared description of how the feature should behave.

Fill in the flow

Player goal [ ]; starting screen and state [ ]; device and input [ ]; available information [ ]; success signal [ ]. For each step record screen/state, player action, system response, next state and where Back returns. Add a separate row for each decision, alternate outcome, and recovery path.

Worked example

Equip a new item from the pause menu. Pause → Inventory → select item → Equip → confirm the slot changed. If the slot is full, show the current item and allow Replace or Cancel. Cancel returns focus to Equip and preserves the old item. Back from inventory returns to pause with Inventory focused.

Test your map

Trace the normal path, the blocked path, and an exit from the middle. For each, ask a peer to point to the next action and name what will happen after pressing it. Fix the first step where their expectation differs from the system response.

Common mistakes to avoid

Mapping only the happy path. Forgetting the state the player arrives in, such as mid-combat or from a notification. Leaving Back undefined, or sending it to the top-level menu instead of the previous screen. Mixing screens and modal pop-ups in the same level of the map. Jumping into visual design before a peer has walked through the flow and agreed on what each button does.

Use it in your portfolio

Include the flow diagram in your case study next to the final screens. Highlight one alternate or recovery path you designed and explain the player problem it prevents. Reviewers look for this kind of systems thinking because it shows you design for real play, not just for the screenshot.

Keep going

Pair this with the Menu Architecture Map and the State Matrix, 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