top of page

Multi-Selection Interface

UX DESIGN

Context

This interface allowed players to customize an item before placing it in the world. It was accessible inside a central gameplay context, which already offered multiple complex interactions, like placement, rotation, etc.

​

The decision to pair two of the customization options together in the same interface could be explained by the way they worked in tandem.

 

As an example, imagine one is the shape of the item to place, while the other is its color. Both had an significant impact on the item to place and were subject to be changed simultaneously.

MY ROLE

UX DESIGNER

PROJECT

UNANNOUNCED (PC/CONSOLES)

STUDIO

UBISOFT MONTREAL

The Problem

How can players be made aware of all the customization options without causing cognitive overload?

Constraints

  • There are a lot of actions available at once for controller​

  • Leadership insists the game must not feel like an editor

  • The quantity of content is subject to increase over time

  • There are opposite intents for customization

    • It must be quick​

    • It must show as much content as possible

FlowChart

Item placement flow. The customization is in the framed area.

Initial Design

Two of the main references that inspired the initial design.

image.png

Hogwarts Legacy's item placement mode allows to toggle between color and item variants.

image.png

Enshrouded has building parts and materials customizable at the same time, with an on-demand menu to see more parts.

First Figma Prototype made to rapidly test the layout and navigation before creating the wireframes.

TRY IT OUT!

Use a Gamepad controller or click on the Dpad icons to customize the shape and color selections.

Version_00_F.png
Inputs=RB.png
Catalog_00.png

BY DEFAULT

​

  • The player can change shape by using Dpad Left/Right​

  • The player can change color by using Dpad Up/Down​​

  • Visible quantity of options limited. Scrolling is supported

ON-DEMAND MENU

​​

  • Holding RB shows more shapes​

  • Navigation with the Dpad

  • Each row is a different category of shapes

  • Visible categories are limited to 3. Scrolling is supported​

  • There aren't enough colors to require a similar interface

To avoid choice overload, I initially made sure to display only a limited amount of shapes and colors. In collaboration with Game Design, I selected the order in which they appeared based on how frequent they were used, so users didn't need to scroll in most cases. Then, I provided a way for users to be able to see more shapes, grouped by categories to provide pattern recognition and ensure finding the desired shape didn't take too long.

Cognitive Walkthrough, used to identify potential usability issues

MAIN GOAL        THE USER WANTS TO CUSTOMIZE THEIR SHAPE AND COLOR SELECTIONS

TASK 01                CHANGE SHAPE

Correct Action

Press Dpad Left or Right

Will the user know what to do at this step?

Yes

Why?

The shape list is visible with the controls on each side

Will the user know they did the right thing?

Yes

Why?

Pressing the inputs changes the selection on the UI and 3D preview

TASK 02                CHANGE COLOR

Press Dpad Up or Down

Yes

The color list is visible with the controls above and below

Yes

Pressing the inputs changes the selection on the UI and 3D preview

STRENGTHS

​​

  • Navigation: Navigating the two lists with separate axis works well​

PAIN POINTS

​

  • Input mapping: Natural mapping cannot be applied to gameplay actions that would benefit from it, since Dpad is used for UI navigation

  • Uniformity: Categories don't have the same amount of content​​

  • Scalability: The interface doesn't support long term needs

The initial design had no significant usability issue and it offered a natural mapping for the UI navigation. It worked well because each selection could be navigated and were represented visually as two different axis. On the other hand, scalability of the interface was becoming an issue because we kept adding more content. While this design worked well for some competitors, we simply had too much content for it to be a viable solution.

 

Also, the user tests revealed players were often using the same shapes and colors. So for the next iteration, I wanted to move the customization a level deeper, to free some inputs and allow users to find content more easily.

First Iteration

Inputs=RB.png
Menu_01.png
Inputs=X.png

ON-DEMAND (QUICK) MENU​

​

  • Pressing RB opens up a menu to customize both Shape and Color

  • ​The player can change Shape by navigating a Vertical List on the left side

  • The player can change Color by navigating a Vertical List on the right side​

  • The player can navigate between Shape and Color with Left/Right inputs​

  • Both lists are scrollable and ordered by recent use

FULL CATALOG

​​

  • Press X while in the Quick Menu to see a full catalog​

  • Items are ordered by categories

  • ​Shapes and Colors are separated in different tabs​

  • Both lists are scrollable and support addition of content

Cognitive Walkthrough, used to identify potential usability issues

MAIN GOAL        THE USER WANTS TO CUSTOMIZE THEIR SHAPE AND COLOR SELECTIONS

TASK 01                OPEN THE CUSTOMIZATION MENU

Correct Action

Press RB

Will the user know what to do at this step?

Yes

Why?

The  input is visible on the previous screen

Will the user know they did the right thing?

Yes

Why?

The interface changes

TASK 02                CHANGE SHAPE

Press Dpad Down

No

The visual representation can be mistaken for a radial selection with the joystick

Yes

Pressing the inputs changes the selection on the UI and 3D preview

TASK 03                CHANGE COLOR

Press Dpad Right, then Dpad Down

No

Users sometimes press A to confirm the shape selection before attempting to change the color, which closes the menu

No

The difference is very subtle when the focus in on the shape VS. color

TASK 04                CLOSE THE MENU

Press A or B

Yes

The control reminders are displayed on the bottom of the screen

Yes

Pressing the input closes the menu instantly

IMPROVEMENTS

​​

  • Intuitiveness: Removing UI navigation allowed us to use natural input mapping for gameplay actions​

  • Content: Faster to find something, as more options are displayed in the Catalog

PAIN POINTS

​

  • Usability: Navigation between the two lists is too error prone

  • Intentionality: Pressing A confirms both selections and closes the menu

  • Exposition: The Catalog is hard to access. Some players don't know it exists​

With this version, we successfully gained more leeway for the gameplay controls, by removing the UI navigation (4 inputs). I also tried a different approach of keeping Shape and Color in the same interface, but it didn't pay off as I had hoped. Instead, it confirmed I successfully had created a multi-selection interface with the initial design, through the mapping on different axis. Additionally, the user tests revealed I needed to reduce the risk of making mistakes and increase intentionality, so that was my focus for the next iteration.

Second Iteration

Inputs=X.png
Catalog_03.png

SHAPE CATALOG

​

  • Press X to open the Shape Catalog

  • Navigation with Dpad Left/Right or Left Stick (like any menu)

  • Press A to confirm selection

  • Added features to support a better categorization and addition of content:

    • Categories

    • Filters

    • Sorting options

    • Favorite system

Inputs=Y.png
Menu_03.png

COLOR CUSTOMIZATION

​

  • Press Y to open the Color customization UI​

  • Navigation with Dpad Left/Right

  • Press A to confirm selection

Cognitive Walkthrough, used to identify potential usability issues

MAIN GOAL        THE USER WANTS TO CUSTOMIZE THEIR SHAPE AND COLOR SELECTIONS

TASK 01                OPEN THE CUSTOMIZATION MENU

Correct Action

Will the user know what to do at this step?

Why?

Will the user know they did the right thing?

Why?

Press Y

Yes

The  input is visible on the previous screen, next to the current shape

Yes

A menu will open with a camera transition

TASK 02                CHANGE SHAPE

Use Dpad or Left Joystick

Yes

The navigation follows the same logic as any other menu in the game

Yes

Pressing the inputs changes the selection on the UI and 3D preview

TASK 03                CONFIRM SELECTION / CLOSE THE MENU

Press A or B

Yes

The control reminders are displayed on the bottom of the screen

Yes

The menu closes as soon as either inputs are pressed. The shape is equipped after pressing A or reverted after pressing B

TASK 04                OPEN THE COLOR CUSTOMIZATION MENU

Press X

Yes

The  input is visible on the previous screen, next to the current color

Yes

The interface changes

TASK 05                CHANGE COLOR

Use Dpad Left or Right

Yes

The controls are visible on each side of the list

Yes

Pressing the inputs changes the selection on the UI and 3D preview

TASK 06                CONFIRM SELECTION / CLOSE THE MENU

Press A or B

Yes

The control reminders are displayed on the bottom of the screen

Yes

The menu closes as soon as either inputs are pressed. The color is equipped after pressing A or reverted after pressing B

IMPROVEMENTS

​​

  • Intentionality: The players open the desired interface through separate inputs

  • Usability: No more navigation error. The player doesn't affect the wrong customization by mistake

In the end, we ended up separating the customization of Shape and Color in two distinct interfaces, with their respective access. Not because multi-selection interfaces are not viable, but because in this case, the content and users had different needs. It took us multiple iterations and user tests to understand that our pre-conceived idea of how players would interact with the content was wrong. It's only once we switched to a full user-centric approach that we started seeing meaningful results.

The Problem

How can players be made aware of all the customization options without causing cognitive overload?

The Answers

EXPOSURE

Players can't know something exists if it's not noticeable or accessible when needed

SCALABLE SOLUTIONS

Using filters, sorting, favorite system, search function, etc.

SIMPLIFICATION

Using natural mapping and separating the information to facilitate decision making

Learnings & Reflections

WHAT I LEARNED

​

  • Testing an idea is always worth it, because it can highlight issues otherwise invisible on paper​

  • We never fully know what players will think or how they will interact with our designs until we've seen it in user tests​

  • Resilience is key. Designs evolve and we need to be open to change​

  • Coming back to an older design is not necessarily a failure, it can mean something was learned

WHAT I WOULD DO DIFFERENTLY

​

Our initial intention to offer a single interface for the selection of two different elements ended up quite a challenge, but it allowed me to test different approaches, take calculated risks and get some learnings.

​

In this specific case, if I could do things differently, I would collect user feedback earlier to understand how they interact with the game. Had we done it sooner, we could have observed that it was totally fine to separate the two customization options.

© 2026 Maxime Bohémier

bottom of page