Ex-Discord boss on product: why group consensus is a trap

This article summarizes an episode of Lenny’s Podcast’s video series featuring Peter Sellis, former product head at Discord.

Peter Sellis, former product head at Discord / Photo credit: Lenny’s Podcast

Giving teams power does not mean getting everyone to agree. It means being clear about who makes the final choice.

Peter Sellis, former product head at Discord, says waiting for group input can slow work down. To succeed, someone must be accountable for the final call.

This approach focuses on serving daily users rather than constantly chasing new ones. It also requires the discipline to say no to good ideas and use AI to help customers without overwhelming them.

Centralized authority accelerates independence

To turn clear decision-making authority into daily operations and reduce unnecessary debates, companies must follow a few guidelines:

• Ideological clarity: Teams must translate the company vision into phrases for everyday choices.
• Single-owner accountability: Each project requires one leader to ensure responsibility.
• Delegated risk: Pushing decision power to the capable employee saves risky choices for senior leadership.

For this to work, employees need to believe in what the company is trying to achieve. It comes down to a shared understanding of why the work matters and clear rules about who gets to make the final choice.

Daily retention outperforms broad acquisition

Once decision rights are established, leadership must focus on retaining the current audience rather than constantly chasing growth. As Sellis notes, “if someone uses the product once a month, you need 30 of those people to equal someone who uses it daily.”

To shift growth, teams must follow a framework to increase daily usage:

• Define daily utility. Write a statement explaining why a customer should engage with the product every day.
• Connect actions to loyalty. Link that core statement directly to user behaviors that foster retention.
• Fix core problems first. Resolve existing issues in the main product before launching features to avoid frustrating a willing audience.

AI amplifies the need for ruthless rejection

Maintaining the focus required for daily retention demands restraint. This discipline is made harder by AI development that risks cluttering the user interface and overwhelming customer attention.

Strong product teams demonstrate their judgment by adopting filters against feature bloat:

• Keeping a running list of rejected ideas to prove the team maintains high standards.
• Testing job candidates on canceled projects to verify they can walk away from unnecessary work.
• Demanding strong reasoning for every AI-enabled addition while regularly removing outdated features.