The future of workspace communication is ticket-based; prove me wrong.

Slack and Teams are like cancer: they were supposed to replace emails for faster communication and collaboration, but due to their low perceived formality and ease of use, they ended up becoming the place where stress and chaos reign.

Information gets constantly lost in D.M.s, threads, and channels. Every time somebody farts, there's a notification for that. Gifs and emojis mask what's essential from what's not. It's increasingly difficult to extract the relevant from the irrelevant.

I've just been to WebSummit in Lisbon, and there were five talks on "Slack and Teams' noise" alone.

I mean, are we sure they are here to stay? I've talked to around 100 people in the past four months, most of whom mute Slack or Teams altogether.

After talking with them and analyzing their communication patterns, it seems like most work-related requests flowing in Slack and Teams can be structured (i.e., Budget approval, Design work, etc.).

"Forcing" people to structure their requests (i.e., title, impact, urgency, etc.) would make them think twice about the importance of what they are asking and whether they already have the answer. In addition, it would automatically help the receiver to filter out the noise and centralize requests.

What are your thoughts on this? Do (did) you see yourself communicating in tickets within your organization?

P.S.
Be brutal; I've started to build something to try to solve this.