Fast incident response is pulling against confidence in an unverified cause.
On-call needs a shorter path through cross-platform evidence, while engineers need every suggested cause to remain challengeable.
Who you’d be doing this for
“I spent an hour telling people which thread was real, and nobody knew why replies were splitting.”
Luam Wekesa · Server Moderator
Runs a large interest community where members use threads and forum posts to organize ongoing discussions.
What is at stake
Reply and thread failures are splitting conversations across web and mobile, and engineers cannot yet agree where the break starts. You have to weigh faster incident traces against evidence strong enough for engineers to trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- on-call speed vs. evidence confidence
- ranked causes vs. engineer judgment
- cross-platform coverage vs. pilot scope
- automation assistance vs. production accountability
Why Discord
Replies, threads, and forum posts carry the coordination that keeps large communities usable when conversation moves quickly.
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.