Defining a North-Star Metric and Guardrails to Measure Slack's Success

You are a product manager at Slack. How would you define what success looks like for Slack, and which metrics would you track to know whether it is getting there? ```hint Decide what to count Slack is paid for by organizations, but its value appears only when colleagues use it with each other. Settle which unit your main metric counts before you name the metric. ``` ### Clarifying Questions - Do you mean the success of Slack as a product and business, or how I would measure my own success as a PM at Slack? - Should I cover Slack as a whole, or one area such as the free-to-paid funnel, huddles, or Slack Connect channels shared with other companies? - Is the goal a health dashboard for leadership, or the single metric that product teams' roadmaps should move? ### What a Strong Answer Covers - The value Slack creates for the people who use it and for the organizations that pay for it, used to justify the metric choice - A precisely defined north-star metric (unit, qualifying action, time window) and why it beats alternatives such as active users, message volume or revenue - Supporting metrics along Slack's adoption path: workspace activation, depth and breadth of use inside an organization, retention, conversion and seat expansion - Guardrails that catch growth that hurts users, such as notification overload, after-hours messaging or reliability problems - Segmentation by plan, company size and workspace age, and how often each metric is reviewed ### Follow-up Questions - Weekly active users goes up while paid seat expansion stays flat. Where would you look first? - A colleague proposes total messages sent as the north star. How would you respond? - How would your metrics differ for a large enterprise rollout compared with a small team on the free plan?