EY Mobility Pathway (EYMP) is an integrated solution that brings together mobility technologies and services into a single, end-to-end platform. It delivers value by reducing costs associated with employee mobility while driving automation and consistent process execution for users across the mobile talent lifecycle.
EYMP delivers immigration, cost estimation, compensation, tax assessment, case management, and data visualization functionality, and owns a modular approach so clients can use as much, or as little of it as they wish.
The project was divided into feature teams. My team was in charge of:
• Travel Pathways: Travel pathways are trip groupings by destination and business traveler. There are three types: Business travels, Assignments, and Permanent Transfers. They were previously called "Mobility Pathways", but this name was updated after Usability Testing feedbacks.
• Dashboard: KPIs and widgets associated with the main sections.
• Service Initiation: The service initiation process for Assignments introduced a new complex questionnaire layout. Regardless of this particular flow, the aim is that the questionnaire is scalable enough for future needs.
• Case Management: The case management section groups all cases regardless of their associated destination.
Each team was composed of: 1 Scrum Master + 1 Business Analyst + 1 Product Owner + 1 UX Designer + 1 Technical lead + 6 Developers. The target device is Desktop based on the fact that 80% of the time most user roles will be uploading forms and documentation. However, responsiveness was considered for being compliant with Accessibility standards (zoom-in mode), and for reviewing information (not editing).
• Working remotely with multi-located teams & learning from other cultures.
• UX Design for SAAS - BtoB
• Design Systems
• Scaled Agile Methodologies.
• Leading & People Management.
• Conducting usability testings. Analyzing and presenting results.
• DISCOVERY INTERVIEWS: EYMP groups a set of services that were previously provided by independent products. Analyzing those products was the first part of the road.
• USER PERSONAS: When the project started, we defined high-level user personas so all feature teams were aligned. However, by the time the product became more and more complex and new feature teams joined, we detected inconsistencies (names and roles) that triggered communication problems.
Therefore, after some interviews with stakeholders, with users, usability testings, and research, we were able to set up three main personas. We refer to them throughout the entire product development process. We created a summarized version in ADO (Azure DevOps) so all user stories are linked to a user persona: Business Traveler, EY User, Corporate Manager.
• CUSTOMER JOURNEY: As part of the product research process, we mapped out the users’ journey as an executive presentation for our clients. The result was extremely insightful since we could: Identify and communicate the product's value proposition, Capture our client's feedback early in the process, Identify key points in the flow to prioritize features, Define the main personas involved, and the main roles we need to create for the MVP.
• PRODUCT MAPPING: This product map's goal was defining a big picture as a reference. Even though we were not creating all the features for R1/2, it provides an overall view of EYMP's information architecture as well as the associations between entities and current vs future features.
• DESIGN THINKING SESSIONS: Wireframes, User Flows, Customer Journeys. As part of our design process, we first analyzed (1) Problem to Solve and (2) Requirements with the BA, PM, Dev Lead and any other relevant member of the team depending on the task. With this in mind, we created a few initial sketches to start finding the solution.
• HI-FI MOCKS & PROTOTYPES: Once we found a solution as a team that could solve both our users and business needs, we created a hi-fi prototype with all edge cases considered. These prototypes served the dev team to review users stories assigned to them.
USABILITY TESTING: We were able to conduct a set of Usability Testings on the Service Initiation Form. Users were internal EY Advisors using another app for several years as well as Clients who received the forms completed by EY Users and had to review the information within that app. The results were shared with the Product Team to capture outstanding improvement opportunities and define priorities.
