A forum is going to be way more searchable. If you want realtime notifications that was solved 50 or more years ago with email or say 20 ish years ago with RSS.
For this reason I prefer JIRA
comments with @-ed colleagues over slack which provides the context and async communication.
An ephemeral slack-like (snapchat for teams!) might be useful for the remote equivalent of talking which is also ephemeral. Knowing that the conversation will be lost and will be interruptive should move most stuff on the forum.
ATC style short radio-style communications might be interesting for this too. “Dan please check broken build. Out”
But yeah there is a lot of cultural bias towards slack like chat systems and at large companies changing that would be like trying to switch away from active directory: unplausable!
I've been thinking about "ephemeral Slack" the last few weeks after a flurry of posts about Slack and workplace communication.
I love the idea. I use Slack a lot for technical discussions with my peers. I've noticed that I seem to be the only person in our department that translates these discussions into Confluence/GitHub documentation.
I'd be very interested to see if an "ephemeral Slack" would force us to be better about documenting our discoveries/decisions/designs etc. It (Confluence) is something everybody at the company complains about, yet few actually attempt to maintain/improve.
Don't get me wrong, Confluence deserves the hate, but we don't have alternatives and, surprisingly I find Confluence a lot nicer to use than trying to search Slack when I run into an issue (provided I know where to look in Confluence, another problem in itself).
I was bummed when StackOverflow got rid of their teams feature, I had always wanted to try that out. I would 100% be on board with a forum for all long-form and persisted communication.
Ideal world: ephemeral chat for day-to-day, forum for persisted comms and institutional documentation, and zero email.
A forum is going to be way more searchable. If you want realtime notifications that was solved 50 or more years ago with email or say 20 ish years ago with RSS.
For this reason I prefer JIRA comments with @-ed colleagues over slack which provides the context and async communication.
An ephemeral slack-like (snapchat for teams!) might be useful for the remote equivalent of talking which is also ephemeral. Knowing that the conversation will be lost and will be interruptive should move most stuff on the forum.
ATC style short radio-style communications might be interesting for this too. “Dan please check broken build. Out”
But yeah there is a lot of cultural bias towards slack like chat systems and at large companies changing that would be like trying to switch away from active directory: unplausable!