Loading
Why users ignore your onboarding
What you can do to fix it
Advanced onboarding techniques
Users land in your product, already confused.
Not because your UX is broken—but because they skipped the onboarding copy you intentionally added.
In this UX case study, we’ll explore why that happens—and how to fix it.
Using YNAB (You Need A Budget) as our example, we’ll break down why people are likely to ignore three common onboarding techniques
Then we’ll look at the subtle UX changes that drive better engagement and retention.
P.S., this is perfectly paired with this Cheatsheet on writing copy that's effortless to read.
Okay, let's get stuck in.
We've just looked at an example where the user attempted to skip part of the onboarding.
The easiest thing to do is to give them more context.
But there are other methods.
For example, you could try to interpret their underlying intent.
This requires really understanding your users, but in the example above it's possible that they just want to explore the features of YNAB.
You might find that any additional education is ignored or skipped.
The user might know that the budget-creation process will take an investment of their time, and pre-emptively be rushing through this process to reach a point of interactivity.
In which case, you could use intent-driven outcomes.
YNAB could create a demo dashboard for the user to interact with, satisfy their urge to play with the app, and then bring them back into the onboarding process.
As a real world example, RevenueCat does exactly this.
Intentions can seem obvious as a user—we know why we do things.
For example:
👀 Observed action
🎯 Possible intent
User sets a specific "goal" during onboarding.
It was the first one in the list, and they just want to see if the app has a specific feature.
User rejects notification permissions.
They don't want notifications while they're learning the app, but would consider them later.
User declares a company size of 1.
They can't be bothered to invite any team members yet, even though it is a team.
By catering to intent, not actions, you can often be far more effective with onboarding, and reduce self-inflicted wounds.
Look at the pop-up below, and guess what it is.
It's fairly likely that you also recognised it as an error, or alert.
And that's because it looks like one.
Which is a shame because that perception carries negative connotations.
But what's really happening in this moment, is that YNAB are trying to teach you about the limitations of a feature. You're trying to auto-assign cash, but you don't have enough to cover everything in your budget.
So this pop-up is educating you about the decision.
But notice that even without changing the text, you can change the tone.
This is why UI matters in UX.
Your choice of component can create a lens, before the user has even read a word.
And by changing the tone, you can influence how people read, digest and retain that information.
We're all familiar with (if not bored to death by) the confetti blast celebration. This is how to design a motivational slingshot that actually works.
Learn which milestones to celebrate, and why
The common mistake when building celebrations
Techniques for upselling more effectively
Companies are building unique features, but then failing to show anyone how to actually use them.
How to structure onboarding for creative input (like AI)
Identifying when simply "pointing" isn't enough
How to make these features more memorable
Substack is optimised for writers, not readers. They use deceptive design and psychological exploits to drive growth.
How Substack uses deceptive design to boost sign-ups
How they exploit uncertainty to drive upgrades
The risks of careless A/B testing
The best retention strategy? Design a product that helps users feel like they’re making progress—right from the moment they set a goal.
How to create goals that stick
Framing benefits better to upsell more
Reducing churn by leaning into goals
There are more than 40,000 designers, developers and product teams who trust BFM to explain why things work. Join them.