Preview: Designing Aptiv's interface language for computational mathematics
State machines, code editors, and data strategies
Have you ever used a vehicle signal "driver's seat belt" as a code variable? Sounds intimidating, but for our users, it's a playground.
To comply with my non-disclosure agreement, I have omitted and obfuscated confidential information in this case study. All information in this case study is my own and does not necessarily reflect the views of Aptiv.
Sole UX/Product Designer
B2B Enterprise SaaS
Extracting the right vehicle data through the formulation of event triggers starts with a vehicle engineer.
Gathering useful, actionable, vehicle insights requires the technical expertise of vehicle analysts and engineers. To fully leverage their engineering knowledge, tools were needed to supplement the formulation of events through complex mathematical logic.
However, as vehicle systems become more complex, the product, Logic Builder no longer served users as effectively.
Co-designing with Technical Product Managers, Software Engineers, and our users brought us closer to the root cause of user needs. These needs were very technical and touched different workflows, teams, and ecosystems. Effective, altruistic solutions required understanding and delving into their technical worlds.
I lead design for the entire digital experience: from concept, user research, workflow definition, ideation, and final design execution. I made final decisions on product design priority and scope, as well as defining future phases for product experience maturity.
Next gen logic building
Give users the ability to define their strategies in collection of vehicle data
Provide tools to make complex computations possible
If we provide users the ability to define their own vehicle data strategies, they will formulate desirable, high-fidelity data, increasing their SME value to customers
Project is shipped as of December 2019 and under NDA. If you're interested to learn more, please send an email to email@example.com