
The sketches are quick and fairly rough so instead of sharing those, I’ll share the designs that were created from those sketches.

Develop: challenges of designing an overlayīefore opening up a design program we started sketching and whiteboarding ideas. We updated the spec, reprioritized features, and set scope so the team was aligned before starting development. In the case of our overlay redesign, our discovery phase helped further define the product spec. This process is collaborative, the entire product team - both engineering and design - can weigh in on all aspects of the project. This document describes what we’re building, who we’re building it for, and the outcome we want to achieve. Our projects at Discord start with a product spec. More like we grew a third arm and we give amazing hugs now. It shouldn’t feel like a different product.

We should aim to include all of the quality of life and fun features of the desktop app whenever possible.

In order to define what a valuable overlay experience might look like, we set aside additional time for discovery during our design process. This process can be broken down into four phases: discover, define, develop, and deliver. The Discord design team’s process generally follows the double diamond method. While this focus on voice features was useful, we wanted to make the overlay useable for Discord’s other core features. This feature worked well for switching voice channels, seeing who was talking, or knowing which of your friends left their microphone unmuted ( I’m looking at you, Siegfried).
