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.
Popularity: 9% [?]
Comments
One Response to “What’s the difference in a UX name?”
Leave a Reply
Recent Posts
- Technology won’t fix a bad strategy
- CMS Facts and Myths, and Why Process is So Important
- Skills to transition to content strategy
- Content strategy: The skills conundrum
- Abilities and aptitudes for a content strategist
- The extraordinary world of content strategists
- Dispelling More Content Myths
- Dispelling Myths about the Content Lifecycle
- Content Lifecycle
- Satisfying the cat: a user-centered design metaphor
Categories
Tags
accessibility ann rockley career development CMS content as asset content convergence content lifecycle content management content strategy convergence DITA Duo Consulting experience design Flash information architecture integration intelligent content interaction design management marketing mentors microformats open standards politics processes professional development ROI search section 508 services single-sourcing social media STC structured content syndication taxonomy TechCraft translation Twitter usability user-centered design user-generated content user experience value XMLPopular
- Using topic-based writing to meet aggressive deadlines
- Flash pages, skip intros, and other annoying content
- Content strategy includes convergence, integration, and syndication
- Content strategy and the new face of documentation
- Redefining content strategy
- A practical definition of content
- CMS selection practices need maturation
- The Content is Not in the Tool: Using Blogging, Microblogging, and Related Social Media Tools to Get Jobs and Influence People (or not)
- 5 Top Business Benefits of Content Re-Use
- Having community means growing community
Random Posts
- RT @s2d_jamesr: RT @elreiss: new article on Johnny Holland: "In defense of 'making it up as you go along'" Comment: http://bit.ly/9NCIQk 1 day ago
- Hastings St near Nuba. Roller blader ran a red light and smashed into truck. She, furious, gestured the truck to leave. Big dent, for sure. 1 day ago
- Canadian? Want to win a free copy of @lukew's "Web Form Design"? Then enter our contest! http://is.gd/dRenr Pls RT 1 day ago
- Definitely worth it! 50% off "Storytelling for User Experience" by @whitneyq & @storykevin Use code 50offST: http://is.gd/dNu6x Pls RT 3 days ago
- More updates...









Latest Tweets
RSS feed
Twitter
Hmmm, that muse looks familiar.
You make a great point about the trade-off of practicality to accuracy, and I totally agree with your prescription about moving up a general level, which is what I would have said too beyond 140 characters. It’s not about the title, it’s about conveying the objective of addressing user needs.
I love how you describe shifting from one service to the next, even within the scope of a given project. So true even when not intentional, but this really suggests how a contractor should shape and sell themselves. Good stuff.
I like “user experience professional” and I’ve even seen “user experience architect” which is a workable, if not a bit too self-invented sounding, but I don’t like “user experience designer” because I’m seeing it associated more and more with people who do not have such real backgrounds in UCD, IA, content strategy, etc., but rather have have learned to use Flex, Adobe Air, Silverlight and the like and suddenly think creating UI’s with this technology is what UX design is about. Basically, I’m seeing a lot of people calling themselves UX Designers that shouldn’t be at all, any form.
Reminds me of a relevant article by Karel Redenburg at IBM, What’s Messing Up Our UIs? http://karelvredenburg.com/2009/03/whos-messing-up-our-uis.html