| ▲ | allan_s 5 days ago | |
in my company we do this a LOT, what helps if having a LOT of slack channels with explicit topic name like * "incident-2025-07-28-CI-not-deploying-disk-full" * "feature-stripe-integration" * "exploration-datadog-or-sentry" and channel comes and go and people are quite "agressive" about routing discussion to the right channel or converting 10+ message thread into dedicated channel. | ||
| ▲ | skeeter2020 5 days ago | parent [-] | |
>> and channel comes and go and people are quite "agressive" about routing discussion to the right channel or converting 10+ message thread into dedicated channel. THIS. I had this at my last gig and it was very successful, but have not been able to replicate at the newer place, because the house keeping is not done, so people end up with the logical conclusion, wrong question that living with a few messy channels is better than living with a bunch of messy channels. I like lighter weight tools that integrate & help like incident management bots, but the vendors will no longer sell you a cheap, useful & focused tool so instead you're faced with convincing your boss to spend a lot of money on an "enterprise-grade", AI-enabled do everything incident/schedule/status/issue/project management system. | ||