Hacker News Reader

Comment by llamataboot | Hacker News Reader

I have no idea why the answer to this problem is "using Basecamp!" - That doesn't make sense to me at all. For me the answer has been to turn off notifications and shut Slack when I need to go heads down, but review it multiple times a day and chime in where needed. It's still such a vast improvement over an email or email+issues based workflow.

View on HN

The CEO of a flat company probably has a need to see everything, JIC. Not all use cases are equal.

> The CEO of a flat company probably has a need to see everything

And Slack does an excellent job at demonstrating why that is idealistic nonsense and simply bad management that doesn't work, simply by making it possible to actually see almost _everything_.

It's one of the great things about Slack, it's much like Scrum in that respect: it may not be the answer, but it sure as hell will confront you with what the actual questions are.

Unfortunately, people who don't want to face their problems will immediately turn around and blame the tool/method. So very typical.

This is exactly the issue. Slack will expose more issues than it will create. If people misuse a tool because of some underlying problems, switching tools will just hide the problems, not solve them.

Sure, but how does Basecamp fix the problem? Wait for part 2, I guess.

Asynchronous communication ... slows things down and encourages a bit more thoughtful communication.

The founder of Basecamp alluded to this in a post very similar to this one https://m.signalvnoise.com/is-group-chat-making-you-sweat-74...

Exactly. I have DND mode configured for between 5 PM and 8 AM. No notifications, unless it's absolutely urgent. Which hasn't happened yet (thankfully!).

Reply on news.ycombinator.com