Stop Removing Every Obstacle: Why a Little Friction Builds Better Products

Somewhere along the way, the design industry declared war on friction. Every UX principle, every conversion optimization playbook, every growth hacker's Twitter thread pointed in the same direction: remove barriers. Reduce steps. Make it easier. One-click this. Auto-fill that. Skip the confirmation screen.

The logic is intuitive. Friction causes drop-off. Drop-off hurts conversion. Ergo, eliminate friction.

Except some of the most successful, most loved products in tech didn't get that memo — and they're better for it.

The Frictionless Fallacy

Here's the thing about removing all friction: you don't just remove barriers for serious users. You remove barriers for everyone. And not everyone is the customer you want.

When a product is too easy to start, too easy to sign up for, too easy to use without any investment of thought or time, you get something that feels counterintuitive: lower satisfaction, higher churn, and a support queue full of people who didn't really understand what they signed up for.

The obsession with frictionless experience conflates two things that aren't the same: effort and confusion. Confusion is always worth eliminating. Effort, strategically deployed, is a feature.

Notion's Onboarding Isn't Easy. That's the Point.

Notion is one of the most popular productivity tools in the US market, with millions of users and a cult following among knowledge workers, developers, and creative teams. It is also, by any objective measure, not easy to start using.

The canvas is blank. The flexibility is overwhelming. There's no guided hand-holding that tells you exactly what to do in the first five minutes. New users often describe a period of productive confusion before things click.

Notion has known this for years. They've iterated on onboarding, added templates, improved documentation. But they've never fundamentally simplified the core product to the point where it loses its depth. The friction is load-bearing.

Here's why: the users who push through that initial learning curve become extraordinarily loyal. They've invested time. They've built systems. They've made Notion theirs. The effort creates ownership, and ownership creates retention. Notion's NPS scores and word-of-mouth growth are directly tied to the depth of engagement that a slightly harder product produces.

If Notion were as simple as a notes app, it would compete with notes apps. The friction is what separates it from the commodity tier.

Superhuman's Waitlist Wasn't a Growth Hack. It Was a Filter.

When Superhuman launched its email client, it famously used a waitlist and a mandatory onboarding call before giving users access. In a world where most apps let you sign up in thirty seconds, this looked bizarre.

The results were the opposite of what the frictionless gospel would predict.

The waitlist created genuine demand — people wanted access partly because it was hard to get. But more importantly, the onboarding call filtered for users who were serious enough to schedule a call and invest forty-five minutes in learning the product. Those users, by definition, were high-intent. They were more likely to pay, less likely to churn, and more likely to become vocal advocates.

Superhuman's CEO Rahul Vohra has spoken publicly about the strategy: they were building for a specific user, and they were willing to use friction to find that user. The waitlist wasn't a growth hack. It was a targeting mechanism.

The result was a product with fanatical retention and a premium price point that the market validated enthusiastically.

What the Support Queue Actually Tells You

Here's a data point that doesn't get enough attention: a large percentage of support tickets come from users who were never a good fit for the product in the first place. They signed up because it was easy, not because they needed what you built. They didn't read the documentation because nothing required them to. And now they're frustrated, and your support team is paying the price.

Intentional friction — a slightly more involved sign-up, a required onboarding step, a short quiz that clarifies use cases — filters out the casual clickers before they become support costs. The math on this is compelling.

A product that converts 8 percent of visitors but retains 70 percent of them is a fundamentally better business than one that converts 15 percent and retains 30 percent. Friction at the front of the funnel buys you quality at the back.

The Design Principle Behind Strategic Friction

This doesn't mean making your product deliberately confusing or punishing users for exploring. There's a meaningful distinction between friction that filters and friction that frustrates.

Friction that filters:

• Requires a small but meaningful commitment (scheduling a call, completing a profile, selecting a use case)
• Sets accurate expectations about the product's depth or complexity
• Rewards the user who completes it with a noticeably better experience
• Aligns with the product's actual value proposition

Friction that frustrates:

• Is arbitrary, with no clear payoff for the user
• Exists because of technical debt or lazy design, not strategy
• Creates confusion rather than investment
• Applies equally to all users, including your best ones

The design question isn't "how do we remove all friction?" It's "which friction serves us, and which friction doesn't?"

Duolingo's Streaks Are Friction. They're Also the Product.

Duolingo is one of the most downloaded apps in US history. Its streak mechanic — the daily requirement to practice or lose your streak — is, technically, friction. It creates a small obligation. It generates mild anxiety when you're about to miss a day.

It's also the single most effective retention mechanism in the product. Users don't just use Duolingo; they protect their streaks. The friction creates attachment, and attachment creates the habit that makes the product work.

Without the streak, Duolingo is a flashcard app. With it, it's a daily ritual. The effort isn't a bug. It's the entire value proposition.

A Framework for Founders and Product Teams

Before you remove a friction point in your product, ask three questions:

1. Who does this friction filter out? If the answer is "low-intent users who wouldn't have converted anyway," keep it.
2. What does completing this friction signal? If clearing the barrier demonstrates meaningful intent or creates genuine investment, it's probably earning its place.
3. Does the experience improve after the friction? Friction is only justifiable if there's a payoff. If users who push through get a meaningfully better product, the barrier is a feature. If they don't, it's just an obstacle.

The best products aren't the easiest ones. They're the ones that feel worth the effort — and sometimes, the effort is part of what makes them feel worth it.

Stop trying to remove every obstacle. Some of them are holding the whole thing together.