Built for automotive manufacturers, the Connected Vehicles platform connects over 20 million vehicles across 150 countries.

Duration 2019 - 2024

Background

Connected Vehicles is a cloud-based platform that enables automotive OEMs to manage their vehicles and services worldwide.

As a dedicated UX designer on this project, I delivered simple yet flexible UX solutions to complex challenges. I collaborated closely with Technical Product Managers, Product Owners and Development Leads to ensure the usability and user-centered quality of final deliverables.

Design Process

Product Design Goals

• The main feature modules should be independent so they can be sold separately
• The UX need to be intuitive to different roles in automotive OEMs
• Seek balance between complicated functionality and easy-to-use interaction

To better understand our customers' needs, we conducted research before every design work, and created personas which represent different roles in an automotive OEM.

We designed different main feature modules as value packs for different potential customers. Below is a journey map of the vehicle OTA Software Update module. It helps us identify the pain points and define the feature design goal.

Design screens of OTA Software Update module:

Design screens of Vehicle Service Management module:

With flexible design, the main feature modules can be sold as a bundle or individually. For example, customers can purchase the platform with Vehicle Service Management module, or the OTA Update module, or choose both of them at the same time. While some function are universal for all feature modules, like user authentication and authorization.

Challenge - Customer Engagement

During our customer engagement, we found that our sales representatives sometimes struggled to explain how our connectivity capabilities support the daily operations of automotive OEMs. To enhance customer perception, we designed a suite of demo tools, including a mobile app, a vehicle simulator, and additional resources.

The mobile demo app represents the OEM mobile app, used by the vehicle owner.

The vehicle simulator represents a physical car in the real world.

These demo tools help our OEM customers gain an intuitive understanding about what will be improved in the end-user side.

Demo Tools Design Goals

• Prioritize visualizing the demo related features
• Focus on easy-to-understand by viewer

Similar to the general product design process, we also created journey maps, wireframes and drafts for these demo tools before stepping in high-fidelity visual design.

Below is a design of remote control flow and UI feedback in the mobile demo app:

The same as all the other IoT platforms, user's commands cannot always reach their devices. It's important that we provide various feedbacks to the end-user in different scenarios.

Below is a user interaction flow design of vehicle services activation in Vehicle Simulator's head unit:

It shows the vehicle services activation flow and detailed feedback of different scenarios in a vehicle's head unit, demonstrating how the product's connectivity capability supports the vehicle user's in-car experience.

Connected Vehicles platform is designed to be a generic product. After we signed the contact with our customers, there are plenty of design needs to be updated to adapt the customer's system and environment. The product design focus switch from generic user to specific customer, and the customization work may change the existing design significantly.

Below is an example of adding OTA update package.

Left is the product design screen. Right is the same screen after we adapted the system of our customer in Europe.

In the end, the customization experience we learned from this automotive OEM will be used in our next generic product design iteration.

UX Deliver Process

This project runs under SAFe (Scaled Agile Framework). We need to deliver the committed features within each PI (Program Increment), which consists of 4 sprints.

However, UX work sometimes becomes a bottleneck during the development process, as teams wait for designs immediately after PI planning. On the other hand, it's also stressful for designers to deliver all UX deliverables within such a short timeframe. As a result, the development of some features is blocked by UX design in the early stage of each PI.

In order to minimize this impact, I started a way of working called Progressive Delivery, which breaks down the each task into different stages. This allows designers to deliver work step by step, without blocking the developers.

In the first stage, we quickly draft a user flow with key actions and data fields, and iterate with stakeholders, so that everyone has a holistic view of the main interaction and what information will be shown in each step. After aligning with the stakeholders, most developers can start their work without knowing the detailed visual style, as this does not affect the back-end architecture.

In stage 2, UX designers focus on the detailed visual style (color, typography, layout, etc.), and front-end developers can begin building the GUI once the detailed design is delivered.

In stage 3, UX designers continually monitor the implementation, and provide supplementary design support, such as strings fine-tuning, and design feedback for specific exception cases (usually come up at this stage).

For different features, each stage may take different time and effort to complete, depending on its complexity and priority. No role in the team was blocked throughout the entire PI's development.

By following this UX delivery process, we minimize the waiting time for developers, and also reduced pressure on designers during the early stage of each PI. It helped improve overall feature development efficiency, and I still apply this method today.