BlogUI/UX

Stop Designing Screens — Start Designing Decisions

Polished screens don't guarantee users do what they came to do. How to design around the decisions users make: clarity, confidence, momentum, recovery.

Denny Pratama

07 Apr 2026 · 5 min read · UI/UX

Stop Designing Screens — Start Designing Decisions

01The Trap Every Designer Falls Into

Open any design portfolio and you'll see the same thing: beautiful screens, polished components, satisfying color palettes. And honestly? They look great. But here's the uncomfortable truth — gorgeous screens don't guarantee a great product. They don't guarantee that users actually do what they came to do.

A team can spend weeks perfecting a checkout screen and still lose people at the last step. The screen can be beautiful while the decision architecture is broken.

That's why it's worth asking a different question. Instead of "How should this screen look?", ask "What decision does the user need to make here — and how do I make that decision easier?"

02What Is a Decision Point, Really?

Every interaction a user has with your product is, at its core, a decision. Should I click this button? Is this the right plan for me? Do I trust this app with my credit card? Should I skip this step or fill it out?

A decision point is any moment where a user must choose between continuing, stopping, or going in a different direction. It's not always a dramatic fork in the road. Sometimes it's as subtle as a loading spinner that makes someone wonder if the app has crashed.

When you start mapping your product through this lens, something interesting happens — you stop seeing a collection of screens and start seeing a series of conversations between your product and your user.

03The Four Layers of a Good Design Decision

A UX audit can evaluate every major decision point across four layers:

  • Clarity: Does the user know what their options are? Can they understand the consequence of each choice without having to think hard?
  • Confidence: Does the user feel safe enough to make the decision? This is where trust signals, microcopy, and visual hierarchy do their heaviest lifting.
  • Momentum: Does making this decision move the user forward, or does it branch them into a confusing sub-flow?
  • Recovery: If the user makes the wrong choice, how easy is it to undo, go back, or correct course?

Notice that none of these four layers mention color, typography, or spacing. That's intentional. Visual design supports decision-making — it doesn't replace it.

04An Example: The Pricing Page Problem

Picture a SaaS pricing page with decent traffic but poor conversion. The page looks clean. Three plans, clear pricing, a prominent CTA button on each card.

Run a decision audit on a page like that and you might find:

  • All three plans are presented with equal visual weight — no hierarchy, no recommendation
  • The feature list uses internal jargon that real users don't understand
  • There's no reassurance about choosing the wrong plan (users are afraid of being locked in)
  • The CTA just says "Get Started" — which tells users nothing about what happens next

The screen isn't broken. The decision architecture is broken. Users land on that page, can't confidently choose, and leave.

The fix isn't a redesign. It's a decision redesign: highlight the most popular plan, rewrite the feature list in plain language, add a "You can upgrade or downgrade anytime" line near the CTA, and change the button copy to something like "Start your free 14-day trial."

Same layout. Completely different decision experience.

05How to Apply This in Your Own Work

1. Map Your Decision Moments First

Before you open Figma, walk through your user flow and mark every point where a user has to choose something. Include the invisible decisions — like whether to trust a form enough to fill it out. These moments are your design battleground.

2. Write the Decision Before You Design It

For every key decision point, write a one-sentence description of what the user needs to decide and what information they need to make that decision confidently. If you can't write it clearly, you definitely can't design it clearly.

3. Use Visual Design to Guide, Not to Impress

Visual hierarchy exists to direct attention toward the right decision at the right time. Ask yourself: if a user landed on this screen with their eyes half-open, where would their attention go first? Is that where you want it to go?

4. Test Decisions, Not Just Usability

Most usability tests ask "Can users complete this task?" Start asking "Did users feel confident making this choice?" Post-task interviews and confidence ratings reveal an entirely different layer of friction that task-completion metrics miss entirely.

06The Mindset Shift That Changes Everything

Design is not about making things look good. It's about making things work well — and working well means helping real people make real decisions with confidence.

When you internalize this, your entire relationship with design tools changes. Figma becomes a tool for modeling decisions, not just screens. Your component library becomes a vocabulary for communicating choices. Your design reviews become conversations about decision quality, not just visual polish.

This is, honestly, what separates designers who ship features from designers who shape behavior. And in a world where every product is competing for attention and trust, shaping behavior is the whole game.

07Final Thought

The next time you sit down to design a screen, pause for just a moment. Ask yourself: What decision is happening here, and have I made it as easy and confident as it can possibly be?

If you can answer that question clearly for every screen in your product, you're already designing better than most. Not because your screens will look better — but because your users will feel understood.

And that feeling? That's what keeps people coming back.

UI/UX

Denny Pratama

Product designer in Indonesia. Since 2018 I’ve designed SaaS products, dashboards and marketing sites, and now I build my own designs too.

About me