« Design as an Economical Function | Main | Information vs. Perception - new threats to corporate branding »
We live in a Google world. Information/answers/solutions await us. We want to search, and so other people want to label, categorize, classify. New (and horrific) words like folksonomy emerge to describe the schemes by which we can sort and label the world around us.
I don't disagree that there is power in being able to give something a name, and then a definition, to ensure that groups of people can converse together. Of course, creating common language can have the opposite effect - a shibboleth being a word that establishes membership in a group (if you know it, you're in, if not, you are out) - obviously shibboleth is itself a shibboleth.
I grew up, professionally, as an interface/usability/interaction person. But I resisted classification, no doubt to the detriment of my own skill development and employment prospects. People wanted to know if I was designer, a tester, a visual person, a graphic person, a programmer, or what? I was none of those things, but I still had skills. I just didn't know how to package them and describe them within the terms that were in use. Ironically, as I moved away from that field during the early days of the web (when the field boomed enormously) the definitions and roles exploded - but it has only become worse. Now we see terms like IA (information architecture), UE (user experience), UX (also user experience), UCD (user-centered design) (and many more) and then all the groups (here, here, here) that emerge to try to fix all the cultural problems that result. And guess what many of the discussions inevitably end up focusing on? What is {IA/UE/UX/UCD/etc.}? It seems a painful cycle of self-definition and then regrouping.
This obviously holds appeal for some and enables them to work with words and ideas to really nail down what is important, in order to best define, and then implement, the key offerings.
Personally, it makes me twitch. I just can't deal with it.
I recently posted details of an upcoming webcast about ethnography to the Discovery mailing list and received the following reply
After reading the info on it - it reminded me of how frequently the terms "ethnographic research" and "in-context research" (and other variations) are used interchangeably . I've tried to distinguish ethnography from in-context interviewing by explaining that in-context interviewing tends to include more direct questions and directed behavior than ethnography.
I have tried to sidestep these details in my conversations with people because I'm not sure how it helps to debate what is "ethnography" and what isn't? I try to focus on the overall process which I'm involved in:
Examine users (consumers or other) in their own context
Infer (interpret/synthesize/etc.)
Apply to business or design problems
And what about us here? Seems like we're establishing a common vocabularly, common sources, interests, disciplines, passions, and inspirations, without worrying too much about design management, innovation, strategy, business, design thinking, or whatever. I'll point to About, With, and For (Hi Brianna!) as a conference that has been successful while deliberately staying away from the navel-gazing self-definition and getting on with the business of what it is we're about. I like the forward momentum of this community and I'm happy without too much definition, as long as there's alignment. And I believe there is.
Permanent URL to this entry: http://www.cph127.com/cph127/2005/08/title_goes_here.html
TrackBack URL for this entry:
https://www.typepad.com/services/trackback/6a00d8345592f969e200d8351df2e653ef
Listed below are links to weblogs that reference Title Goes Here:
The comments to this entry are closed.
CPH127 is a sense-making initiative. We aim to create a open dialogue around the profound understanding of the leadership, organization and strategy of creative business functions with the aim to create new value (for customers, employers and stakeholders.