I enjoyed this article and agreed with all the points. However, I am calling bullshit on the title "Experience Architect"
I enjoyed this article and agreed with all the points. However, I am calling bullshit on the title "Experience Architect"
So when you make the change to "Experience Architect," dropping the "User" prefix, it becomes vague to the point where I literally had no idea what you did for living, although I guessed from the article's content that you worked in UX somehow, presumably designing user interfaces or consulting about them. But as someone who (rightly) rails against vagueness in marketing and against bullshit that masquerades as expertise, I would think you'd be averse to a title which trades clarity for puffery.
And oddly enough, I wrote an article about that too. :) Maybe this will help:
http://thehipperelement.com/post/47950319899/do-you-have-the...
As someone who values making scientific decisions, I would challenge you to survey people in the tech industry (programmers, visual designers, UX experts, etc) and ask them if they know what an "Experience Architect" does.
It is difficult enough that some people don't know that user interaction and user experience are jobs different from a graphic designer and front end developer. But I think user interaction and UX are at least somewhat known. As you said: "If you do information and interaction and UX, go with “UX” as a job title."
It sounds like "UX Designer and Information Architect" might be accurate in your case? And it sounds almost as impressive as "Experience Architect" :)
As far as I'm concerned, if you aren't designing buildings in the real world, you aren't an architect, and have just co-opted that title in an attempt to appear more that you really are.
we get no respect, yet everyone wants to be _like_us._ :+)
-bowerbird