Welcome to my rant/essay/discussion about the state of the art in the UX world.
First, you’ve likely noticed the title of this article. It reads “UXD” (short for User Experience Design), not just UX. This is where my rant begins: the inaccuracy of terms, a prevailing sense of laziness, and a pervasive “whatever” attitude in everything related to the UX field.
Let’s start with term accuracy. I understand that using ‘UX’ isn’t incorrect per se; I’m not inflexible. And it’s certainly not as misused as the cringe-worthy ‘UI/UX’ term. However, for the sake of clarity in this article, precise term usage is essential.
Why do I prefer ‘UXD’ over ‘UX’?
Remember: We cannot create a user experience. Different users will have different experiences, and while we can measure those experiences, we cannot generate them—unless, perhaps, we possess divine superpowers.
What we can do is design with the intent of guiding users to experience something the way we intend. This is why we talk about UXD or User Experience Design. We can craft experiences that encompass various elements, be they analog, digital, virtual, or physical.
And here, I’ll add some salt to the wound: the current state of UXD seems to be, at best, narrowly confined to Human-Computer Interaction (HCI). More often than not, it’s reduced to just app or web design. Even worse, many designers truly believe they’re doing UI design (or UID, as we’re discussing it) and can’t grasp why they aren’t designing a user interface when they are, in fact, crafting a web application (news flash: they are not the same!)
I see many newcomers to the field who don’t even understand what a User Interface really is, who are unfamiliar with HCI, or who misuse the dreadful ‘UI/UX’ term. But here is the thing: it’s not their fault. Most “UX courses” skim over these details or worse, they perpetuate these misunderstandings, with many even including the ‘UI/UX’ misnomer in their titles. This sets a shaky foundation for what comes next. I mean… if you don’t even know the basic terminology…
But let’s leave it at that, as this portion of my rant about UX terminology concludes here. What’s important is that we understand why I use ‘UXD’ rather than ‘UX’.
So… why UXD isn’t important?
As the article title says, I think nowadays UXD isn’t important. But let me be clear: “do I think UXD is important?” is not the same than “do I think UXD SHOULD BE IMPORTANT?”. The answer to the first question is NO. The answer to the second question is “YES PLEASE!!!”.
And why do I say this?
Well, let’s make a brief recap. UX (this time as a whole discipline) went through a series of transformations through the years. From its humble beginnings almost a century ago, to a more standardized corpus of disciplines, to a UX boom that started around 2010, got really strong right before the COVID-19 pandemic, and then started declining at a slow but constant rate.
When I say declining, I mean a twofold scenario: on the one hand, there’s an obvious decline in quality, which can be explained by the reasons I mentioned in the previous section. On the other hand, big companies with huge UX departments are clearly ignoring UX principles. And I doubt they don´t know what they´re doing. They lead (and always led) the state-of-the-art when it comes to the UX field.
And I’m not talking about “arguable” things. I’m talking about basic principles. Almost as if they never existed. Mega companies using tables for content display? Basic accessibility issues almost everywhere? Complex (almost impossible) user flows there’s no way they have been ever tested and passed such tests? Dark patterns becoming the norm and “deal with it”?
Possible reasons are many. I really don’t know them. Furthermore, I assume each case is different, so a generalization is moot. And like I said, these companies have some of the brightest UX minds in the world, so I highly doubt they don’t know what’s happening. I had the honor to work with several of the companies that “forgot” UX principles and I can tell they really know their business.
And maybe the word “business” is key. I have observed that in many cases UX is subordinated to branding, therefore there’s a chance marketing teams are overtaking UXD roles, or at least ignoring UXD advice. I’m not saying this will always be the case, but it clearly explains some cases.
Another option is similar to teh above, although this time the ones bending UX designers’ arms are development teams. This is probably the case in as many cases as the paragraph before. If you want an example of development teams clearly overtaking UXD roles, then Google is the most clear example. Whoever uses Google Cloud APIs knows it’s complete madness and probably the less intuitive tool ever made. However, we can blame it to its own inherent complexity and maybe there was no better way to do it. But now that Google launched Google Analytics 4 (GA4 for short), it’s more than evident they didn’t test it with users at all. There’s no possible way GA4 passed any test when compared to Universal Analytics (UA), the previous version of Google Analytics. GA4 has a lot less features than UA, yet it is incredibly complicated for experienced users, let alone novices.
And there’s an objective way to prove it: in order to use either Google Cloud or GA4, you need to search how to do it… on Google! Google documentation on their own platforms is complicated, or incomplete or directly non-existent.
I’ll provide you a simple example you can test by yourself. Go to Google Cloud, sign up if you don’t have an account and get a SMTP to send mails. Be warned: this is probably the most menial task on Google APIs platform, I didn’t choose it because it’s difficult, I chose it because it should be extremely easy! If you have any doubt on how should it work, this is the user journey to follow (learn how to get to this in the article Intentionality and User Intent in User Experience):
Simple, isn’t it?
Now try to get an SMTP API on Google Cloud. There’s a catch: you can’t get help on Google Search. You can use the documentation if you want, just no tutorials from third parties. Then let me know how it went 😉
User Experience Design going bananas
If you followed my instructions and tried to get a simple API info from Google, you already know what kind of things are we dealing with. We can give them a pass because all other APIs are more complex and sophisticated, so maybe they went with a “let’s make everythign equal”. But… what about accessibility? Did everybody forget about basic accessibility principles? They’re not related to complex user behaviors or anything like that. Yet accessibility (while mandatory by law in most countries) is blatantly overlooked.
Let’s see an example that borderlines the dark pattern side:
Here WeTransfer has a barely legible text over some kind of “veil” or scrim that allows users to see the form they always used, just not before users accept cookies. The CTA is aptly placed next to the semi-visible button, which is a very good idea and a proper visual design principle and UI pattern. Then a “ghost button” with low visibility to Manage Preferences and then a “No, thanks” link with similar visibility than the “ghost button”.
Now, on top of the poor accessibility, there’s something like a dark pattern: if you click the “No thanks” link, you would expect that you simply don’t accept cookies. However, that’s not the case. You’re taken to a web page where you’ll see a button to accept Terms and Conditions in order to use the service. There’s nothing wrong with this, it’s a common practice and I’d do the same.
But the copy that took us to this page wasn’t about accepting Terms and Conditions , but to reject cookies. So I took a look… and voila, cookies were “accepted” by magic.
While I frankly don’t think this is a big deal, is there a need to fool users this way? Why not simply have the “I accept” CTA button and the “Manage Cookies” button like most websites or apps do?
Yes I know accessibility. But I don’t care.
Another example of “I don’t give a pickle about UX principles” comes from Apple. If you go to Apple’s homepage, you’ll find a nicely designed web page with no errors and fully accessible. Congrats Apple, you did it great, A+++!
Then we visit teh MacBook Pro page and it seems teh UX designers for that page “think different” (pun absolutely intended!). It has more errors than content!
And not only we have 43 accessibility errors and 202 alerts, of which around 50 are errors as well on close inspection (really, Apple?). Take a look at those 195 structural elements.
Just in case you don’t understand what this means: it’s not wrong. But it’s annoying as hell, almost everything is a title or a list. Try visiting the page with a screen reader and you’ll see what I mean.
Now, the question is: how did we go from 0 errors and great content organization to some kind of accessibility nightmare? Which leads us to the next question: do you REALLY think a UX designer did this page? This was obviously designed by UI designers, but it’s an archetypical example of a page built by developers.
We can improve your business!
Let us help you with the best solutions for your business.
It only takes one step, you're one click away from getting guaranteed results!I want to improve my business NOW!