![]() We found that focusing the design to be a multiple card view allowed Taskers to quickly browse and pick up tasks, which was successful in them getting more work and also resulting in more completed tasks overall. After the first release, we found from talking to Taskers that it was very ineffective because Taskers were more likely to pass on a task than to commit to one as they preferred to be able to view all of the tasks before selecting ones they wanted. The first release was focused on getting Taskers to take or pass an available task. ![]() We went through 2 iterations of releases for this. We also saw this as an opportunity to not only just get tasks that were abandoned, but also allow Clients to automatically hire Taskers especially if Clients didn't care about who they hired specifically. This feature was known to be "Rescue/Optional Tasks", which were tasks that were abandoned by other Taskers. The biggest request and feature that Taskers loved about the old system was being able to browse tasks that were available. "How do I find more work?" was a common question asked by Taskers. My process is always starting with sketching to think through many different ideas to refining and prototyping based on constant cycles of critique and feedback. After all the user research, I broke down the design to the core functionality that Taskers needed and then worked to piece together everything. #Task rabbit vs taskr android#Initially, I started with using the current app on both iPhone and Android to get a sense of what the experience is like on the Tasker side and completed a few real tasks as a Tasker to truly experience the Tasker side of the system. After understanding some of the issues, I talked to customer support and Taskers to gain a deeper understanding of the issues. Mobile was the medium we focused on because Taskers were constantly completing tasks on the go. ![]() #Task rabbit vs taskr update#Taskers wanted to be able to update their skills and profile, know what tasks they were hired for, find additional work, and update their availability. After talking to Taskers, we learned that the Tasker app we shipped was painful to use. It was difficult to navigate around the app, update availability, and worst of all, knowing which tasks were required. We learned after launching the redesign in July 2014, tasks were not completed properly or on time. For TaskRabbit's entire system to function smoothly, the Tasker experience needed to be designed well. ![]() #Task rabbit vs taskr full#The teams were made up of 1 Product Manager, 3 Engineers, and 1 Designer.Įven though the Client experience was redesigned, that only completed a piece of the full experience. The old TaskRabbit model didn't support any of the functionality that Taskers wanted.ĭesign features for Taskers that will give them the proper information and context to deliver quality customer experience through better communication and work. ![]() We wanted to make sure Taskers had all the tools, information, and context they needed to complete a task successfully. Taskers wanted to be able to manage their schedule and tasks, update their skills and profile, view all their task history, and monitor their performance. Even if the Client experience was designed well, the full experience would be incomplete because the rest of the experience is dependent on the Tasker. This created an opportunity to redesign the service from the ground up. The new redesign wasn't easy, we had to tackle designing for the Tasker (Users that do tasks and earn money) after redesigning the experience for the Client (Users that hire Taskers to do tasks for them). TaskRabbit was changing its model from posting tasks and bidding to a direct hire model. TaskRabbit is a website and mobile app that allows users to outsource small jobs and tasks to people in their neighborhood. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |