4 ms·
"UX designer" is a bit of an ambiguous phrase, and it gets the correct amount of sarcastic scorn for being a buzzword. But I think it means something more impo
by calinet6 13y ago
"UX designer" is a bit of an ambiguous phrase, and it gets the correct amount of sarcastic scorn for being a buzzword.
But I think it means something more important: as you say, good UX requires a recognition that everything that goes into your application contributes to the experience. Software design, copy, marketing, UI, etc. etc. Everything. We all know this and understand this.
What UX is, then, is software quality systems engineering. "Everything that goes into the experience" is no longer simply visual design or UI components, but a complex web of inputs and influences to manage in order to ensure quality. A good UI designer has one piece of that puzzle and ensures the visuals and interactions are spot on, but a good UX designer takes all that and more into account and extends their influence to many other areas outside the visual. It's not their job to do all the work, but it is their job to manage the systems in place to ensure the experience is high quality.
Software is getting more complex and more interesting. The "UX designer" moniker is just a response to that; a recognition that UI designers are becoming more holistic and with wider reach. They are becoming quality management systems engineers. This requires more than just UI design, though most UI designers probably naturally have the skills and knowledge to make it happen.
It's a positive development IMHO. You may not like the broad nebulous term UX, but I think if we think of it more as systems design, maybe we can start to pin it down and make it a useful job title.
- AJ007 13y agoI see strong parallels between UX designer and game designer. It was not until more recently that it has become generally accepted that everything from time killing mobile games to enterprise software demands good UX. Decades ago game designers figured out that a good UX meant a larger player base and ultimately more sales -- rather than contracts and inescapable legacy lock ins. UX is about creating a clear, intuitive experience for the user (the front and back end work that makes that possible.) This is done through consistency of patterns, both unique to the application and drawn on existing and historical work (also makes for a good argument against software patents, but that is another issue.) At the very least, this requires some one or a group of people to create an agreed upon design document from the start. Steve Jobs view of the liberal arts goes a long way in explaining UX. Everything matters. That hardly means every single team member should be an omniscient visionary with hundreds of niche interests.