Every time I search for a solution to a problem for Drupal 10/11, I get page after page of results for Drupal 6/7. By Drupal 8 discussions had moved from groups and issue queues to Slack.
Communities are having the same debates over and over. New members ask questions that were definitely answered six months ago. Teams rediscover solutions to problems they already solved. Users search for solutions to problems that seem to repeat. And repeat. And repeat.
We used to have forums. And forums had one massive advantage: you could find things.
Threads had descriptive titles. There were categories. Search actually worked because the content was structured for retrieval. If someone asked a question that had been answered before, you could link them to the previous discussion instead of retyping everything.
Then Slack happened, and Discord, and Teams, and we all decided that real-time chat was simply better: More modern // more collaborative. More like how humans “naturally communicate” (as if there’s anything natural about the internet itself.)
[…]
Companies pay for Slack per user per month. The cost of storage is real but abstracted. Meanwhile, the cost of fragmenting and decaying knowledge is completely invisible until it’s too late. How do you measure the time wasted rehashing old decisions? How do you quantify the mistakes that could have been avoided if someone had been able to find that old discussion?
These costs are real and large, but they don’t show up in any budget line.