web analytics

You’re not a user experience designer if…

The UX field is booming. It seems like the number of user experience practitioners has doubled in the last year — from newbies who’ve just entered the workforce, to mid-career changes, to folks who’ve been doing this all along but finally found out what to call themselves.

It’s incredibly reassuring to finally see a long overdue interest in user experience practice; after all, that’s what many of us have spent our careers fighting for. I started this blog to give greater insight into how we think, how we work, and how we benefit customers and companies alike. I consider myself lucky to be among many professionals who speak at conferences around the world in an effort to bring UX into the mainstream. And it’s working!

There’s just one problem: not everyone calling themselves a user experience designer is actually a user experience designer. Unfortunately the designation isn’t as clear cut as a doctor or a lawyer. Most professions are certified and regulated, so you don’t see impostor behavior often — and when you do, it’s typically in the form of a news article about someone going to jail for fraud. Perhaps more analogously, even those in non-regulated occupations like writers and programmers would have a hard time passing themselves off as such without actually writing or actually programming.

But how does a user experience designer demonstrate their user experience designing? I’m not talking about quality or level of expertise here; I’m merely referring to the veracity, the legitimacy of the title itself.

Regardless of what they choose to call themselves, how can you identify someone who isn’t actually practicing UX at all, who’s only hitching their wagon to a rising star?

You’re not a user experience designer if…

  1. You don’t talk to users. If you design entirely based on intuition without ever gathering intel from a single human being who might at some point in their life come into contact with your business, I’m sorry, but you just aren’t a user experience designer.
  2. You can’t identify your target audience. If asked who your site is intended for and you say anyone and everyone, you are wrong. If a product is designed for everyone, it works for no one. A user experience designer would know that and narrow the target.
  3. You don’t define the problem before trying to solve it. If your boss tells you what to build and you don’t start the project by first determining why — the specific pain point that people are currently experiencing that your product aims to eliminate — you’re a lackey, not a user advocate. Nine times out of ten, understanding the problem changes the solution dramatically.
  4. You can’t articulate your users’ goals. Maybe you kinda get the problem people are having, but unless you can communicate (in your own words) the objectives your target users are trying to accomplish both in their lives and their work, how can you craft a solution that will truly support their efforts?
  5. You design in a vacuum. No user experience designer works alone, so if you are, you aren’t one. Even a UX team of one relies on stakeholders, visual designers, developers, marketers, the guy in the next cubicle , etc. for feedback. A user experience designer knows the product isn’t meant for them, and always tests its effectiveness with other people.
  6. You make design decisions based on your personal preferences. If your coworker or client asks you, “Why did you choose to use checkboxes instead of radio buttons?” and your answer is, “Because I’ve always liked checkboxes better,” please dear God don’t call yourself a user experience designer.
  7. You don’t consider the business objectives. Surprise! If all you want to do is protect the consumer, join the ACLU. A true user experience designer understands their company’s goals just as deeply as they understand their constituents. That allows you to determine which of the constituency’s needs should be addressed by the product, and make a case to the powers that be how doing so will positively impact the business in the long run.
  8. You don’t use UX methods. User interviews, usability tests, personas, scenarios, card sorts, affinity diagrams, concept models, sketches, flow diagrams, sitemaps, wireframes, prototypes, web analytics, A/B tests, the list goes on and on. If you don’t have a systematic approach for articulating what you learn about your users to others on your team, or even a loose process to iterate on your ideas for what they’ll experience, you might be trying but you aren’t a user experience designer.
  9. You don’t design for conditions and edge cases. If you map out best-case scenarios and how-we-want-it user flows, but don’t take the time to craft branches and escape hatches for alternative needs, user errors, system errors and general curiosity, you don’t understand people very well and you’re not a user experience designer.
  10. You only think about the interface. If you’re focused exclusively on what the user sees and does on your website/mobile app/desktop app/kiosk/whatever, but never plan for how they’ll get there, what they’ll do when they leave, how they’ll come back, and most of all, how they’ll feel about it a week later, you’re a user interface designer, not a user experience designer. There’s a big difference.

I might sound like I’m contradicting myself

The above slide is from my presentation DIY UX: Give Your Users an Upgrade Without Calling in a Pro. So yes, I am partially to blame for this trend. But I didn’t really mean for people to start putting the title on their business cards and anointing themselves User Experience Designers without actually putting in the hard work.

The point of that slide in particular is to get people to realize that no matter what their role is, if they touch the outcome of the product in any way, shape, or form (as a designer, developer, copywriter, business analyst or marketer), they are ultimately affecting the user’s experience with the product, and as such, must take responsibility for doing right by them. This means learning who they are, listening to their needs, understanding their behaviors, and getting their feedback each step of the way. Otherwise you have no right to call yourself, or let your boss call you, what you’re not.

If you have the title of User Experience Designer and you want to do these things but aren’t being allowed to, don’t stand for it. Send the culprit this post if you’re feeling ballsy. Or let me know how I can help, either in the comments or via email. It’s one thing to claim to be something that you’re not just to be in vogue and make yourself more appealing to prospective employers; it’s another thing altogether to try doing the job and having roadblocks put in your way. What user experience designers do is honorable, compassionate, and valuable to businesses’ bottom line. When it’s actually practiced.

Related Posts:

Email Newsletter

Did you enjoy this blog post?
Get more like it delivered straight to your inbox.

  • Pingback: UX Flavours | +++

  • Pingback: How to Conduct a Usability Study: A Complete Recipe & Checklist taigeair

  • Pingback: Stuck in the Details? Mind Map User Tasks (UXBooth)

  • Pingback: Removing User from User Experience?! | Timothy Whalin

  • Pingback: BUX Podcast 91: UX Business Cards: What Does Putting UX In Your Job Title Mean? | A Better User Experience

  • Pingback: Articulating User Experience Design | Tangible UX

  • Pingback: Notification to myself about pitfall on UX pathway | Daily Design Pieces

  • Pingback: Confluence: Development

  • Franka Baly

    I have been in this industry for over 20 years and when I started we were not called UX Designers, we were called Human Factors Engineers. My point is the field is evolving… what we call ourselves, what we do, how we do our jobs etc. I think a lot of terrific designers are being asked to do a lot of UI work that takes them into the domain of UX quite often in today’s business environment. They are talking to customers and getting feedback to iterate on design and have to take into consideration business objectives as well. All this without being trained on a lot of the methodology of a UX designer. They are being creative in eliciting feedback and using cart sorts and A/B testing without even knowing that they are employing UX methods. I think that is very cool!! I wasn’t classically trained in HCI (Human-Computer Interaction), there was no such thing as a UX degree when I was in college, but I was trained and mentored by several PhDs that were and learned all of the methodology of doing HF/UX in a classic usability lab using Datalogger software, Pathfinder analysis and running data analysis using SAS to calculate t-tests, ANOVAs, and standard deviation. In my current position, I have had to throw a lot of that traditional methodology and assessment out the window because a lot of it doesn’t work in our lean and agile world where I need feedback and information fast so my team of developers can implement the changes on my mock-ups. They could care less what the standard deviation was. We are all seeking to arrive at great solutions for our customers and companies employing whatever methods can be done in the time the business gives us, even if it isn’t always pretty. I say that what you call yourself doesn’t matter, what does is that you have a commitment to creating a product (whether hardware or software) that is takes into consideration how your end-user will interact with it. I am happy to be a part of this amazing community!

  • Pingback: UX Flavours | Blog

  • Pingback: Actionable stereotype | intuition

  • anber

    I understand why UX is becoming such a huge “thing”. I “get” it, but just because there is a Santa, doesn’t mean I believe in him.

    My problem with bad UX designers is this: Bad UX designers breed more UX designers.

    I agree with most of the points mentioned here because very few UX designers take those points into consideration.

    I’m a programmer and everyday I deal with so called “UX designers”. It’s the most frustrating part of my job when “bad” UX designers tell me how to implement their “vision”! Everyone wants to be a rockstar and are constantly trying to reinvent the wheel. They have no idea why things have evolve the way it has. They have no idea what lessons have been learned and why things are “boring”. These people given “authority” over critical factors that span across various disciplines.

    I’ve been developing software for over 15 years and I have a fairly good idea why certain ideas would work or fail. I’m not UX person and would never call myself that but it’s really amusing when someone with less experience comes and tell me their “vision” and how I should do my job.

    I have many developer friends who went over to the UX profession only because they could no longer deal with the pain of following the convoluted schemes that so-called UX designers come up with. It’s easy; today you’re struggling to implement some convoluted idea, tomorrow you are a UX designer and other people are left
    dealing with the crap.

    The real problem with UX designers are that there is little accountability for the decisions they make. That is what sets them apart from other professions.

    To make my point: Our client insisted on a backup feature for their software. That’s a very good idea and we implemented a backup and restore feature. Our UX designer insisted that I remove the “restore” button because that would clutter the interface and confuse the user. This particular UX designer left the company and the developers were held accountable for the bad design when the client realized 3 months after launch of their software couldn’t restore backups. Soon afterwards, one of our team members joined the UX team :)

  • cj

    I wish I could take your points, and subject them to a “You’re not a ___blank if you ___blank” treatment all around – I know many people who think they can do the UX (or any other type of designing) without taking into account the reasons why you design the way you design and do what you do! It’s a good article, not just for UX but for anyone that wants to say they are a graphic designer professional – unless you are considering your clients, their customers (or users) and getting input, feedback, and resources, stop and take a good look.

    :D I’m so adding this to my favourites and using it as a benchmark for myself and any other UX designer brought on board!

    • http://www.whitneyhess.com/blog Whitney Hess

      That’s so cool to hear, CJ. And you’re right, this does have applicability to almost any profession I suppose. Being a practitioner never means having all the answers or being a magician (unless you are a magician). We all have to improve our collaboration and communication, mindfulness and compassion.

  • Pingback: UI != UX | Matt Langan

  • Bob Bodine

    Evaluated by results but identified by its processes.