Why We’re Betting Against Real-Time Team Messaging

Thank you — I agree with your vision, of connecting, deep work, time for reflecting and disconnecting. But it sounds to me like most of what you are talking about can be accomplished more through culture and practices than with tools and functionality itself. Getting people to take time off, not feel like they need to respond immediately, keep conversations tidy and in the right place, reply fully and thoughtfully, not need to indicate their availability/presence, and so on: these are more about practice and culture than the tool. It’s about how people use it. What you have created in Twist, is essentially the same as Slack and Teams, but with some slight functionality differences that emphasize your cultural slant. It is entirely possible to ignore presence, not respond immediately or feel a need to do so, thread conversations, search, take time off, turn off notifications, etc. in Slack and Teams. Likewise, it appears that Twist could be used as a real-time chat/messaging app, so it really depends on the users and culture. And it’s important for teams to discuss these issues and have some understanding/documentation about these practices and expectations.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.