Good UX and good business aren't opposites. They just move at different speeds.

Early in my career, I saw "user experience" and "business goals" as two sides pulling against each other - design wanting more time and polish, business wanting speed and revenue. Most of my frustration in those years came from treating it that way.

What actually changed things for me was realising the tension usually isn't real - it's a translation problem. Business stakeholders aren't against good UX. They just don't experience friction the same way a user does; they experience it as a metric moving in the wrong direction.

So the shift I made was less about compromising on design quality, and more about connecting the two languages:

• Tie UX problems to numbers stakeholders already track. "This flow confuses users" lands softer than "this flow is costing us X% in drop-off at this step."

• Bring business context into design reviews, not just after them. Understanding a revenue constraint early changes what "good" design even looks like for that problem.

• Protect the user experience where it truly matters, and bend where it genuinely doesn't. Not every screen deserves the same fight. Save the hard conversations for the ones that actually affect trust or usability.

• Ship the smaller right thing over the perfect slow thing. A well-designed increment that ships beats a fully polished version that missed the business window.

The best product decisions I've been part of over the years didn't come from design "winning" over business, or the other way around. They came from both sides finally describing the same problem, just in different vocabulary.

That's usually all the alignment takes.