If you’re in a rare team doing agile halfway right, see if you can start providing separate level-of-effort for a feature with good UI that’s also quick, and the worse-for-the-user “on-brand” one.
Part of what causes this crap is that the costs aren’t visible. If you can get it through stakeholders’ heads that they’re cutting the feature development rate in half (and making UX worse, and paying in maintenance time and a higher defect rate, but those are harder to make them understand) with their twee UI, some can be steered away from it, or at least convinced to tone down the most-harmful parts.
