This contradiction is at the root of the mid-2010s articulation of UX, which gave rise to the UX/UI designer and the UX Unicorn. Asking the same individual to personify both roles on the fly is inefficient and leads to poor process decisions over the life cycle of a design.
UX is different everywhere, but the Silicon Valley lives in the future
Ian Armstrong

Absolutely spot-on insight. It describes exactly what myself and many of my colleagues face on a daily basis. And I work in one of those supposedly “futuristic” cities.

The root of the problem goes beyond cost, though. Older SW companies are still struggling to recognize that there are indeed two sides to UX. They perceive all designers as UI/visual. “UX/UCD” is just some magic fairy dust sprinkled here and there by those who happen to be endowed with it.

When faced with the prospect of actually implementing a true UX process (generative research and validation), they quail. “Our sales people drive product definition because they work closely with clients and prospects.” “We have to deliver on time; we simply can’t fit that much upfront work into the timeline.” “We can’t get access to end users; they’re too busy.” “We already have all that domain knowledge in-house; why do we need to ask the same questions again?”

It’s been a hard row to hoe convincing management otherwise. Tips, anybody?

Like what you read? Give Tristan Naramore a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.