What follows is a response to Adam Connor’s attempt to articulate his personal definitions and beliefs about UX Design. I appreciate the effort required to make such an attempt, and respect that these are his beliefs and will try to respond as such.
It is probably worth your while taking a read of Adam’s piece before continuing…
So, let’s begin.
Reason 1: I agree with the premise here, that a person’s experience of the ‘thing’ we’ve designed is the result of a very complex interplay of many, many variables over which we have little to no control. That said, someone on the team whose role it is to consider what that interplay looks like to a potential user (see note below about terminology) feels like an important inclusion. And whilst I laud the sentiment that everyone should be thinking about it, the reality is most people don’t, and many lack the capacity to start.
The reason I say that is many people lack the capacity for empathy needed to adopt someone else’s perspective in any real sense. Yes, that’s why we involve users in our design process – from research through prototype testing etc – but that doesn’t remove the need for a designer to be working through the implications of that perspective on the ‘thing’ we’re designing.
Reason 2: “The UX Designer should be defining the experiences they want users to have.” In many respects, this is all a UX Designer can do. In many cases, they don’t even do that. Or they focus on a narrow part of experience – typically functional. It is rare you see a designer intentionally defining emotional qualities for their design as objectives. You do see it amongst brand strategist, but this tends to be an articulation of an outward-facing quality rather than inward-facing, customer-centric qualities.
Reason 3: I agree with all of this, but you lost me when you said “Design is problem-solving, plain and simple.” Design is, in part, problem-solving, but it’s a lot more than that, too. Yes, it’s the “creation of a solution aimed at achieving a specific outcome/goal.” But it’s also the process of reaching a shared understanding of what that specific outcome/goal should be; and framing (or re-framing) the problem itself so that our solutions have significance and meaning. Design is also craft, and facilitation, and exploration, and creativity, perseverance and a deep-seated dissatisfaction with the world around us. At its more self-expressive end Design is very akin to Art, and very distant to ‘problem-solving’.
Reason 4: Totally agree with this. Case in point: the unboxing experience begins with the packaging.
Reason 5: This feels very much like a post-rationalisation. There’ll be evidence of individual designers who thought this way, but I don’t believe an understanding of, or an intentional objective coached in terms of, experience has formed an established part of design education until relatively recently.
JJG and others articulated a relatively narrow, technology (or, more specifically, Web-) centric definition of User Experience. We’re continuing to explore the more abstract, medium-independent understanding of experience and experience design, and gaining a richer appreciation for the area as a result. We’re seeing a parallel exploration in other fields, influenced and driven by similar discoveries and research.
Any sentence that includes “<something> is just design” is going to bristle with me – I think it’s a gross simplification of design and – see below on terminology – not accurate.
Notes around terminology
I think it might have during a conversation with Jon Kolko that he said (and I paraphrase from memory): “I see three problems with the phrase ‘user experience designer’. i) User is such a narrow term, and assumes a context for both the person and designed object that isn’t necessarily true. ii) it’s conceited on the part of a designer to think they can ‘design’ something as intrinsically personal as an experience. And it’s arrogant to think we have control over such a complex, personal thing. iii) Most of what people practice as ‘UX Design’ isn’t design at all. It might be creative; it might be successful; but it isn’t Design.”
I agree with him as far as it goes, and this is broadly consistent with Adam’s thoughts in the section: “Experience Design does exist”
It’s easy to fix the first one by dropping the word ‘User’ and dealing with the now-absent technology connotation in other ways, if necessary. The second point can be covered by inserting the word ‘for’ – i.e. designing for experience. It acknowledges the difficulties of closely and prescriptively defining a person’s experience, whilst maintaining experience as the intent or goal of the design activity. The third is much more difficult to resolve, but we’re seeing (I believe) a growing trend towards experience design work being undertaken using processes and methods that are more true to the intent of Design.
Comments welcome – either here or at Adam’s post where this originated.