The new UX skills

The new UX skills

The role of the user experience designer is changing. It’s becoming less about ‘owning’ experience and actual design and more about facilitation and collaboration, says Lee Allen of TH_NK

What is it with user experience CVs? UX has never been about simply churning out wireframes and yet that’s what I’m often confronted with. Obviously, a strong portfolio is really important, as is a strong design rationale, but what I always look for, above all else, is quality of communication. And that’s becoming more important as our role is changing. UX is becoming less about deliverables and more about facilitation. And here’s why.

The move towards Agile development has seen the uneasy joining of two processes that don’t necessarily complement each other: Agile and UCD (user-centred design). The problem lies in two very different outlooks. To developers, iterative means incremental growth, while to designers it means multi-revision and honing of the design – and as a result, the processes conflict.

For the two disciplines to effectively complement one another, we need to be more collaborative. The trouble is that in truth, people don’t always know how. Often, in bigger teams the transfer of knowledge slows down and learning becomes harder through a mix of understandings and perspectives.

I’ve heard of Agile projects where people slip into the old mindsets of work being passed down the conveyor belt of a linear development process. This way, great design intent becomes lost in the complexities of build and timings, with the end result rarely being true to the original ambitions.

So what’s the solution? Well, for a start, UX designers need to understand the nuances of
the technology they are designing for. Equally importantly, developers need to recognise the psychological and cultural factors, interaction designs and, perhaps even more importantly, the power that emotional engagement can play.

We must specialise

Couple all this with the myriad of devices and technologies we are designing for and it becomes obvious that it can’t be done alone. No one person can effectively combine their specialist skills and knowledge and take on all these other roles too.

So, while interdisciplinary knowledge is invaluable, specialist roles bring specific skills that the practicalities of projects will always require. Yes, UX designers will still design, but I really don’t see that as the only core skill any more. I wouldn’t want my design team creating deliverables in isolation. I’d want them to be talking to people, to be encouraging, challenging and educating – both other team members and clients – and getting them involved too.

So what is the role of the UX designer going forward? I believe it will be one of a communicator, an educator and, above all, a facilitator. It will be about possessing the right skills and the passion required to collaborate and solve design problems effectively. Together.

I see the role continuing to unearth insights into the behaviours we are designing for. But I also see it as connecting the dots between the various research silos that inevitably exist. We’ll also need to work together with analytics for a better understanding of both the ‘what’ and ‘why’, and then feed these learnings back through clear principles to help communicate meaning and create shared models of understanding.

Our role will become more about helping to facilitate the design process by building creative environments and then utilising methods in which we all learn from one another.

So, as I sift through my latest batch of CVs, I’m not just looking for a great eye for design, but the wider research, synthesis, communication and facilitation skills that will enable project teams at TH_NK to be ever more successful. And if we all work together and learn from one another, we can take our industry to the next level.

This article originally appeared in issue 217 of .net magazine - the world's best-selling magazine for web designers and developers.

5 comments

Comment: 1

Great perspective on the issue - adopting the shift of from creator to facilitator will actually allow UX designers to FIND the best solutions to their problems (through collaboration) rather than trying desperately to INVENT them. As you say, they just need to be able to let go of the desire to necessarily own the idea.

We've seen more and more CVs from people with a good understanding of the importance of UCD (including graduates), the challenge for them is how to actually undertake that work. A UCD process in the wrong production environment will most likely fail to produce what it intends to.

Agile can actually allow UCD to do what it does best, as long as they collaborate with the developers rather than just pass them stuff.

There's a Nielsen report describing the conflict of the two methods which with anecdotes from teams working in that way - a much nicer way to get your head around it than project management books on the topic...

http://www.nngroup.com/reports/agile/

Comment: 2

I really enjoyed reading this and very much agree with the things you say. I feel like I'm more of a facilitator of stakeholders these days rather than a pixel-pusher. My question for you is this: How does one convey this in their CV?

Comment: 3

Great article, thanks! I've had the experience of bringing together a design team and an agile mobile development team to form one mobile studio, that is, one team with one goal: do develop great apps. The role of the UX designer is fundamental to keep things functioning so I absolutely agree that communication skills are crucial as well as the design experience. In our teams, the UX Designer is a co-PO or a representative of the business vision inside the team.

I wrote about our process on my blog:

The process that has been working for us:
http://www.uxmindset.com/2011/11/lean-ux-agile-development-the-next-big-...

A tool we developed to bring product mindset (and thus design mindset) to developers:
http://www.uxmindset.com/2011/11/the-product-canvas-bringing-a-product-v...

Comment: 4

I'm no Agile expert, but the role you describe sounds like that of the Project Manager.

Comment: 5

This article is spot on. I believe the keywords are communication and synthesis. The UX architect is the person with the grand vision, the professional who understands all the layers of a design challenge, from technological development to user roles and behaviors to marketing and business goals. This person has to synthesize the parts into a cohesive whole, directing the whole process, but always maintaining open channels of communications as a two way street. I believe this makes for the best results in any experience design project.
June issue on sale now!

The Week in Web Design

Sign up to our 'Week in Web Design' newsletter!

Hosting Directory
.net digital edition
Treat yourself to our geeky merchandise!

site stat collection