Discord Waypoints
Sondhayni Murmu
Discord "Waypoints"
Discord has spent years helping people find communities. This is about staying part of one.
Role
Design, research
Timeline
2024, revisited 2026
Tools
Figma, Claude Code, Notion, Discord
A spec project I first explored in 2024 and found my way back to in 2026 — the AI landscape had made things possible that weren't practical at the time.
Current State
What opening Discord looks like today:
Every server is its own community…
…with dozens of channels, all running in parallel…
…each filling up whether you're watching or not.
Actual screenshot taken from actual Discord.
Discord is organized around servers — persistent communities built around shared interests. Inside each server, content moves through channels: text, voice, and thread-based spaces that fill continuously. At scale, an active server generates more content than any member could read.
It starts to feel a little like this:
Research
The Starting Point
I conducted 7 interviews across two rounds.
Every person's relationship with Discord was different — different servers, different habits, different reasons for showing up. But when I mapped specific behaviors rather than attitudes, two patterns kept surfacing.
Affinity map — click to zoom
Two Patterns
Every pass through the data landed in the same two places.
The Observer
Reads channels regularly, rarely posts
Has typed a reply and deleted it before sending
Drops in, catches up, leaves without a trace
Wants to feel part of the community without performing membership
The Contributor
Posts when something comes to mind — doesn't wait for the right moment
Joins conversations mid-thread without hesitation
Uses Discord to contribute as much as to consume
Checks back to see if anyone responded
2024 — Original Design
The problem wasn't the content. It was the navigation to find it.
What Discord had already built going into 2024
Threads (2021) - Organise fast-moving chat into side threads
Forum channels (2022) - Browseable topic threads for focused discussion
Browse Channels (2023) - Admin-curated channel discovery for new members
AI Summaries (2023) - Catch up on what you missed while away
Favorites (2026) - Pinned channels from across your servers — surfaced in one sidebar
The "Launchpad"
In 2024, working from this research, I designed a "Launchpad" home base — a personalized view that surfaced relevant content from your servers without requiring you to visit each one individually.
Discord launched Favorites as an experiment in 2026 — essentially what Launchpad was: a pinned list of channels from across your servers, surfaced in one place.
2026 — Audit
Between 2024 and 2026, Discord shipped three more features in this space. By 2026 the underlying AI tooling had matured enough to make this worth revisiting. The audit is a check on what had changed.
Feature | Problem it solves | Problem frame | Helps re-engage after absence? |
|---|---|---|---|
<br>Bookmarks / Reminders Sept 2024 | Save messages and resurface them at a chosen time | Information | No |
<br>Ignore Feb 2025 | Hide specific users without blocking them | Information | No |
<br>UI overhaul (inbox, density) Mar 2025 | Inbox repositioned, navigation tightened, UI density options added | Information | No |
? | ? | Participation | Yes |
Every shipped feature makes information easier to find. Waypoints is the member-side counterpart to Browse Channels: instead of an admin curating what's visible, each member declares what matters to them.
The Gap
The Observer
Reads channels regularly, rarely posts
Has typed a reply and deleted it before sending
Drops in, catches up, leaves without a trace
Wants to feel part of the community without performing membership
WHAT THEY NEED
A clear on-ramp back into conversations they care about.
The Contributor
Posts when something comes to mind — doesn't wait for the right moment
Joins conversations mid-thread without hesitation
Uses Discord to contribute as much as to consume
Checks back to see if anyone responded
WHAT THEY HAVE
Posting doesn't feel like a big deal — the barrier to contribute is low.
Take Chelsea: Design Buddies announced a design-a-thon, and she wanted in. By the time she went to join, teams were already formed. Discord showed her everything — it just didn't know this was the thing she'd been waiting for. A Waypoint for "design-a-thon" would have caught the announcement, the team formation thread, wherever it came up — surfaced to her when it was still actionable.
Waypoints — The Solution
A Waypoint lives within a server. You set it once, declare what you're tracking, and it monitors that server's channels indefinitely. Radar is the other half — a unified feed that surfaces every match from all your active Waypoints, wherever they came from.
Two surfaces
Waypoints are scoped to individual servers — you're telling a specific community what you care about within it, not setting a global interest across all of Discord. Radar aggregates the results: one feed that pulls every match from every server where you have an active Waypoint.
Setting a Waypoint
From the Waypoints panel in any server, or right-click any message to start from context. The system proposes a Waypoint based on the message; you edit it to match what you actually mean. Nothing is created silently — every Waypoint is visible, editable, removable.
Radar
Radar is a scrollable feed of everything that matched your active Waypoints — across every server, in one place. Navigate directly from a match to its channel, edit a Waypoint on the spot, or filter by server.
A Waypoint for "design-a-thon" should catch posts about it whether they say "design sprint", "collab project", or anything else that means the same thing. That's semantic matching — it's what makes Waypoints work in natural language rather than as a keyword filter.
This isn't notifications.
Notifications are sender-controlled and about recency — they fire because someone posted. Waypoints are user-controlled and about relevance — they surface because you declared interest. The trigger is completely different.
Prototype
Three navigable flows — the Radar feed, the Waypoints panel, and the right-click entry point. At the bottom right is a button to open a control menu to view all available flows and states.
Built with Claude Code — routing, Figma-faithful components, and the semantic matching mock in a few evenings. The AI tooling that made this fast is the same shift that made the core feature possible.
Impact & Measurement
If this shipped, here's what you'd watch — and what each signal would actually tell you.
Discord has 260M monthly active users and 31.5M daily actives. Within that gap are Observer-segment users — people who are in their servers, care about them, but don't know what's worth engaging with when they show up — and without a clear reason to, eventually stop.
7.3M Nitro subscribers
31.5M Daily active
~229M monthly-not-daily — Observer behavior likely concentrated here
Waypoints is a lever at the Observer → daily active boundary.
What success might look like
If this shipped, these are the signals worth watching — and what they'd actually tell you.
DAU/MAU ratio — Observer segment
First post rate
Waypoint-to-engagement rate
Waypoint retention at 30 days
Reflection
The assumption I'd validate earliest is NLP reliability. The design depends on matches being good enough that one imperfect result doesn't break trust — visible match attribution is the recovery mechanism, but that's worth testing against real data.
TL;DR
Discord has an information problem, but it also has a participation problem - this is the design that addresses the latter.
Like this project
Posted Jun 6, 2026
Designed a feature for Discord to enhance community engagement through personalized content tracking.
Likes
0
Views
0
