Let's kill the UX department

Let's kill the UX department!

Chad Vavra says his greatest accomplishment as a user experience director will be the death of his department and claims demand for UX specialists will lessen

I recently interviewed a candidate from the Stanford d.school for a position in my young, but growing user experience department within RFI Studios. As we worked our way through her experience and my expectations, we found ourselves on the subject of the history of UX as a department and how ours works with the rest of the organisation.  As I tried to explain my opinion of UX, agencies, and the current lack of experienced UX candidates in the job market I found myself, instead, talking about web developers.

My point was that 15 years ago when I was pursuing a creative technologist degree, and then entering the job market, curriculums didn't really teach creative coding as a practice. I had to pursue a BFA with computer science and animation art electives. That lack of curriculum resulted in a shortage of developers who were prepared to visualise the fledgling game and World Wide Web job markets. Those rare few with a natural talent for visual design and user interfaces were fought over with high salaries and silly perks. As curriculums evolved, more developers entered the job market with the necessary skills the world [wide web] was demanding. Over time, with the influx of developers who had learned or taught themselves those skills, salaries were reflected more accurately.  

I think it’s very fair to say that UX is in a very similar state of high demand, low supply. My fear is that if I overpay junior candidates because of what seems to be a shortage of contenders, how will I be able to promote and reward them later when they have gained experience and more candidates enter the market?   

It has always been my belief that user experience is the job of an organisation, not a department. But the last few years have seen UX departments being formed within organisations as specific principles and process coalesced for the constantly evolving web.  Educational curriculums such as those in the d.school with its hands-on training of user centred design, programming and visual design, are only now correcting themselves to include new UX practices. This reflects in the candidates coming from them still not fully prepared to enter the market with the needed experience. The natural result is a salary bubble for the few new candidates who have the necessary skills or experience. I believe this is the example of what is to come from other institutions.

The supply of people with UX skills will increase across all disciplines, and demand for specialists will lessen. With that change UX leadership will have to evolve. In many ways the culture of startups is already experiencing this as the limited staff must cover many roles. Decisions will have to be made regarding who in a company is responsible for the discovery and design aspects of UX. I believe visual designers and developers will ultimately be fully capable of the design tasks. As a hiring manager looking for those tasks I'm more interested in a UX person's abilities with Creative Suite, Xcode or TextMate than I am with Visio or OmniGraffle. I can't help but think it's time to pass the UX reigns in the respect of most design. 

This leaves the question of who should do discovery. One obvious option is the strategist, but strategists usually carry an MBA, the key letter being 'B' [for business] and a lack of experience for discovering and defining user behaviours. UX discovery and strategy naturally overlap in how businesses can take advantage of users’ needs and desires. In order for strategy to properly do discovery, strategists are going to have to learn to be anthropologists – a pretty tall order for the 'BA' educational systems in place.

So where does that leave me in my goal to kill the UX department? It leaves me looking for designers with liberal art degrees and capabilities in psychology, behavioural neurology, and anthropology who can learn to weave business requirements into their work as goals and outcomes. These people aren't easy to find and even harder to hire, but it's the evolution that we have to make as UX leaders if we're going to continue to improve our work as a practice.

10 comments

Comment: 1

This is an interesting idea and I think you're generally right, but sets expectations a little unrealistically.

The part that really got me thinking though was, "In order for strategy to properly do discovery, strategists are going to have to learn to be anthropologists ". I think you are 100% correct here.

Comment: 2

Provocative and unnerving. I strongly agree UX should be the lifeblood of an organization. And I feel the lure of trying to find that perfect designer who can also architect or the perfect developer who can also design. It would seem to streamline production and reduce overhead, but in an agency where the work is always different and requires novel twists to the UX, design, or development, placing too much pressure on one individual to juggle different disciplines can be extremely limiting. When a developer is coding, they are not designing. When an architect is figuring out the optimal flow for an interface, they aren't designing. You can, in effect, lose time. And more often than not, when time is a factor (and it always is in an agency) all disciplines take the path of least resistance. Engineers rationalize away UX and designers stop worrying about how a user will get from A to B. Perhaps this is where more evolved leadership comes in, but department leaders should not be at that low of a level, fretting over a user flow.

Maybe this is all solved by hiring that perfect employee, the conscientious designer or developer with highly tuned empathic perception for the user and their needs. But I can't be everywhere, man. I've already got a job.

Comment: 3

I also agree that UX is the lifeblood of any customer-facing online solution, but I don't think that this makes it easy to answer whether UX is a separate role or department. That answer has to scale to the organization, team, and product. And the latter should, in fact, introduce yet another responsibility: product management.

Just take a moment to pare back why we do what we do: ideally designers and developers engage in discovery, and in doing so have direct contact with customers in order to solve their needs. But if their job is design and development, they can't skew their time too much toward those tasks per Soapko's comment "I can't be everywhere, man."

And in our company, neither do our UX staff. It happens to be that in our organization (we do online education), we have UX staff focus on analysis, prototyping, and evaluation. And that's also very time-consuming when done thoroughly, so there's still not a ton of time left for them to do thorough discovery and strategy.

So enter product management. Online product managers work further upstream by forming and maintaining relationships across all levels including voice of customer, organizational leadership, and competitive analysis. The goal of this is much larger than good UX and design: it's making sure that the right online products are being developed in the first place. And that's where I think the UX role of anthropology is quite accurate, but it can still be too much work for even UX staff.

And circling back to smaller teams and organizations, then true enough: there won't be resources to have separate product managers, let alone separate UX staff. But then the design and development better be slicing and dicing their time adequately and stepping away from their desks several times a month to engage in user- and product-oriented research and strategy. The risk of not doing so is designing and developing brilliant solutions for problems that, at worst, aren't even there or, at best, aren't our customers' or client's top needs or concerns.

Comment: 4

soapko: I work for/in an agency too and the problem with 'agencies' is that we do rationalize our expectation. My point in wanting to 'kill' the department is that without it agency work will sink or swim. no one will be able to rationalize that it was someone else's job, which is isn't, It's everyone's.

klayon: I'm very interested in your experience. I'm not asking anyone to be everywhere. Trust me, I don't want that for me, or anyone I work with. I disagree with the notion that disciplines (like design and dev) can't skew to UX though. I was both in the last 15 years of my career and I can attest from direct experience that working from a UX perspective is more efficient to make things. I don't think it's a leap to think that our discipline will become a greater part of the educational cycle very soon.

Comment: 5

Nope. Appreciate your thoughts, though.

Agencies and Clients both have a need for user-centered design specialists, who understand how to conduct behavioral research, synthesize findings, understand the end-user's mental model, and act as strategist/end-user advocate as well as interaction designer. That's alot of specialized work to do, and we cannot expect that this important process can be absorbed by traditional Designers or Developers. We cannot minimize the importance of the User Centered Design process, nor can we expect that it is something that anyone can pick-up. It isn't magic, but it surely takes a dedicated role. Thanks for your article!

Comment: 6

I have more faith in the agency than you do Jonathan, though you're taking the title a little too literally.

And you're right, it's not magic. In fact I call perfect UX candidates 'unicorns' - because they don't exist, just like magic.

Comment: 7

I am glad to read this article. I am one those User Experience Designers *not coder* and I can say that our lives are not easy (well, which one it is?). Let me explain better...
If you look into the UX vacancies you can find a high variety of requirements to be hired: php, apache, ruby, c#, c++, java, css, hml, flash, adobe suite and so on. While most of them are justified (such as everything useful to produce wireframes, mockups, scenarios, information architecture, interaction flows, semi functional prototypes for the user evaluations and so on), the majority of them are not. At least in Europe, there is still lots of confusion. This situation generates a vicious circle: HR don't know what exactly look for when hiring a UX (I heard once 'we know we need a UX but we don't know what you -as category- can give us') and when they find a coder that claim to be a UX they are happy to hire that person because they have two skills in one person. I am not saying that a coder cannot be a ux. I am saying that if you code you don't have the time *and the point of view* to take care of the user experience. So lots of time, UX positions are taken by coders. I had the opportunity to ask to a UX manager of a big enough company what does he do (or the team does) to get in touch with the users or what kind of ux technique they use internally... the reply was shocking: we never get in touch with the user and we I just do it according to my taste and point of view. That's not ux, sorry. Ux requires users involvement at some stage and I am convinced that it creates a good value for the company in terms of quality of the final product, quality of the internal job and processes, market strategy. The new courses in Interaction Design and User Experience are very interdisciplinary: from graphic to marketing, through sociology, front end editing, art etc.
Be a pure UX is fantastic and, as every other job, it requires to be constantly update and never stop to learn which is exciting... but the life of a pure UX is not easy at all! :)

Btw, my background is sociology, anthropology, communication, political science, interaction design, graphic

Comment: 8

antuneleta: So knowing to code is good for being a UX'er, but knowing UX is too much for coders? Also, I agree that certain aspects, like user research, aren't right for coders, just like prototyping isn't right for strategist.

Overall my main point is that UX is the role of an organization, not a department.

Comment: 9

This article resonates with me on many levels (thanks Ronnie). My career has twisted and turned until I landed in UX. I am not a developer by any means, and only occasionally interested in the actual user interface itself. That may sound strange and make one think that I couldn't possibly be the right person to design the user interaction model. But, in not making the interface my focal point I have found a good measure of success in designing the interface.

I am more and more interested in UX as it supports the business and increasingly chartered by my bosses to apply UX principles to improve business processes and assist in strategic planning. Of course, eventually what is learned from those business exercises trickles down in to the design of the service (I work for a cloud computing company) and then the design of the interface in to that service. I am seeing first hand how moving UX professionals upstream in the planning and product/service design process is where true transformation can take place for a business and its customers. The modern economy demands services and products to be fully integrated with process that is adaptive to the rapidly evolving need of customers. And there lies the BIG opportunity for the UX community.

My background is history/anthropology/film major turned business analyst and now UX designer.

And from all of my different training, I would actually say that history is the most important subject of all in approaching UX. Anthropology, psychology and sociology are sciences that you need to understand to be effective with CI. But history tells us the "why", the higher truth of what is driving the human to interact with the product or service. The actual design of the interface is many, many levels down the value chain from the "why".

History establishes the broader pattern of behavior and the cycles of change. No strategy can be built for a business without the context of "why" their product or service is useful to humans at this exact point in history and where in the cycle of change the product fits. (is the product a result of change, a cause of change, etc.?)

Any effort to understand that bigger picture will put your user's experience in to context and better inform the design effort. Thanks Chad for helping me crystallize my own thinking!

Comment: 10

chadvavra: all the knowledge is good for both! my point is that it is just a matter of points of view and focus. Doing user research and all the other ux stuff gets time and focus from other activities. I think that the best comes from the meeting of the two points of view. The UXer creates scenarios, analyze behaviours, the market context, the context of use. According to this, the UXer shapes the product and proposes changes. Those changes sometimes are difficult to achieve in the short term or simply are not achievable because of the availability of the internal resources. The important is to figure out what the product can provide and what is the best and successful path to follow. Coders know what they can do and what it is possible to achieve in terms of resources. The meeting point between ux and code creates the best possible solution.
About the discussion 'organization or department', I think that the UX needs to be spread across the organization. The separation between departments creates a wall between roles. Working together allows to discuss and exchange thoughts all the time. Apparently it is what Apple does. They don't have a ux department but ux designers in every department.
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