When to Remove Friction and When to Lean Into It

In the design world, “Delight” is the ultimate compliment.

Whitespace, minimalism, and frictionless flows are moral imperatives. We are taught that “Simple” is always better than “Complex.” If an interface is dense, it’s “cluttered.” If a workflow has steps, it’s labeled “heavy.”

But there’s a reason why an incident response tool like PagerDuty feels intense, information-heavy, and unapologetically utilitarian, yet still be loved by the people who rely on it.

And there’s a reason why a dating app can lose you forever because one screen feels slightly confusing.

That difference isn’t taste.

It’s the Desperation–Relief Spectrum.

JTBDUX—the convergence of Jobs-to-be-Done and UX—treats this spectrum as a strategy lever. Different jobs carry different emotional weight, and that weight determines what users will tolerate.

Some jobs are “my hair is on fire.” People will forgive ugly. They will push through friction. They will pay for relief. Other jobs are “this might be nice to have.” People won’t push. If it isn’t effortless, they’re gone.

Where your product lands should shape your UX, your messaging, your pricing, even how much friction you can get away with.

Rescue > Delight

When it comes to high-desperation jobs, users don’t need delight. They need rescue.

Think about the moment your bank app sends you a notification: “Was this you? $842 at an electronics store in another state.”

Or the moment your on-call engineer’s phone lights up: “P1 incident. Checkout errors spiking. Revenue impact ongoing.”

Or the moment you’re at the airport and your flight gets cancelled: “Next available seat: tomorrow.”

Or the moment you open a tax app at 11:43pm on April 15th.

In these moments, the user isn’t exploring. They’re not browsing features. They’re trying to stop immediate pain. And that changes what “good UX” means.

What “good UX” looks like in rescue mode

When your hair is on fire, speed and clarity beat elegance. If someone is rebooking a flight, they don’t care about a beautiful carousel. They want the fastest possible path to: “Here are your options. Here’s the earliest arrival. Confirm.”

Sometimes, information density can be comforting. When you’re handling fraud, you don’t want the app to “keep it simple” by hiding detail. You want timestamps, merchant names, locations, last four digits, “freeze card” status, and a clear audit trail of what just happened.

Minimalism is not automatically “clean” here. It can be a form of concealment.

A bit of friction can be acceptable—sometimes its required. If I’m about to freeze my card, submit an incident update, or finalize a tax filing, a confirmation step isn’t “annoying.” It’s stabilizing. It says: “This is real. This is irreversible. Let’s make sure.”

People will pay for relief.In high-desperation jobs, the value isn’t theoretical. It’s immediate. The user isn’t asking “is this worth it?” They’re asking “can this make the pain stop?”

There’s a subtle danger: teams assume this tolerance lasts forever. It doesn’t. When the crisis ends, the same user who tolerated friction in rescue mode will become much less forgiving in maintenance mode.

When friction is an exit, not a speed bump

Now let’s flip to the other end of the spectrum. The user isn’t in pain. They’re curious. They’re open. They’re willing to check it out—but not willing to work for it.

This is the world of:

• social feeds
• dating apps
• casual notes
• entertainment browsing

In these jobs, the user’s alternative isn’t “suffering.” It’s “do nothing” or “use whatever is already on my phone.” Friction here is fatal.

A login wall on a casual notes app? Bounce.

A confusing control in a dating flow? Bounce.

A dense settings menu before you’ve shown anything fun? Bounce.

If the job is optional, the experience has to be rewarding in itself. There simply isn’t enough pain to power them through effort.

Low-desperation jobs often need perceived value before payment. That’s why freemium, trials, and “aha before the paywall” patterns exist. If the job doesn’t feel urgent, asking for money too early is like asking someone to buy a gym membership while they’re still on the couch. You can’t charge for potential.

Design for the job’s emotional weight.

A lot of teams overestimate desperation. Founders feel the problem intensely because they’ve been living with it for months. But the average user might not be desperate at all. They’re browsing. If you build a high-desperation experience (dense, heavy, full of steps) but attract low-desperation users, they’ll bounce and you’ll call it a “marketing problem.”

It often isn’t.

It’s a calibration problem.

So ask the questions that locate you on the spectrum:

• What happens if the user doesn’t solve this today?
• Is there a real consequence, or just a vague sense that things could be better?
• How actively are they searching for a solution—did they come to you, or did you have to find them?
• What are they comparing you to: a competitor, or doing nothing at all?

The answers give you clues as to where the job sits on the Desperation–Relief Spectrum. And once you know that, you stop fighting religious wars about “delight” and “minimalism.”

You design for what the user is actually here for: Relief—or a nice-to-have.