Inconsistency isn't a polish problem. It's an operations problem that happens to look like UI.
The symptoms are familiar:
- Rework when the "quick" button doesn't match the system.
- Slow onboarding: "which button is canonical?"
- A11y fixes bolted on after launch.
- Performance debt from one-off CSS that nobody owns.
~90%, one real number
I watched one consistency fix cut reclamations ~90% on a product. No full redesign. No new features. Same action, same component, same behavior, everywhere. Users stopped making the same avoidable mistakes. Support tickets dropped. Revenue impact wasn't on the original roadmap, but it showed up. Alignment, not magic.
Design engineers protect integrity
Sometimes that means saying "use the system" when a PM wants a gray button by Friday. That's unpopular in the moment. It's cheaper than five sprints of cleanup.
Quick hacks compound; so do systems. Pick the compounding you want.
Find where the tax hides
Run the Health Check on this site, or grab the 40-point audit checklist. Score tokens, parity, governance. The red cells are where you're paying, often in rework and support, not in Figma hours.
It doesn't have to be this way. Honest next steps beat another hero screen.