The story behind PlayStation's button symbols, why × confirms in PS5 menus, and what it reveals about user experience and interaction design.
You have highlighted a game on the home screen and need to open it. Which button do you press?
Most likely ×, without a second thought. But how did you learn that this button means “confirm” or “continue”?
Here is the twist: the designer of the PlayStation buttons gave × the meaning “no”. Today it is the confirm button in PS5 menus worldwide, including Japan. Sony made it the default confirm button in every region when the PS5 launched in 2020, so that games and the system menu would confirm the same way.
To follow the story, it helps to separate two things: the meaning the designer gave a symbol, and the way people learned to use it.
What do the four PlayStation button symbols mean?
When the first PlayStation launched in Japan in 1994, its controller carried four symbols that later became part of the PlayStation identity:
△ Triangle
○ Circle
× Cross
□ Square
According to Japanese designer Teiyu Goto, each symbol was given a meaning and a colour:
△ The green triangle: viewpoint, one's head or direction.
□ The pink square: inspired by a sheet of paper, standing for menus and documents.
○ The red circle: “yes”, the right choice.
× The blue cross: “no”, or cancel.
The aim was simple symbols that are easy to remember, instead of the letters other controllers used. Goto's account of what the PlayStation button symbols mean was reported by Gematsu.
Knowing what a symbol means doesn't always tell you what it will do in a game, though. □ might open a menu in one game, do something entirely different in another, and throw a left punch in a fighting game.
This is the gap between what a designer intends and what a user learns along the way, and it is the part that matters to an interaction designer.
How circle and cross picked up different jobs
In Japan, players grew used to ○ for confirm and × for cancel. That matches what the two marks mean there: a circle is correct, a cross is wrong.
In many other countries it went the other way. × became the confirm button, while ○ went back or cancelled. WIPO's account of the controller ties the symbols' meanings to the territory and to the game.
So the same console came to be used in two different ways, depending on the region and the game.
A player can know that × confirms without knowing any of its history. They learned the function from what happened on screen each time they pressed it.
Button functions change inside games too. In football games, × might pass and ○ shoot. In fighting games, the buttons take on entirely different jobs.
The symbols stay fixed. How they are used changes with the context.
A user can know a button’s shape well and still have to learn what it does.
What changed with PS5?
With the launch of the PS5 in 2020, × became the default confirm button in every region, Japan included.
As Famitsu reported from Sony Interactive Entertainment, the decision was meant to unify the controls and reduce the confusion between system menus and games.
PlayStation's guide to PS5 button functions lists the current console-menu functions:
× selects the highlighted item.
○ cancels a command.
Inside games, each button's function depends on the game's design.
For a player used to confirming with ×, this feels natural. A Japanese player who had confirmed with ○ for more than 25 years had to change an old habit.
The controller kept its shape. The buttons kept their places. What changed was the result people expected after pressing.
What does the user expect before they press?
In UX, the picture a person holds of how a product works is called a mental model.
A mental model is what makes someone expect a particular button to open the page, a × to close the window, or the site logo to take them back to the home page.
That expectation comes from past experience. The more often something is used, the faster and more automatic the action becomes.
The same idea shows up in an online store. Say the “Save address” button has always sat at the bottom of the screen. After a redesign, a “Back to order” button sits in that spot.
A user may tap it quickly, expecting to find the save button there, and leave the page believing their address was saved.
They can read the button perfectly well. What they expected at the moment they tapped was something else.
A team can check this with two prototypes. Keep the “Save address” wording and appearance the same, move it in just one version, and watch where each participant reaches first. To test the label, fix the position and compare two wordings in a separate round.
So when you change a button people are used to, a tidier design isn't enough. You also need to know what people expect when they use it.
When does a familiar icon need a label?
Symbols save space, but they don't always carry the same meaning.
Take ×. It can mean:
Close the window.
Go back to the previous page.
Cancel the process.
Delete an item.
Decline a request.
These actions look alike, but their results differ.
Picture someone reviewing a furniture installation appointment. A panel opens with the appointment details and a × inside it.
Will the × just close the panel, or cancel the whole appointment?
Closing the panel is simple and easy to undo. Cancelling the appointment can change the booking and the customer's day.
This is where a word clarifies the result. “Close details” can describe leaving the panel, and “Cancel installation” the action that changes the booking.
NN/g's research on icon usability notes that understanding an icon depends on a user's past experience, and that a text label helps when a symbol could mean more than one thing.
The rule is simple: the bigger the consequence of an action, the clearer its meaning needs to be.
How to test a change to a familiar control
You can test the change with a prototype before it reaches the live product.
Start with two clear tasks:
Check the appointment details, then return to the list of orders.
Cancel the appointment because the customer's plans changed.
Don't name the button to use. Ask the participant to complete the task, then watch where they try to press first.
Then ask: what did you expect to happen?
A user may finish the task after more than one attempt, but that doesn't mean the experience was clear. The first press, the moment of hesitation and the step back to correct a choice reveal a lot about the interaction design.
Test the design with two groups:
People who know the current product.
People using it for the first time.
Existing users may act out of habit. New users rely more on the words and shapes in front of them.
If one group struggles, you'll learn whether the problem is the button's name, its position or the order of actions on the screen.
How much explanation you need depends on the cost of a mistake. Closing a panel by accident is minor. Cancelling an appointment or deleting an order needs more care, and may benefit from a confirmation step that tells the user what will happen.
One question for the next design review
Before changing a button people are used to, show the design to a user and ask:
What do you expect to happen when you press here?
That simple question shows the gap between the meaning the design team intended and the meaning that reached the user.
The story of the PlayStation button symbols shows it well. × began as “no” and became the confirm button for millions of players.
You can give the design in your product its first meaning, but use is what teaches people the meaning that lasts.
