MAPPING TEMPLATE
Game Menu Architecture Map
Map front-end screens around the tasks players return to.
Why it matters
Players return to the same menus every session to continue, adjust settings, or check progress. A clear architecture keeps those common tasks within a few presses and makes Back feel predictable. It also helps the team decide where new features belong instead of adding them wherever there is space.
Workflow
List entry contexts such as first launch, returning player, and pause. For each, rank primary tasks by urgency and frequency. Build a screen map with parent, default action, destination, Back destination, and unsaved-change rule for each screen. Separate navigation hierarchy from modal overlays.
Worked example
A returning player starts on Continue, while a new player starts on New Game. Display settings opened from pause return to the pause menu with Settings focused. Warn before discarding a pending change and restore the earlier settings on cancel.
Try it
Map Continue, load save, and change subtitles. Draw a loop for each task and have a partner predict where Back lands before they press it.
Common mistakes to avoid
Organizing menus around internal systems instead of player tasks. Burying frequently used options in deep sub-menus. Treating pop-ups as full screens. Sending Back to different places depending on how the player arrived. Forgetting to warn the player before unsaved changes are discarded.
Use it in your portfolio
Include the architecture map and a short annotation for one decision, such as why Continue is the default for returning players. A clear map shows hiring teams that you can structure a whole product, not only individual screens.
Keep going
Pair this with the Player Flow Worksheet and the Controller Navigation Test Script, or practice on a real brief in the Bi-Monthly Challenges. Want feedback from working game UX/UI designers? Explore the UI Peeps Masterclass.