Product Sense Case: Make Google Calendar Better for a User Group You Pick

You are a product manager on Google Calendar and have been asked to make it better. Decide what the improvement should achieve, choose which users you are improving it for, find what frustrates them, propose and prioritize changes, and explain how you would measure success. ```hint Follow one event end to end For the users you chose, trace a single event from the moment someone needs to schedule it until it is over, and mark each step where the calendar leaves them doing the work by hand. ``` ### Clarifying Questions - Is the focus the free consumer product, the version sold to businesses as part of Workspace, or both? - Is the aim to win people who use another calendar, to deepen use among current users, or to strengthen the paid Workspace business? - Which surfaces are in scope: web, the mobile apps, or the calendar built into Gmail and other Google apps? - Are there limits on using data from Gmail, Drive or Meet to power new calendar features? ### What a Strong Answer Covers - A stated goal for the improvement and why it matters to Google - User segments compared, with one chosen and the reason - Pain points drawn from that group's scheduling and meeting workflow, ranked by how often they happen and how much they hurt - Solutions compared on explicit criteria, including fit with existing Calendar features and the effect on invitees and people on other calendars - A primary success metric with guardrails, plus the main risks and how to handle them ### Follow-up Questions - How would you confirm your top pain point is real before building anything? - Your feature saves the organizer time but adds steps for invitees. How do you decide whether to ship it? - How would your plan change if the goal were winning people who use a competing calendar?