Users Don’t Care About Your Flow. They Remember How It Felt

You’re registering on a website.

Step 1: Enter your phone number
→ Easy. Almost automatic. You don’t even think about it.

Step 2: Enter the OTP
→ Slight friction. Switching to SMS, coming back… mildly annoying, but fine.

Step 3: Fill in name, email, password
→ Routine. You’ve done this a hundred times. Still on autopilot.

Step 4: Upload a document
→ Wait… what?
Why is this needed? Is this even the right page? Did I click something wrong?

Step 5: Set preferences
→ You’re doing it… but now you’re slightly unsure about the whole thing.

Step 6: Submit
→ You just want this to be over.

Step 7: “Registration Successful”
→ Relief.

Now think about it.
There were 7 steps.

Most of them were fine.
Some were even effortless.

But what do you remember?
Not the easy parts.
Not the number of steps.

You remember that moment at Step 4 —
where doubt crept in.

Years ago, Steve Krug wrote in Don’t Make Me Think:

Users don’t mind multiple clicks.
They mind not knowing what’s going on.
That’s exactly what happened here.

And later, when you think back on the experience…
You don’t replay every step.
That’s the Peak-End Rule:

You remember:
• The moment of doubt
• And how it ended

So here’s what actually matters:

While using your product →
Does each step feel obvious and justified?

After using your product →
What moment defines the memory?

Most teams optimize for the wrong thing.

They:
• Reduce steps
• Simplify screens
• Track completion rates

But ignore:
• Moments of doubt
• Moments that define memory

A good experience is not:

“Fewer steps”
It is:

✔ No moments that make users question themselves
✔ Clear sense of progress throughout
✔ An ending that feels clean and complete

Your product is not judged by how smooth it was.

It is judged by:
Where users hesitated
And what they remember after