I arrived to help with the increasing UX workload for the inspire/research team, in particular for the search functionality. Working with UX researchers, Product Managers, Content Strategists and the Technical Product team.
There was also opportunities to improve the UX ways of working within the product team where we got to further implement the Design Thinking process.
This case study was the result of previous lab testing findings, where the refinement of options on destination landing pages needed to be optimised to better suit where the user was in their journey.
Requirements gathering
• Important findings from Expedia group wide user research reports.
• Taking into consideration the company product principles.
• Previous discoveries from past user testing sessions in regards to refining options from landing pages.
• Desktop research from carefully selected resources to find out good practices in ‘sub-category’ UI across product and e-commerce.
• Looking into existing assets within the design system to reuse.
Design strategy
• Quick ideation sketches which transferred onto more detailed Sketch iterations and user flows.
• Content hierarchy and image selection was defined in parallel to designs.
• Test and learn strategy helped identify the more successful interactions and to move onto one round of iteration.
• All designs were soon transferred onto Figma.
• Designs converted into Zeplin links with any existing assets renamed to resemble its real life code.
• Behaviour, assets and content documentation added onto Confluence page.
• Documentation and links presented to UX engineers for prototype build and development team soon after.
Additional project: Integrating new compulsory travel tax into search functionality
• Researched into most optimal UI to help calculate a more accurate price on display.
• UX collaboration with wider teams within product helped with applying the design across the whole user journey.
• Extra communication with Design Systems team and native app engineers resulted in specific UI solutions for native app compared to web.
Back to Top