UX and the Button Dilemma: Where Do “Back,” “Cancel,” and “Save” Really Belong?

Spotify

Designing user experiences isn’t just about color palettes, components, or typography. Sometimes, the most important decisions come down to this:

Where does the button go?

“Back,” “Cancel,” “Save,” “Exit.”

Simple labels. Complex implications. Because the placement, hierarchy, and behavior of these buttons can make or break a user’s journey.

Let’s explore why.

Why Button Placement Matters More Than You Think

In UX, users scan and act faster than they think. They rely on patterns—muscle memory, consistency, and visual priority. So when a button is placed in the wrong position or does something unexpected (looking at you, Cancel = delete all progress), you introduce:

  • Friction
  • Frustration
  • And worst of all—lost trust

Small decisions have big consequences.

The Problem: Inconsistency and Confusion

Here’s what we’ve all seen:

  • A “Cancel” button is placed where “Save” typically goes
  • “Back” sometimes navigates, other times erases work
  • “Exit” implies safety but causes data loss
  • “Save & Exit” is often used as a band-aid for unclear state logic

It’s not that these patterns are inherently wrong. It’s that they’re inconsistently used, ambiguously labeled, and rarely explained. And when every app does it differently?

Users pay the price.

What Button Placement Teaches Us About UX

This isn’t about aesthetics. It’s about intent and clarity.

Key UX principles button placement must support:

  • Cognitive flow: Does the button appear where the eye naturally goes after reading the content or completing a task?
  • Touch and tap ergonomics: Can users reach primary actions easily with one hand on mobile?
  • Hierarchy and priority: Which action do you want the user to take? That should be the most prominent.
  • Safety and reversibility: Are destructive actions far enough away—and confirmed?

Button Behavior Guidelines That Work

1. Primary actions go bottom right

This aligns with Fitts’s Law, eye-tracking studies, and common design heuristics. Whether it’s “Next,” “Save,” or “Submit,” it should anchor the end of the user’s visual flow.

2. Destructive actions go left or away from confirmation

“Cancel,” “Delete,” and “Discard” should not be the brightest button on the screen. Color them accordingly. Separate them visually and spatially.

3. Use clear labels, not ambiguous verbs

  • “Save & Exit” is better than “Done.”
  • “Cancel” should not mean “delete everything.”
  • “Exit” should always clarify what’s being lost or saved

4. Avoid double-negative situations

“Cancel” inside a modal asking if you want to cancel an action = confusion.

Bonus: Context Matters

Your buttons aren’t universal. They exist within a journey.

  • In onboarding flows, users expect a “Back” that lets them review—not abandon.
  • In form-heavy admin tools, “Cancel” should always trigger a confirmation, not silent data loss.
  • The stakes are higher in healthcare, legal, or finance; clarity and confirmation should be mandatory.

Final Thought

Button placement is one of the most fundamental yet overlooked aspects of UX. It’s where logic meets muscle memory. Where expectation meets action. Where a good experience either flows—or falls apart. If you want users to trust your product, start with your buttons.

They may be small—but they’re not insignificant.