User experience and user requirements are two independent approaches. User requirements address the customer's requirements and expectations for the solution, whereas user experience encompasses all aspects of how the user interacts with and uses the software. The software product should be easy to use and has usable features. Moreover, the additional value for the software is if the product has an attractive design or working environment that is in line with user behaviors, it can occur if integrate software requirements and user experience. Integration escalates developer productivity by focusing on features that meet the user's needs and expectations. That integration improves efficiency in software development by identifying and addressing problems that may arise during the development process, saving developer time and effort in developing software. The usage context of integration of user experience and user requirements in UX Journey contributes increase developer productivity and self-efficacy in developing software by focusing development on features that match the user needs, as well as increasing efficiency in overcoming problems that arise during the development process. UX Journey makes developers feel more confident in their ability to develop quality software.

This study reports on empirical findings of participatory design workshops for the development of a supportive user experience design system in the automotive. Identifying and addressing this area with traditional research methods is problematic due to the different UX design perspectives that might be conflicting and the related automotive domain limitations. To help resolve this problem, we conducted research with 12 User Experience (UX) designers through individual participatory prototyping activities to gain insights on their explicit, observable, tacit and latent needs. These activities allowed us to explore their motivation to use different technologies; the system's architecture; detailed features of interactivity and describe user needs including Efficiency, Effectiveness, Engagement, Naturalness, Ease of Use, Information retrieval, Self-Image awareness, Politeness, and Flexibility. Our analysis led us to design implications that translate participants' needs into UX design goals, informing practitioners on how to develop relevant systems further.

As we approach the 135th anniversary of the automobile, two industry trends, automation and digitalization, are rapidly revolutionizing the thus far, relatively unchanged automotive user experience. This paper describes the development of the Valeo MyMobius user interface concept. The goal of this project was to explore how to achieve an intuitive driving experience as the automotive industry undergoes transition from primarily analog to primarily digital interfaces and from physical buttons to multimodal interactions. To achieve the perception of intuitiveness, designers must understand their users, find and reduce physical and cognitive friction points, and bridge knowledge gaps with interface designs that facilitate discovery and learnability. The Valeo MyMobius concept featured steering wheel touch displays that supported quick, frequent menu selections using swiping gestures (common in smartphone interactions) and reinforcing icons (to facilitate learnability). Learning algorithms personalized the experience by tailoring suggestions, while more complex interactions were handled with a conversational voice assistant, which also served as a driving copilot, capable of contextually suggesting when Advanced Driving Assistance System (ADAS) features such as ACC could be utilized. The visual design aesthetic embodied Kenya Hara’s design philosophy of “Emptiness,” reducing visual clutter and creating spaces that are ready to receive inspiration and information. Altogether, the Valeo MyMobius concept demonstrated an attainable future where the perception of intuitiveness can be achieved with today’s technologies.