The most underrated design skill at an enterprise company is knowing how to work within a design system rather than around it. SHIELD wasn't a constraint, it was infrastructure. Building the Language Indicator within its rules meant the pattern could be adopted across the entire site without a redesign. Systems thinking isn't just about the component. It's about the component's relationship to everything that already exists.

Cultural context is a form of user research you can't conduct in a usability test. As a Latin American designer, I understood the difference between a Spanish interface that was translated and one that was localized: the micro-copy choices, the tone, the expectation of being genuinely considered rather than accommodated. That understanding shaped decisions no competitive audit or A/B test could have surfaced alone.

The hardest UX problems aren't the ones where something is missing, they're the ones where something is partially present. A half-translated website is more disorienting than no translation at all, because it creates an expectation it can't fulfill. Designing for the gap, the in-between state required as much empathy for user confusion as for user intent. That's a design problem most systems ignore.