Prioritize Roadmap for Team Chat

Company Context

PulseChat is a B2B workplace messaging platform serving 25,000 companies and roughly 3.2M monthly active users. It competes with Slack and Microsoft Teams by focusing on mid-market companies that want simpler workflows and lower admin overhead.

Problem

Growth has slowed, and leadership wants the next two-quarter roadmap to improve retention and expansion revenue. Product research shows three major opportunities: enterprise admins want stronger compliance controls, end users want less notification overload, and sales teams are pushing for AI meeting summaries to win competitive deals. Engineering capacity is limited to one major initiative plus one smaller supporting feature this half.

The candidate should explain how they would prioritize among the following roadmap candidates:

• AI meeting summaries
• Advanced admin audit logs
• Notification bundling and quiet hours
• Cross-workspace search
• Workflow automation templates

Recent data:

• Gross revenue retention fell from 91% to 86% over 2 quarters
• Enterprise win rate drops by 18% when compliance features are missing
• 34% of churned users cited "too many notifications" in exit surveys
• AI summaries are requested in 22% of active sales conversations, but only by larger prospects
• Cross-workspace search is heavily requested by power users, who represent 12% of accounts but 31% of seat expansion

Deliverables

1. Define the prioritization framework you would use and why.
2. Segment the users and identify whose needs should drive this roadmap.
3. Rank the roadmap candidates for the next two quarters with clear rationale.
4. Explain the trade-offs you would make across user value, business impact, effort, and strategic positioning.
5. Define success metrics and how you would revisit priorities if new data emerges.

Constraints

• 2 quarters to deliver meaningful impact
• Capacity for 1 large initiative and 1 smaller initiative
• No increase in infrastructure spend above 12%
• AI features must meet basic enterprise privacy requirements before launch