The notification path must restore timely coordination without making every server louder.
Weekend event participation depends on alerts arriving, while member trust depends on irrelevant alerts staying rare.
Who you’d be doing this for
“People keep asking why the raid started without them, and I don’t have an answer.”
Emi Suzuki · Server moderator
Runs a large gaming community whose scheduled activities depend on members receiving server notifications.
What is at stake
Opted-in members are missing time-sensitive server alerts while others receive unrelated pings. You must weigh reliable event delivery against the preference changes and safety exposure each path creates.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- timely event alerts vs. member notification fatigue
- global recovery vs. irreversible preference state
- model guidance vs. verified evidence
- weekend urgency vs. safety review
Why Discord
Discord server activity depends on members seeing the right message in time to join conversations, games, and events.
Written with these in mind
Not your kind of problem? 16 more at Discord, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.