(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), m=s.getElementsByTagName(o)[0];a.async=1;a.data-privacy-src=g;m.parentNode.insertBefore(a,m) })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); ga('create', 'UA-1596564-1', 'auto'); ga('send', 'pageview');
Home » NewsBlog » Are We Taking the “U” Out of UX?

Are We Taking the “U” Out of UX?

What is a UX designer?

I recently saw a great ad for a senior UX specialist from MathWorks. Some excerpts:

  • Work with the development team to follow a user-centered design approach as you work collaboratively to brainstorm and design innovative solutions to complex problems.
  • Make recommendations to team members about which usability methods to use to answer their questions about users and design directions based on projects’ needs, goals, and constraints.
  • Work closely with team members to conduct user research, identify pain points, develop user profiles, and create task lists.
  • Collaborate on paper and functional prototypes.
  • Run usability tests, conduct interviews and site visits, organize surveys, and perform other usability assessments you think are appropriate.

It outlines exactly what I would expect in a UX job. We learn everything we can about a project from stakeholders and competitive products, find ways to research what users want and need, evaluate those needs with stakeholders, modify the project plan, and create solutions which are validated with users before finalizing the product.

But when I was looking for a new gig, that was the exception. Many of the job descriptions I saw asked for a wide array of UX skills, with some even asking for more than listed above. But it seemed that they really wanted a visual designer who could prototype.

From a senior UI/UX designer ad:

  • Experience with testing and usability labs and rapid prototyping experience
  • Ability to create clear and engaging visualizations
  • Deep knowledge in understanding what engages and motivates users

Sounds like they are looking for someone well versed in research, usability testing, and prototyping. But the more urgent need is reflected in the request for “perfection” below:

  • Project work demonstrating strong UX process and perfect detail for visual and interaction design principles (IA, IxD, typography, layout, hierarchy, color, composition)

Do you think they’ll hire someone who can conduct user research, wireframe, and test? Or someone with a stunning visual portfolio?

Perhaps that reflects the ‘UI’ part of this want-it-all job description. Let’s look at a pure UX designer spot which asks for:

  • Excellent analytical skills
  • Extensive experience in practical user research, information architecture, interaction design, and user-centered design process, as well as user experience principles and techniques

Sounds great! But its true colors are shown in the next requirement:

  • Translate ideas/concepts into premium visual designs

User experience is a huge buzzword these days. Although seemingly self-explanatory, some companies aren’t getting the point—they’re still overlooking behavioral experience in lieu of look and feel. Many of the ads I saw reserved their most specific and vivid language for the visual design end of things. It left me scratching my head and wondering if only the most sophisticated—and largest—companies truly wanted UX and had the budget to support it. Are other companies just paying lip service to the current buzz by hiring visual designers and labelling them ‘UX’?

A drift away from research?

User researcher Alan recently left an Atlanta-based company with a large UX staff. In his first two years there, he had participated in many different types of user research around the country. However, in his last year, he found his research marginalized.

“My new boss didn’t care about doing research. It seemed the company as a whole was giving it less importance. Instead, they would run design thinking workshops and go straight into development. Any research or usability testing was left to the end, to rubber-stamp the solution.”

This is especially jarring as the company is known for taking UX seriously.

Buzzwords—such as UX—can suddenly zoom into prominence, and I can’t think of any in the industry bigger than ‘design thinking.’ According to Google Trends, web searches for design thinking have quadrupled in the past five years.

Chart showing increase in design thinking searches from December 2012-June 2017.
Searches for ‘design thinking’, December 2012-June 2017 (Source: Google Trends)


The first step of the design thinking process is empathize, where you engage and observe users to learn how they talk about work while watching them to learn how they truly approach tasks. In other words, it is user research. And who does research? UX folks! It’s not difficult to imagine IT project leaders and stakeholders bypassing this step and moving straight to steps 2 and 3, where they define the problem and brainstorm solutions. That’s their comfort zone.

In “Five mistakes of beginning design thinkers,” Dana Mitroff Silvers, a design thinking facilitator and digital strategist, writes, “I’m frequently asked by clients to skip this phase and jump straight into problem-solving.”

She also describes an experience I’ve had many times, where companies block access to users—and a research phase. Many times, Silvers’ clients ask if they can skip this phase because they “already know what their audiences need and can speak for them.”

This makes sense to me. Teams bypass the unfamiliar empathize phase and jump straight into defining a problem and its solutions. This is how development has worked in the past, and, without training and coaching in empathy or a full understanding of its benefits, it’s easy to skip empathy. I checked this out on my next interview, with a company that told me they needed a hybrid UX/visual designer. I asked them if they were using design thinking, and the director of product answered, “yes.” Did they skip the empathy step? They sure did.

If a company just follows the last four stages of design thinking—design, ideate, prototype, and test—what does a UX designer look like? I think it’s a visual designer who can prototype.

Segregating research and design

UX architect Alyssa recently had a user research contract with a large telecom firm. She found it disappointing that the designers seemed to have no accountability to follow the research findings. Instead, researchers performed a new usability test every week or two and threw them over the transom to the designers, with no sense of whether designers would follow the recommendations

That doesn’t seem right.

I’ve noticed more and more companies splitting their UX practice between researchers and designers. Problem is, “UX designers” are usually expected to handle not only interaction design, but visual design as well. Although the advent of easy-to-use tools makes it easy to create clickable prototypes, these are two different skill sets. I’d expect interaction designers to analyze behavior and workflow and act as user advocates; visual designers promote the brand.

The split of the design teams into researchers and designers might be hampering effective software development. To truly understand the user, designers need to develop empathy. They, and other team members, can gain this by conducting user research or usability studies—or just by being present during research efforts. This locks in the user’s successes and difficulties and gives the designer a sense of what is truly important, which will pay off in more targeted designs. Besides benefits to the designers, regular user research keeps a company informed of user expectations and behavior. If these benefits were widely understood, wouldn’t companies pay more than lip service to empathy and user research?

Prototype and test falls short

Alan Cooper, creator of Visual Basic and UX-guru author of “The Inmates are Running the Asylum,” decried the “Proto&Test” mindset in a Twitter thread “Prototyping and testing is not interaction design.” Cooper writes that Proto&Test makes management happy because it never rocks the boat. Although it creates small improvements, keeping the designers and their bosses hopeful and happy, it never truly supports the user—or the product—by going for the big change.

We’re still misunderstood

We’ve seen that under the banner of design thinking, companies may be skipping the empathy stage and returning to a comfortable, self-contained design process. Design thinking does bring in a valuable prototyping/testing phase, but cutting corners on user research turns back the clock and misses a chance for specific insights and innovation that can put a product over the top. And failing to conduct at least intermittent research just prolongs the mindset that we “know what our users want.”

Segregating research and design, although emphasizing visual design skills, may cause companies to pass on those cognitive-oriented designers that created “UX” in the first place. Visual design provides an important initial impression, and a number of studies have shown that people rate attractive sites higher on usability at first glance. But visuals are only one part of the UX equation. How will a user who regularly uses your product truly form her opinion? Visuals will play a part, but I think it is more likely to depend on a great workflow—the process users need to follow over and over.

So what do we need?

I’m not certain what’s wrong, but I suspect we haven’t made our case sufficiently. We all implicitly understand the value of a true UX process, but does the Director of Development or Marketing?

We may be victims of our own success. We’ve improved the state of UX drastically—examples of great design can be found on any smartphone. Improved development tools take advantage of interaction patterns that we’ve pioneered, and toolkits make digital artifacts that look great. Perhaps development leaders feel that they’ve seen enough good design that they believe they can just do it. When hit with another tight schedule, why go through a research phase for deliverables—and benefits—that can’t easily be quantified?

I wrote an article for my last company on the benefits of user research. It was hard to find case studies that offered explicit value that everyone could understand. In most of my own projects, user research underscored reasons to change the direction of a project, find the optimal task flow, and place the right information in the proper hierarchy on a screen, but I lacked a solid ROI case.

I think we need to make an effort to create studies showing the value of research that immediately resonate with stakeholders. Perhaps we need to create and publicize a regularly updated library of case studies that clearly demonstrates ROI. This would be a great project for UXPA, CHI, or IXDA, and I’d be happy to help.

I fear that if we don’t, we all may need to be visual designers who can prototype.

Go to Original Source

Mark Richman

Powered by WPeMatico

2018-03-07T03:05:15+00:00March 7th, 2018|Categories: News, Tutorials|Tags: , |
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it. Ok