Twist
Tame chaotic teamwork with Twist
Start new thread

Twist 2.0 - For teams burnt out by real-time chat, work async, not ASAP

by
•
Twist is asynchronous messaging for the flexible future of work. Break free from the 9-to-5 and the constant meetings, emails, and Slack chats. Join the async work revolution where you — not your teammates — dictate your schedule.

Add a comment

Replies

Best
Using Twist daily. This made my day. Wish you the best and congratz.
Maker
Awesome to hear, Petr 🙏
Love the philosophy. Big fan of doist and it’s values. Wishing you all the best on your future of work bets.
Sounds like this product was made for me!
I love this slogan: Work async, not ASAP! Can relate to everything you describe, we (my company Alconost) are also a remote company spread across 10+ countries, and the ability to work asyncronously is important. Good luck with the launch! ;)
Loving the new update. Great work!
Congratulations and team! The future is of work is definitely async 😎
Looks good, one of the problems with async I find is the opposite problem - people being ignored and essentially blocked for many hours unable to find a resolution. I assume this is a reaction in many teams to the ASAP issue you mention. Would be interesting to see if Twist helps in that regard - individually urgent things get dealt with while the noise can get pushed back
Maker
one way to combat this is by embracing a more transparent culture, for example: — Most Twist channels should be public, including leadership channels — Having a handbook-first culture that documents things, for example, core workflows. See GitLab's handbook for an extreme example of this — Most services/knowledge should be accessible by default to the team (e.g., access to Github repos, Google Drive docs should be shareable to the whole organization) When you do this, people can unblock themselves. Another critical aspect in async-first is having independent people that can easily manage their work and remain accountable with little or no direction. E.g., if they are stuck on one problem, they will tackle another one.
great points, I think the most important thing is public channels and good docs. I’m trying to bring in both at a place at the moment - so much information is just in people’s heads
I have been thinking about Twist and the "Future is async" concept, and I got the same question, that is how to deal with people not getting answered on time. I agree that independent people can manage such situations better (in our company culture, that's exactly the type of people we try to hire), but sometimes a colleague needs a reply from me personally, and it may be urgent. Not being able to see whether I'm online or not could be stressful in this case, as my colleague would have no way of knowing the chance of me replying any time soon. This aspect is kind of bothering me when I think of using Twist.
Maker
in Doist, we have the phone number of everyone, and we can message/call them if we really need them urgently. This method is only used a few times in 10+ years. Most things aren't urgent. A core problem is that the current way to communicate is making every message urgent and something you need to look at right away. Urgent communication should be the exception and not the default. That's at least how we think 😊
Hey Amir, thanks for sharing! I'm a bit suprised you guys hardly ever have urgent requests, but maybe this is something to get used to... and something to be spread through the company culture :) I am curious about this topic now and will keep exploring it :)
What a lovely redesign. I've been a fan of Twist for many years but couldn't convince the team to switch away from Slack and now it's too late.
Maker
it's never too late to adopt a better way of communicating, working (and living) 😅
Very cool idea
Great solution for remote working! Having quick conversations about multiple tasks makes it so easy to miss/forget something and then have to scroll back to try and find it is very time consuming.
First
Previous
123
Next