Can’t we all just get along?
UX design versus everything else
“Delight vs. MVP?”
This was the title of a group discussion I came across recently on LinkedIn. Upon seeing those two letters — ‘v’ and ‘s’ — I was simultaneously intrigued and disturbed. I had just come to realize the severity of a destructive epidemic in the UX community: the idea of “Us” vs. “them” and “this” vs. “that.”
As a UX designer, I’ve seen these two letters used quite often…
— UX vs. UI
— Omnigraffle vs. In-Browser Prototypes
— Photoshop vs. [ NOT Photoshop ]
— Clients vs. Designers
Get Chris Alvarez’s stories in your inbox
Join Medium for free to get updates from this writer.
What’s crazy to me is that UX designers communicate ideas of hierarchy, priority and cadence using shades of grey but speak in terms that are so distinctly black and white. Is it really about A vs. B? Or is it more about A and B and how much of each make sense to the right person.
We’re supposed to do what?
Like it or not, the role of a UX designer — UI designer, Researcher, Developer, generalist — also includes the responsibility of negotiating, coaching, mediating and listening. It would be entirely appropriate to say that UX designers sit squarely BETWEEN two sides but that’s exactly what we’re meant to do.
For every project I’ve been on as a UX practitioner, I’ve had to place myself in the middle. I’ve been between businesses and users, between teams, between people, and have even been in the middle of arguments about which [software] tool is better than the other. But that’s one thing I really love about what I do; it’s not just about right or wrong. It’s about listening and helping both sides come to an agreement. There are times where the two sides are aligned and my job is easy. Other times though, priorities are misaligned and things get pretty rough. Bet really, that’s where the fun begins.
Back to that forum post…
“Delight vs. MVP” is clearly the wrong way to think about the needs of a project. For this specific example I think there are really two questions at play: “how do I convince a client that the experience should be delightful?” and “how do I get the development of ‘delightful’ interactions prioritized while still considering an MVP?” The answer to these questions is equal parts communication and research.
By communicating with (not to) the client about what to expect in the project, they should have a good sense for the time it takes to inject those delightful bits of the experience. If there is one story that encompasses the “delightful” parts of the experience, then there is no way for the client to know how to prioritize this over anything else. If there are smaller stories that are associated with specific user goals, then it’s easier from the client’s perspective to give the go-ahead. Enhanced micro-copy, for example, could add bits of delight that are tied to the goal of getting through a sign-up process with little pain. This example wouldn’t cost a lot of development time.
If the “delight” comes from fancy animations, or a more frivolous interaction, then perhaps the effort required really doesn’t make sense. The key though is to just ASK.
Communication = getting rid of “vs”
Design is all about communication. The end result is a visual communication TO other people, but in terms of process, it’s communication WITH other people. For a design(er) to be successful, there must be a willingness to simultaneously compromise and advocate. It’s tough, and awkward but if there is research to back up the recommended solution, then the designer is no longer a solo voice.
So please stop thinking about how your ideas should be prioritized over theirs. Instead, think about how to communicate about all ideas; set the priority together and communicate using the language of insights instead of intuition. Usually the only person who ends up getting hurt when one side “wins” is the customer.









