|
|
|
|
|
by dmix
2409 days ago
|
|
So it's not just chat, but how Basecamp combines chat with a message board, allowing for a less pressing non-async alternative for certain types of communication. The secondary effect is the async chat kinda sucks which pushes people towards using the message board when they otherwise wouldn't? This is interesting. Often constraints make for a good experience. But in terms of solutions to apply more general to other companies it's difficult to nail down here (besides of course adopting Basecamp). As the author mentioned they tried having a sync backbone with Github Issues but eventually everyone just started using Slack for everything. I'm curious if a Slack company did a better job of directly integrating a sync message board feature if it would be used. Or would it require totally rethinking the product + a workplace culture/methodology. |
|