For the Freelancer experience redesign, I have conducted an extensive Journey map study. You can read more about it here. I addressed freelancers' paint points and needs discovered during this study in the new design proposal.
For the Freelancer experience redesign, I have conducted an extensive Journey map study. You can read more about it here.
The current freelancer Home page needs to respond to paramount user needs - Work and Income. Over the last 8 years, it has acquired various functionality but not answer the basic questions from the user:
The main goal of Freelancers in the product is to get a job, complete it and get paid. The Dashboard need to help users to accomplish it.
The Dashboard is not a separate step of the experience. It is a "home" page and indicates user action and status. Regardless of the user's flow, the Dashboard reflects and answers the question:
If there is nothing for me as a user, you can lose my interest and engagement.
The redesign of the freelancer's workflow was a challenging task due to the involvement of multiple interested groups whose work and processes would be impacted. This was one of the main issues addressed in the stakeholders input.
It goes beyond what the interface looks towards how the process should be and how we should tackle one or another challenge to optimise the company processes overall.
The stakeholder groups were:
Interest groups often have differing opinions on how things should be done. Trying to find common ground during a discussion can be a lengthy process and may not necessarily lead to actionable outcomes.
To move the processes constructively, I facilitated multiple workshops where various groups were involved, put in a position of working together and not confrontation.
I began to map the flow and values for each design view based on accumulated knowledge
Recognizing the high demand for mobile responsiveness needing more user experience, I created a navigation tree map and developed ideas for mobile interactions.
I had two main concepts in mind - Calendar and Schedule. Knowing that Freelancer often struggles with time management and multi-tasking, I did the first moderated testing with three Freelancers.
I decided to drop Calendar's approach after interviewing and reviewing prototypes for the following reasons:
Recognizing the high demand for mobile responsiveness needing more user experience, I created a navigation tree map and developed ideas for mobile interactions.
Takeaways from the calendar concept that I took to the future proposals
For the next round, we did unmoderated testing with the cart sorting exercise on the Schedule concept. I paired with usability researcher Jillian Heller for this study.
The current Dashboard has a lot of noise and non-essential information. It is an issue since it is the first place a freelancer sees once on the platform and their most frequented screen. (9k+ users per month)
By making the Dashboard a leaner screen and only presenting the essential information and action items for the Freelancer after log-in in, testers will have a more valuable and efficient experience throughout their time on the platform.
To validate if the redesigned Freelancer Dashboard is successful as Testers' new main entry point.
Learning from the usability findings, I prepared the final Work (Dashboard) proposal.
I presented the design to the engineering team to gather technical questions and feedback. Team and engineering input is always to the point and essential for successful delivery.
I paired with the usability researcher Helen Hendrikson for moderated testing. The goal was to validate the prototypes to ensure we deliver the maximum value to freelancers.
The Sample: a total of 10 users (5 new and 5 old users)
The study helped to capture the missing data from the invitation and task design, such as a Run start day. It showed the difference in perception of the Testing run status vs Task statuses. It challenged the relevance of some data points on the right-side panel sections. Helped to identify the missing data from the task table and detect potential overload of user attention in the onboarding steps.
After revising the design and reviewing by engineering team I prepared design for engineering handoff of the first iteration. The first iteration (first product release) is the version of the design with scoped data and functionality.
The prototype for the first production release you can find bellow: