Launch Decision and Design for a Google Workspace Task-Completion Product

You are a product manager at Google. Google Workspace, the suite once branded G Suite (Gmail, Calendar, Docs, Sheets, Drive, Meet, Chat and related apps), is where many people already receive and carry out their work. Would you launch a product whose purpose is to raise the rate at which users complete their tasks? If you would, take the interviewer through how you would design it, the trade-offs you would make along the way, and the metrics that would tell you whether the launch succeeded. ```hint Pin down what a task is "Task completion rate" means little until you decide what counts as a task and where those tasks live in Workspace today. Settle that, and look at what Workspace already offers for tasks, before arguing that a new product is needed. ``` ### Clarifying Questions - What counts as a task here: only items users write into a to-do list, or also commitments implied elsewhere in Workspace, such as emails waiting on a reply, comments assigned to someone in a Doc, or action items agreed in a Meet call? - Should the product serve paying Workspace business customers, people on free personal Google accounts, or both? Admin controls and data-handling expectations differ a lot between them. - Is task completion rate already measured somewhere, and if so, does it count tasks finished by their due date or finished at any time? - Does the answer have to be a new standalone product, or may it be a capability built into the existing Workspace apps? ### What a Strong Answer Covers - A precise definition of a task and of the completion rate, including how to stop the rate from improving simply because fewer or easier tasks get recorded. - An explicit launch decision that accounts for the task features Workspace already has and explains why users still drop commitments. - A chosen user segment whose pain points map to solutions that use Workspace's view across email, calendar, documents and chat, prioritized into a focused first version. - The main trade-offs, such as standalone versus embedded, automatic task detection versus manual capture, timely reminders versus notification overload, and content privacy with admin control. - A success metric with guardrails and a plan for testing the launch. ### Follow-up Questions - If the product suggests tasks it finds in emails and meeting notes, how would you deal with suggestions that are wrong, and how would you measure that error rate? - Many teams already track work in dedicated project-management tools. Would version one integrate with them, compete with them, or leave them alone? - After launch the completion rate rises, but the number of tasks captured per user falls. How do you read that result?