Every time we debate adding a profiling survey, someone says:
“Let’s not add friction.”
“Time to value must be short.”
And sure — that’s partly true.
Nobody wants a bloated flow. But here’s what most teams miss:
👉 Not all friction is bad.
Only friction without value is.
I’ve seen it over and over:
When we added a question like “What are you trying to do?” — not for data, but to actually personalize the experience — activation went up.
Why?
Because users felt like the product listened to them, and they were going to create something together. Kind of better than just speed for the sake of speed, right?
And here’s why:
Effort Justification
Effort Justification explains why people care more about outcomes they work for.
But here’s the kicker:
👉 Effort doesn’t have to be just a tax. It can be signal of meaning, a step that helps you create collaboratve connection betwen your user and your product. They tell you a story and you listen to it.
When users click through a flow with zero decisions, zero context, zero ownership — they don’t feel committed.
And they don’t feel seen.
The result? They leave.
How we are making it worse by trying to make it better
We confuse “fast” with “valuable.”
So we kill everything that feels like a step:
– Use case selection? Gone.
– Preferences? Later.
– Questions? Skip.
We think we’re helping users move faster.
But we’re just giving them a product that doesn’t care who they are.
Here’s a move you can steal from Duolingo to make it right
Duolingo asks three things upfront:
Why are you learning a language?
How much time do you want to spend daily?
Are you a beginner — or want to take a placement test?
And based on those answers, they:
– Start you at a different level
– Adjust your XP goals and reminders
– Adapt your early content to fit your motivation (travel, school, etc.)
They don’t change the whole UI.
They change what you see first, how much you do, and why it matters to you.
Those short questions become a great investment in activation and long-term retention.
3 steps to break this pattern next week
Add one question at the start of onboarding that lets users define their goal (e.g. “What do you want to use this for?”).
👉 Show a different screen or checklist based on their answer.Replace one generic empty state with a filled-in preview that matches what the user said they want.
👉 Even if it’s fake data — make it feel like their version of the product.Rewrite one setup step to show the reward.
Instead of: “Connect your calendar”
Say: “Connect your calendar to instantly create your booking page.”
If you forget everything, remember this:
Users don’t value “easy”. They value seeing themselves in your product — and that takes a little effort.
