I attribute the titles being a mess because of the 'newness' of the web/tech era and the specific design challenges. There is a design pyramid which unfortunat

I attribute the titles being a mess because of the 'newness' of the web/tech era and the specific design challenges. There is a design pyramid which unfortunately build on top of each other for the majority of business use cases: Graphic Designer -> UI Designer -> UX Designer -> Product Design -> Service Design These are the levels of the pyramid at which the design process revolves around, depending on the need, for most products or services: Visuals -> Web -> Experience -> Product -> Service The narrative of it closely mirrors the history of many orgs: Visuals: Hey our website looks like a database written by engineers, maybe we can make it pretty? UI -> hey, we really need it to look like it belongs on the web, not just a RISD grad's art project, let's get someone who understands web design UX -> okay, now our site looks like every other site. But no one uses it because it's still just a database with lipstick. Let's get some experience designers in here to make it better. Product -> Okay, now our site has some nice experiences... but they are all disjointed and random and don't account for business needs... Let's get some product designers in here. Service -> Okay, our product now is pretty cohesive and quite good... but there's a whole realm of things we have to do outside our product (Customer Service, service processes) that suck and are bringing the user experience down as a whole. Let's get some service designers in here... In my opinion, this is the way most businesses think about design.