I’ve been a UX designer and a UI developer for a long time. I’ve decided to start new blog posts about those experiences.
For the last several years, there have been a huge number of jobs around UX. In reading the posts, it is obvious they don’t really understand what they need. I see a ton of generic UX skill sets being posted. “UX designer who can research, create wireframes, do visual design and be a front end developer. WHAT? No, that isn’t how it works!
User Experience as a separate practice from web or mobile design isn’t all that old. One practiced what we call UX now but the title you had as a job was probably something like designer, or researcher, web developer, front end designer and so on.
Before we can move forward with other posts, we have to get the business of what, who, how and when out of the way.
Roles and responsibilities
This is something that even my own team doesn’t seem to understand. When I see the job posts, it is clear someone doesn’t understand. I’ve been a hybrid for a long time, meaning I design and develop. I ran a conference for 4 years on that very topic, but the UX world isn’t that easy. Being good at one aspect of UX doesn’t mean you are, or can be good at another aspect.
Typically a PHd or the very least a Masters. Could be in Psychology, could be Human Factors, but these are the big brains. They find the data the company has, or they create ways to extract the data. They are the ones who create personas, or Behaviors and make sense of who the user of the product is. They are also the front line when it comes to understanding the customer lifecycle and know how to put all that data in a way that clients understand it. They are the ones who ask for the business plan, they make the Experience and journey maps. They are also the ones who make the design plan for the rest of the team to follow.
To truly understand what the customer needs, and to sort through all that data takes months sometimes. This portion of the UX world is sorely misunderstood and I see people all the time dismiss this as something they don’t need. Yes, sometimes it is expensive to have someone like that on a team, but they are indispensable. The time they take is time well spent. It is just because so many companies, like the one I work for, always had the Product managers and the BA’s do that portion of the design. It isn’t the same, but having a Product Owner understand the data is awesome.
Often these are also the people who facilitate the user testing. Focus Groups, usability testing, and facilitating those tests isn’t easy. You have to be trained, period, in how to ask the right questions to get the answers you need instead of something you can’t use. I’ve watched plenty, and I am telling you, I know I couldn’t do it without a lot of practice.
This person makes sense out of data as well, but moves it to the next stage. Information Architecture, Information Analysis, task flows, more detailed Experience and journey maps, spec docs, wireframes all happen or start here. Could a UX Strategist do this? Sure, but most of the ones I know couldn’t draw their way to a decent wireframe in Axure or tool of your choice, to save their soul. But, the role of the interaction designer is to format all that data in a way that it makes sense to the client. All the pieces I mentioned above, it pains me to say that clients don’t appreciate all of this either. They seem to get wireframes, but not everything else. So in your Design Plan, you should list them all, but you don’t have to put dates to everything, so they get what they want, but you can still do what you need to get where you need.
Can an Interaction Designer manage the data? To a point, but these people have been trained in ways a typical Interaction Designer isn’t. A researcher could more easily also create all those things listed. The wires, and IA and flows, so if one wasn’t needed, it would be the Interaction designer.
This is where typical jobs think things begin in the UX world. It is something they can understand. It is also a place most clients think things begin as well, for the same reason. Everyone can connect with colors, images, icons, logos, graphics and fonts. When a client sees a wireframe, they are often still looking for a look and feel, and in the slightest details they are looking at the shades of gray and if you put ANY color in somewhere, they see it as a final color. So it isn’t surprising they are impatient to see what the visual design for the project will look like.
As a manager in the business, it is still difficult to get the right visual designer inside the UX team. I’ve had previous print people design something for the web, and I get inconsistent spacing, tracking, kerning and someone who just doesn’t understand the web. Mobile designers, forget it. Almost impossible it seems to find the right people. Maybe it is just Kansas City. Maybe all the talented people have moved out of town. I am just kidding, I am sure they are out there, but they are fewer and farther then I’d like.
This UX team members job is to not just make things pretty. A common misconception from the Product owners, all the way to the President of the company. They often further the interaction design. They make the spec doc from their visuals for the developers to follow. They’ll make the annotated wireframe sometimes, and depending if the team’s members stop here, sometimes they also make the assets for the developers.
Front End developers, UI Developers, UI Strategists, Design Realization
So many names. Interaction Designers seem to forget about these people. I know a ton of Interaction purists who ignore the UI folks, not deeming them a part of the UX team. The second you forget about this part of UX, you have also discounted the developer. Often they are the only real liaison to the dev. And, the second you discount the developer, you have a crappy product. The person making the wireframes knows what the persona wants, they understand the data, but they don’t have knowledge of the back end of the product like the developers do.
I started speaking at developer conferences in 2006. I was often the only designer at those conferences until somewhere around 2009 or so. My first D2W Designer/developer conference was in 2010. It was born from a frustration I saw where designers complained about developers, and developers complained about the designers. These people didn’t often talk. If you look at websites and applications from that time period, you can tell! Things didn’t work as well as they could have because of it.
In the UX team, this person can have multiple roles. They can help the dev teams get up to speed on new technologies. They can make the assets and the spec guides for the designers. They can help with the adaptive layout of the new website. They can also help make the graphics like icons and things for the mobile world where multiple sizes are needed.
On our UX team, they are the ones in charge of all the prototyping as well. We often have complex interactions to test, and we test a lot. We have many, many products, both for digital and retail. Testing is essential, and getting the right interaction in front of customers to test is also essential.
In the days, weeks and months to come, we’ll explore all aspects of the UX world. I hope you join me.