Company Context

Slack is a mature B2B collaboration platform used by millions of knowledge workers across startups and enterprises. Huddles, Slack's lightweight audio collaboration feature, has strong adoption in small teams but weaker repeat usage in larger organizations where users default to Zoom or Google Meet for scheduled and cross-functional conversations.

Problem

Over the last quarter, Slack collected recurring user feedback that Huddles feel "too casual for important meetings," are "hard to join or manage in large channels," and lack enough structure for follow-ups. Quantitatively, Huddles are started by 18% of weekly active teams, but only 42% of first-time hosts use the feature again within 30 days. Enterprise customers have specifically requested better meeting controls and clearer post-call artifacts.

Leadership wants to improve Huddles within one quarter, but engineering capacity is limited to one product squad. You are the PM assigned to decide what to do first based on this feedback.

Deliverables

1. Explain what you would do first to evaluate the feedback and avoid reacting to anecdotal requests.
2. Identify the most important user segments and the core problems worth solving first.
3. Propose a prioritized improvement plan for Huddles, including what you would ship in the MVP versus later phases.
4. Define success metrics and how you would validate that the changes improved the feature.
5. Discuss key trade-offs, including speed vs. confidence and simplicity vs. added functionality.

Constraints

• One cross-functional squad is available for 12 weeks.
• You may ship at most one major workflow change and two smaller supporting improvements in the quarter.
• Slack does not want Huddles to become a full Zoom replacement; the feature should remain lightweight.
• Any solution must work for both desktop and mobile, but desktop can be prioritized for MVP.
• You cannot rely on a large pricing or packaging change to drive adoption.