TaskRabbit: Diagnose and Fix the Biggest Pain Points After a Client Books a Tasker

You are a product manager at TaskRabbit, the marketplace where clients hire independent Taskers for jobs such as furniture assembly, TV mounting, moving help and small home repairs. Focus on what happens after a client has booked a Tasker. Explain how you would find the weakest points of that post-booking experience, which problems you would fix first and why, what you would build, and how you would measure whether it worked. ```hint Find before you fix List the stages between a confirmed booking and a finished, paid and reviewed task, then decide which of TaskRabbit's own signals would show where each stage breaks down and how much each breakdown costs in lost repeat bookings. ``` ### Clarifying Questions - Is the focus the client's experience after booking, the Tasker's, or both sides of the marketplace? - Where does "post-booking" end: when the work is finished, when payment clears, or after the review and any rebooking? - Which task categories and markets matter most, for example short assembly jobs versus multi-hour moving help? - What data can I use: support tickets, cancellation records, ratings and review text, chat activity, invoices and the hours Taskers submit? ### What a Strong Answer Covers - A stage-by-stage map of the post-booking journey for clients and Taskers, from confirmation through the work itself to billing, review and rebooking - A concrete method for ranking pain points with TaskRabbit's own signals (support contacts, cancellations, disputes, ratings, repeat bookings) by how often they occur and how much damage they do - A focused choice of the two or three worst problems, with solutions that account for Tasker incentives as well as client needs - Success metrics tied to tasks completed as promised and to repeat bookings, with guardrails on Tasker supply and earnings - Risks such as extra work for Taskers and test results distorted by the two sides of the marketplace sharing one pool of supply ### Follow-up Questions - Your fix for last-minute Tasker cancellations lowers them, but Taskers in the test city start accepting fewer bookings. What do you do? - How would you test a change aimed at Tasker reliability when clients and Taskers in the same city all draw on one pool of supply? - If the data shows the worst problems actually begin before booking, for example vague task descriptions, would you still limit your scope to post-booking?