Mis-selling of design as UX is the problem I keep meeting people who say they do UX but don’t, they are designers and there is nothing wrong with taking a design approach to digital, process or product development projects. The problem comes in the mis-selling of design as UX, as the results are dramatically different.
How do you design the experience? You can design a framework or architecture but the experience is in someone’s mind and in their emotions. UX research or UX analysis all make lots of sense but UX design does not, UX is in the emotions of the user not in a digital product or system. The
This is just a quick post showing the basic level differences between User Experience (UX) Roles and Information Architect (IA) Roles. I’m working on a full model post as well, but that is still being written. User Experience (UX) Roles. User Experience (UX) Roles Diagram User Experience Architect (UX Architect) Gathers requirements, defines the system
There seems to be a huge level of confusion around user experience (UX), but one of the key things is that the user interface is not the user experience. Simple digital systems are constructed with several interlinked components; User Interface – what the user sees Interface Logic – what the user can do Logical connections