Innovation has a budget. Spend it on the problem.

Every product that solves a problem in a genuinely new way has to teach the market how to use it. There is no way around that. And every one of them hears the same objections on the way: it's too hard, I'm not used to it, it's not intuitive. The mistake isn't hearing those objections. It's not knowing which ones you're supposed to push through, and which ones you caused for no reason.

"It's too hard" is the price of anything new

New behavior is uncomfortable by definition. When Tinder asked people to swipe right or left on a face, it wasn't just a new gesture. It turned dating from something slow and considered into a three-second impulse, and plenty of people found that strange, or worse. That friction wasn't a flaw in the product. It was the product. If Tinder had softened the swipe into something more familiar, it would have softened away the entire reason it existed.

So when a truly innovative product meets resistance, that alone tells you very little. Resistance is what the edge of a new behavior feels like. The team that treats every "it's not intuitive" as a bug to fix will sand the innovation down until nothing new is left.

The novelty budget

I think of it as a budget. Users will spend a limited amount of attention learning something new before they give up. Every unfamiliar element in your product draws from that same budget, whether it's the core idea or a settings screen that works differently than they expect. So the question isn't whether to ask users to learn. It's where you spend what they're willing to give you.

Spend it on the part that is actually new, the part that solves the problem in a way nothing else did. Everything around it should lean on best practice as hard as it can. A radio button still means pick one. A login still looks like a login. Settings live where people look for settings. Every convention you reuse is something users already know, which leaves more of the budget for the thing you actually need them to learn.

DeFi taught me this the hard way. The core innovation of automated market makers was real and worth teaching: instead of waiting for a counterparty, you traded against a pool, and anyone could provide the liquidity. But users also had to learn wallets, seed phrases, gas fees, token approvals and slippage settings before they ever got to that idea. None of that was the innovation. It was infrastructure leaking into the interface, and it burned most of the novelty budget before the product had a chance to show what was new. The pool was the lesson worth teaching. Everything else should have felt like something people already knew.

Reading the objections correctly

This gives you a way to sort feedback. When someone says "it's not intuitive," ask what they're pointing at. If it's the core behavior, the thing that makes your product different, that's expected, and the answer is better teaching, not retreat. Watch whether people who get past it stay. If they do, the friction is worth it.

If they're pointing at anything else, a form, a menu, a flow that could have looked like every other product they use, that's not the cost of innovation. That's friction you added for free. Fix it by borrowing the convention, and give that attention back to the part that matters.

Bottom lines

Resistance to something new is not proof it's wrong. Innovative products will always hear "it's too hard" at first.

Users have a limited budget for learning. Every unfamiliar element draws from it, core or not.

Innovate on the problem, borrow everything else. Best practice around the core leaves more room for the core.

Sort objections by what they point at. Friction in the new behavior needs better teaching. Friction anywhere else needs a fix.

Market education isn't something to avoid, and it isn't something to be proud of either. It's a cost. The products that make new behavior stick aren't the ones that ask for the most change. They're the ones that ask for exactly one change, and make everything around it feel like home.