EY
EY
Enterprise UX
AI Enabled Technology Platform
UX/UI Design Lead
EY Leadership believed Artificial Intelligence (AI) has the potential to make a huge difference to the EY and its clients. According to Nigel Duffy, the EY Global AI Leader, 80% of EY’s business involves the use of unstructured data. Improving this figure by 5% would have a $1 Billion impact on the bottom line.
I worked with the EY Germany team who was responsible for spearheading the creation of EY FlexAI, a AI-enabled technology platform that centered around tackling the following challenges:
The initial scope of the FlexAI Platform focused supporting the following products:
During the analysis phase, I developed current-state swimlane diagrams for each product to understand of the current user flows for the different products in scope for the the FlexAI platform. I utilized these swimlane diagram to identify follow-up questions, process pain points, key assumptions, and requirements across each product.
Based on the swimlane findings, I developed a streamlined-common set of User Flows across the different product solutions. The User Flows focused on fulfilling the user’s needs as they interacted with the platform. The User Flows served as the foundation of the design of the wireframes and screens.
For the design phase we initially developed some quick prototypes for Tax Return, Smart Contracts and Hotspot Analysis products utilizing Sketch and Invision. These prototypes allowed us to determine a common set of user patterns and interactions that could be used across the platform. These design components became the foundation for the “FlexAI” component library.
The initial release of the platform focused the Tax Return product. We further refined the FlexAI pattern library by building out the detailed design for the Mantelbogen and Anlage N sections of the German Tax Return.
EY’s current Tax Return solution (DateV) captures overs captured over 900 data elements. It would be very large undertaking for the UX team to design out the needed screens. In order to streamline the design effort, I created a “Data Configuration file” where a business analyst could map the remaining portions of the Tax Return to the approbate component within the pattern library. I worked with the Development to refine the Data configuration file, so they could use the file with the pattern library to build out the system.
