Focus of the Project
The priority of the project was to enhancing the existing experience of the application, which is why it was extremely important to understand our end users. We started our journey with Research that included 1:1 user testing and 1:1 user interviewing from 3 individual ordering teams. On the basis of the user feedbacks the design tasks got prioritized by our product team. The screenshot below is a small snapshot of what we found from the user testing.
I led this 9 months remote project from research through launch and collaborated closely with 2 product owners and 3 engineers.
Findings from User Testing
User Research
The goal of the research is to understand the current ordering process of the end users for identifying the problem areas to better bridge the gaps between manual spreadsheets and order planning. We wanted to enhance the current experience of the app to match up to their daily activities and lifestyle. We conducted 10 one on one interviews with end users who create and manage orders in DOT with these primary points:
Their job role
How they start and end their day
Their goals and activities
Busy periods
Systems they use
Pain points
Motivation
Wishlist
Findings from User Research
We could identify 3 types of persona : Content planners - who is responsible for scheduling when and where to launch the title; Global Content operation Manager - who are responsible for managing created orders as well as remediating issues related to the orders and Global Content Associate(s) who are responsible for doing the research of the assets and creating orders.
Persona 1
Persona 2
Persona 3
Existing Journey Map of Order creation process for 3 individual teams displayed a picture of Issue Remediation being the trickiest step, with heavy manual coordination across teams amid tight and numerous delivery timelines.
Few example of the requests made by users on the existing experience
The experience below displays improving the existing notification experience of the application, with enough information about individual components, with the total number of orders successfully or failed to be placed.
Being able to provide title-specific dates for selected components while creating orders for a title in the chosen platform.
Providing prior order information on the right co-pilot for individual components, with the capability of navigating to the legacy application when needed.
Users are being provided with additional context about languages and components that were ordered for a title in a platform
