Users Want Now, Not Later

TL;DR: Present bias and hyperbolic discounting make a small reward now feel stronger than a bigger reward later. If your product asks users to wait too long before they feel value, most of them will leave.

You put the payoff at the end again. It sits behind setup, behind the tour, behind the “just one more thing” screen. Designers tell themselves users will push through because the value is coming. Then they do not. A lot of the time the problem is timing. You are asking people to pay a cost now for a payoff they have not felt yet.

The present has more weight

In 1997, David Laibson described hyperbolic discounting in plain enough terms. A reward loses force as it moves away from the present, and it loses force faster near now than people think. Ted O’Donoghue and Matthew Rabin later called this present-biased preference. The name matters less than the pattern. People can mean yes in advance and still choose no when the effort is in front of them.

That is the part designers keep getting wrong. The user who signs up and plans to finish setup was not pretending. The calculation changed when the forms, waiting, and decisions became real. Kahneman and Tversky add something useful here too. The friction in front of a person feels heavier than a gain they have not felt yet. The hassle is happening now. The value is still theoretical.

This is why so many onboarding flows look fine in a planning deck and die in use. On the deck, the cost is broken into small boxes: name, password, preferences, permissions, payment details. On the phone, it lands as one long ask before the product has earned anything. Designers count steps. Users feel drag.

This does not mean people never wait for value. People wait for all kinds of things. But if the payoff is still abstract and the friction is already real, a lot of them will drop it.

Spotify moved the feeling forward

When Spotify launched with a free tier in 2008, the key move was not the price alone. It was the order. People could use it first. They could feel the product in the commute, at work, at home, before the company asked for a harder decision.

By 2014, Daniel Ek said that “more than 80% of our subscribers started as free users.” By Q1 2023 Spotify had 210 million paid subscribers out of 515 million monthly active users, and its annual report called the free tier “a funnel for our paid subscriptions.” The order mattered. The product let people feel the gain before asking them to pay the cost.

Apple Music went the other way. Free trial, yes, but with a credit card upfront. Same music problem. Different order of commitment. Free does not always win, but value felt now and commitment asked later is a different proposition from commitment now and value later.

That ordering changes the whole mood of the decision. One version says, try it and see. The other says, commit and trust us. Those are not the same ask. A product can have the same catalog, the same promise, even the same eventual price and still feel much heavier because it asked for belief before giving proof.

Where does value actually start

Ask one hard question: at what exact moment does a new user first feel something useful? Not finish a step. Not complete setup. Feel the product do something for them. That is the moment that matters. Then look at everything sitting in front of it: credit card field, permission request, tour, welcome email, five setup screens in a row. I have worked on flows where one extra screen looked harmless in Figma and killed the whole thing in use.

Once I started looking for the first real payoff instead of the first completed step, a lot of onboarding work started to look fake to me.

It also changed what counted as progress. A completed profile is not value. A configured dashboard is not value. Those may support value later, but they are still prep. If the user cannot point to the moment the product helped them, then the product has not started yet. Everything before that is still a tax.

What to move

Move value as far forward as you honestly can. That is the action here. A lot of users will choose what feels concrete now over what only sounds useful later. If your product makes them wait too long to feel anything real, many of them will put it down and do something else.

Sometimes that means shrinking setup. Sometimes it means letting people browse before they create an account. Sometimes it means giving them one real result before asking for more information. The move is not always the same, but the question is. What can they feel now that makes the next ask easier to carry? I have watched one useful preview do more than three careful onboarding screens.

Your product is always competing with what feels immediate.