Published on March 25th, 2009 | by Rahel Bailie1
What’s the difference in a UX name?
A professional contact of mine mused about the self-designation of “user experience (UX) designer” as opposed to the more specific terms within the UX field. His rationale is that “few individuals, if any, actually do EVERYTHING involved with holistic UX.”
My reaction, which I couldn’t fit into 140 characters, was that using a self-designation with a certain amount of specificity sacrifices practicality to accuracy. Individuals who have been hired as a single-function specialist may have the luxury of presenting as a “usability engineer” or “information architect”. For the independent consultant, this strategy can have definite negative consequences.
In my practice, I work with a range of clients, from the small start-up to behemoth multinationals, and every size and flavour of organization in between. I’ve been recommended as a writer who “gets the technical stuff” and ended up spending most of my time revamping their public site, from card sort and user research, through to information architecture and transaction flows, to the usability tests after the developer and designer have finished building it. I’ve been hired as a “usability expert” and the task turned out to be requirements gathering and process analysis – in other words, a business analyst.
Because there is a large degree of fuzziness among the management layer of those who do the hiring of UX consultants, and is compounded by HR groups asked to bring in a “usability person to restructure the site”, or an IA for work that turns out be more interaction design than information architecture, it’s important to concentrate more on describing the services provided. For many years, I described what I provided as “performance improvement for communication products” because that’s how executives understood what I could do for their companies. That might have been rewriting content, restructuring a site, restructuring content for the site; the important part for me was that the client knew what to expect as to the value I could bring to their communication vehicle.
If I were to generalize about how to handle labels, it’s to move up one conceptual level. For example, when in doubt about whether something is a car or truck, move up one level to the term “vehicle”. When in doubt about whether your clients will understand the difference between a BA, IA, IxD, or Usability Geek, move up one conceptual level to the encompassing term of User Experience professional. This places you firmly within the UX field (as opposed to a technical IA, for example), and allows you to engage in a conversation with the client about recommended processes and where you fit within that realm.