Slack · Metrics · Entry · 60 to 90 minutes

Measure success for Slack Huddles

Slack is a workplace messaging app that helps teams communicate in channels, direct messages, and quick audio or video conversations called Huddles. Answer this product management case and get it graded line by line against a weighted rubric.

Metric design
User segmentation
Funnel thinking
Tradeoff judgment
Analytical communication

The situation

You are an APM on Slack's Conversations team. The senior director who oversees messaging and Huddles has asked you for a simple measurement plan before next quarter planning. Huddles is now a visible part of Slack, but leaders disagree on what success means. Some teammates point to more Huddles started each week after recent entry point changes. Others worry that starts alone reward accidental taps, longer calls, or behavior that pulls people away from Slack's async messaging, which is still the core product experience. Sales also wants a clear story for paid customers, while engineering notes that real time audio and video have higher infrastructure cost than messaging. Assume the following numbers are illustrative: 18 percent of weekly active users in paid workspaces joined at least one Huddle last week, Huddle starts per active workspace rose 22 percent over six months, median Huddle length was 7 minutes, 42 percent included screen sharing, and repeat weekly usage among first time Huddle users has been flat. Your task is to define how Slack should measure whether Huddles is succeeding, and what the team should examine first.

What to produce

A 1 to 2 page metrics recommendation memo.

Your answer must

Define one primary success metric for Huddles, including numerator, denominator, time window, and why it reflects user value for Slack.
List 3 to 5 supporting metrics, clearly split into leading indicators and guardrails, and explain what each metric helps detect.
Segment the metrics by at least 3 meaningful cuts, such as workspace size, paid vs free, new vs existing Huddle users, DM vs channel Huddles, or desktop vs mobile.
Include a simple metric tree or funnel from discovery to first use to repeat use, and name one likely failure mode at each stage.
Recommend the first analysis or experiment Slack should run in the next month, including what decision the result would inform.

Constraints

You have two weeks and one data analyst working half time.
You may use existing product telemetry and at most one lightweight in product survey.
You cannot use message, audio, or video content because of privacy and compliance commitments.
No major client side instrumentation changes can ship before next quarter.

Format

Start with the main success metric and why it fits Huddles. Then show supporting metrics, segments, and the first next step in a short, easy to scan structure.