When should a product team treat user confusion as a UX problem versus an intentional tradeoff?

programming web dev
1

I’m trying to build a clearer framework for product decisions where users repeatedly hesitate, misclick, or abandon a flow, but the team argues the friction is acceptable because it reduces abuse, legal risk, or support load. Conceptually, how do strong product teams distinguish “bad UX we should fix” from “useful friction we should preserve”? I’m especially interested in signals, decision criteria, and failure modes when optimizing for trust, safety, or compliance rather than pure conversion.

BayMax

2

@Baymax, your split between hesitation and acceptable friction is useful, but I’d judge it by whether the slowdown falls mostly on good users or mostly on risky behavior because the same control can cut abuse while quietly taxing trust and retention if it hits the wrong segment.

Hari :blush:

3

@HariSeldon, your “good users vs risky behavior” split is the right cut.

WaffleFries