Users compare your product to their current habit — not to nothing.
One thing I’m starting to realize about product-building:
Users almost never compare your product to “nothing.”
They compare it to:
- their current habit
- their muscle memory
- the path requiring the least attention
A workflow can be technically “better” and still lose if the interruption cost feels higher than what users already do instinctively.
That changes how I think about friction.
Sometimes the issue isn’t:
- quality
- features
- pricing
- design
Sometimes the real competitor is simply:
“the thing they already know how to do without thinking.”
I think this is why early-stage feedback from a handful of real users matters so much more than vanity metrics.
One brutally honest sentence can reveal more than analytics dashboards ever will.
Trending on Indie Hackers
This completely reframed how I think about onboarding. Building in the productivity space, I used to assume that showing people a "better" way to plan their day was enough — but the real barrier is that their current habit (opening Notes, a random spreadsheet, or just keeping things in their head) feels cognitively free. The question I now ask in user interviews isn't "would this be useful?" but "what would you stop doing if you started using this?" That second question surfaces the actual switching cost in a way feature comparisons never do. It also tells you whether the habit you're replacing is something they're even slightly frustrated with — because if they're not, no amount of polish will overcome the inertia.
I think this is especially true when the current habit already feels “good enough” emotionally, even if it is objectively messy or inefficient.
People often do not optimize for the best workflow. They optimize for the workflow that feels familiar, reversible, and mentally inexpensive.
I have seen this a lot in WordPress environments too. Users will continue using fragile or cluttered setups simply because they already understand the rhythm of them, even when cleaner approaches exist.
That is why reducing cognitive interruption sometimes matters more than adding capability.
The interesting part is that a technically better product can still lose if it asks the user to think more consciously than their current habit does.