2 ms·

There were tools called bulletin boards or wikis created decades ago that can accomplish what is described above. All of these chatty tools require discipline b

by cudgy 5y ago

There were tools called bulletin boards or wikis created decades ago that can accomplish what is described above. All of these chatty tools require discipline by those making posts to not refer to other projects within the silo of the channel. I’ve found this to almost never happen. Email allows for normal conversational encompassing communication method that does not rely upon siloing information about projects into their respective channels. For example, if Blork and FooBar Projects are related In a comment that is made in one of the project channels, it is not easy to navigate their relationships in these tools Without explicitly adding tags to refer to the other channels. All these tags then create a spiderweb of useless links for the most part, and the information flow is weird and difficult to follow in many cases. This model can be advantageous for example when referencing checkins or other tickets within comments of a bug/story reporting system. However, bug reporting systems typically have fewer parties involved in the comments, so things don’t get quite as out of hand.

dagw 5y ago
There were tools called bulletin boards or wikis created decades ago that can accomplish what is described above. Far be it for me to defend Teams, but one thing it does kind of right is to automatically create a wiki, a project tracking and a file share page in addition to the chat space for each project so that you can, if you want, use the right tool for the job. That being said I worked at places a decade ago that tried to do the internal bulletin and wiki thing for their projects, and for whatever reason, it never worked anywhere near as well as I've seen Slack work. So while I agree in theory with many of the complaint levied against Slack as a productivity tool, in practice I've yet to see anything work better. But it is also clear that, for whatever reason, I haven't experience many of the time wasting antics that other people seem to be describing.

by cudgy 5y ago

dagw 5y ago

There were tools called bulletin boards or wikis created decades ago that can accomplish what is described above. Far be it for me to defend Teams, but one thing it does kind of right is to automatically create a wiki, a project tracking and a file share page in addition to the chat space for each project so that you can, if you want, use the right tool for the job. That being said I worked at places a decade ago that tried to do the internal bulletin and wiki thing for their projects, and for whatever reason, it never worked anywhere near as well as I've seen Slack work. So while I agree in theory with many of the complaint levied against Slack as a productivity tool, in practice I've yet to see anything work better. But it is also clear that, for whatever reason, I haven't experience many of the time wasting antics that other people seem to be describing.