Discord Product Improvement: Choose a Segment, Find Pain Points, Prioritize Fixes

Quick Overview

A product improvement case on Discord, the server-based community chat app. It tests whether a candidate can set a goal, choose one user group, find real pain points in how that group uses servers and channels, prioritize solutions by impact and effort, and define success metrics with guardrails.

Discord Product Improvement: Choose a Segment, Find Pain Points, Prioritize Fixes

Company: Discord

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are asked how you would improve Discord, the chat platform where people gather in servers made up of text channels, voice channels and threads, and also talk one-to-one through direct messages. Choose what to improve, explain why it is the right thing to improve, and describe how you would know the improvement worked. ```hint Pick one group first Discord serves very different people: gaming groups, study and hobby communities, creators with large fan servers, and the admins who run them. Choose one group and find where their experience breaks down before proposing features. ``` ### Clarifying Questions - Is there a goal to optimize: attracting new users, deeper engagement from existing users, or revenue from the paid Nitro subscription? - Should the improvement serve the members of communities, or the people who create and moderate servers? - Is there a platform focus, such as the mobile app versus desktop? - Are we looking for something shippable in a quarter, or a larger multi-quarter bet? ### What a Strong Answer Covers - A goal grounded in where Discord stands, with a reason it was chosen over the alternatives. - A deliberate choice among distinct user groups, such as gamers, non-gaming community members, server admins and moderators, and creators. - Pain points drawn from how Discord actually works, such as finding servers, getting started in a crowded server, keeping up with busy channels, and notification overload. - Several solutions prioritized by impact and effort, with one chosen and specified in enough detail to build. - Success metrics with guardrails for spam, moderation load and notification fatigue. ### Follow-up Questions - Your feature raises the number of servers each user joins, but messages per server fall. Is that a win? - How would you keep your improvement from making it easier for spammers or raiders to find and flood communities? - How would your plan change if the goal were Nitro revenue instead of engagement?

Overview: A product improvement case on Discord, the server-based community chat app. It tests whether a candidate can set a goal, choose one user group, find real pain points in how that group uses servers and channels, prioritize solutions by impact and effort, and define success metrics with guardrails.

Discord logo
Discord
Nov 19, 2024
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are asked how you would improve Discord, the chat platform where people gather in servers made up of text channels, voice channels and threads, and also talk one-to-one through direct messages. Choose what to improve, explain why it is the right thing to improve, and describe how you would know the improvement worked.

Clarifying Questions Guidance

  • Is there a goal to optimize: attracting new users, deeper engagement from existing users, or revenue from the paid Nitro subscription?
  • Should the improvement serve the members of communities, or the people who create and moderate servers?
  • Is there a platform focus, such as the mobile app versus desktop?
  • Are we looking for something shippable in a quarter, or a larger multi-quarter bet?

What a Strong Answer Covers Guidance

  • A goal grounded in where Discord stands, with a reason it was chosen over the alternatives.
  • A deliberate choice among distinct user groups, such as gamers, non-gaming community members, server admins and moderators, and creators.
  • Pain points drawn from how Discord actually works, such as finding servers, getting started in a crowded server, keeping up with busy channels, and notification overload.
  • Several solutions prioritized by impact and effort, with one chosen and specified in enough detail to build.
  • Success metrics with guardrails for spam, moderation load and notification fatigue.

Follow-up Questions Guidance

  • Your feature raises the number of servers each user joins, but messages per server fall. Is that a win?
  • How would you keep your improvement from making it easier for spammers or raiders to find and flood communities?
  • How would your plan change if the goal were Nitro revenue instead of engagement?