I am what I am
In the Cubicle of the Unknown Consultant, there hangs a homily captured from a well-circulated e-mail:
You know you have a job in technology if you need a PowerPoint presentation to explain what you do for a living.
Generally, user experience designers try to maintain a slim but firm boundary between themselves and, well. . . you know. . . technogeeks. After all, we're there for the users, not the elegance of the code.
But the identity crisis--and the inability to describe our role concisely--is an issue we share in common. I used to be a college teacher. Little or no confusion there, and a limited questionnaire: What subject? Which college?
Then I became an Instructional Designer. That provoked a bit more conversation, but when I met other IDs, I felt that I knew, in general, what they did. And, after some preliminary explanations (no need for PowerPoint), so did clients.
Then I entered the world of user experience. My first job title was "Cognitive Engineer" (cue the Devo mix). The title sounded scientific, alluding back to UXD's evolution from physical ergonomics. Still, it gave folks virtually no idea of how I spent my working day, or what I could bring to the table. PowerPoint presentation v1 was born.
During the boom, user experience proliferated, drawing talented people from backgrounds related through tangential. In my experience, few colleagues came equipped with formal training in HCI; however, they did bring relevant skills. Some team members were wireframing virtuosos, some transitioned from a visual design background, and others could code as proficiently as they could design.
Client expectations therefore varied wildly: does a single person architect and provide visual design? Does a usability expert also do HTML? Titles began to proliferate, compounding the confusion: am I an IA? an Interaction Designer? a User Experience Designer? What's the difference? Or are they all the same? How do we define ourselves to each other, to our users, and to the people who may be interested in what we can do for their sites and applications?
We've evolved way beyond PowerPoint narratives--it's crucial for us to delineate roles and their core competencies while retaining the uniqueness and synergy of individual skill sets, or we will invent a (user-unfriendly) geekdom all our own.
Comments: 1 so far
Leave a comment
About Pathfinder
Follow the Blog
-
Get a monthly update on best practices for delivering successful software.
Subscribe via email
Subscribe via RSS
Categories
Topics
Archives
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
Blogroll
Recent
- Elements of Testing Style
- Aesthetics and Web Design
- Asterisk-Java Testing with Groovy
- 3 Misuses of Code Comments
- Fluently NHibernate
- Digging a Hole and Covering it with Leaves — The Software Development Version
- The Importance of User Experience - Do You Understand It in Your Bones?
- Writing Your Own Protocol With NSURLProtocol
- What’s In Your Dock: iPhone edition
- Feature Fatigue

It seems that your trackback url isn’t working (I couldn’t ping it with haloscan).
Anyhow, I wrote a post linking to this article at:
http://stupidapp.blogspot.com/2006/09/what-am-i.html
Comment by Guy, Monday, September 11, 2006 @ 2:22 pm