Success Metrics for a Calendar App: North Star, Drivers and Guardrails

You own a calendar app as its product manager. How would you decide which metrics show whether the product is succeeding? ```hint Separate the outcome from the steps Before listing counts, decide what outcome for the user shows that the calendar did its job, and which user actions are only steps on the way to that outcome. ``` ### Clarifying Questions - Is this a standalone consumer calendar, or one bundled with email and work tools that business customers pay for? - Which users matter most: individuals managing their own time, people scheduling meetings at work, or families and friends coordinating shared plans? - Is the app new and trying to grow, or mature and focused on retention and reliability? - What will the metrics be used for: one company-level north star, or a dashboard that steers a specific team? ### What a Strong Answer Covers - A product goal and the main user types and jobs, such as personal planning, scheduling with others and shared family plans - A north-star metric that reflects value delivered, with an argument for why it beats alternatives such as daily active users or events created - Supporting metrics across the user journey: acquisition, activation, engagement and retention - Guardrail and quality metrics such as sync errors, missed reminders, double bookings and notification fatigue - How the metrics would be used in practice, and how each could be gamed or move for the wrong reason ### Follow-up Questions - Your north star rises while weekly active users fall. What could explain it, and what would you check first? - An executive wants the team to optimize invites sent. What could go wrong? - How would you separate the effect of a new auto-scheduling feature from seasonal swings such as holidays?