Threads is a platform to help growing teams share, discuss, and make decisions—no matter where they are . In an effort to help others transition to remote work, we've also made our plans free until July 1st.
I got a chance to demo Threads with @rousseaukazi a while back. I love how they're going slightly against the grain to reinvent the "forum" while everyone else is focused on real-time chat.
Thanks, @rrhoover!
One thing I like to think about is how the internet has been fully distributed from day one, and with that - so were online communities. These communities lived off of two core communication tools: IRC (urgent, quick chat) & Forums (important, thoughtful updates/discussions).
As work becomes more diverse & distributed, they're starting to resemble online communities more and more. Slack took IRC, stripped it down, and rebuilt it up for modern teams in mind. We did the same thing but with forums.
These two tools are meant to work together to give you the full range of communication. Create knowledge. If it's urgent, share it on Slack. If not, post it on Threads.
Trailing this now and it's a big improvement over our existing solution. Natural, intuitive, and fast. Great design and content experience. Feels like a no-brainer to switch. Thanks @rousseaukazi and co.!
Hey everyone!
Today, we are making Threads—a platform to help teams share, discuss, & make decisions no matter where they are—available to everyone. In an effort to help others transition to remote work, we've also made our plans free until July 1st. Sign up now at threads.com.
In Feb '19, we came out of stealth with a waitlist in place. The response was encouraging; not just in terms of numbers, but the breadth of customer diversity. From small groups to fully distributed teams to +1000 person organizations—we've been heads down listening & building.
The plan was to launch broadly later this year. However, with COVID-19 rapidly evolving & posing unique challenges for all, sitting on our tech wasn’t an option. And while this isn’t the way we imagined people to experience remote work for the first time, it’s on us to help.
As a community, we're all doing the best we can to support one another. So if you’re a big company becoming fully distributed or a small team figuring it out as it comes, shoot me a DM, send us questions, and check out our guides at www.threads.com. We're here to help.
Side note: We’re planning to start a space on Threads where people can come together & discuss remote working practices. If you’re interested in joining, let us know (wfh@threads) and please share with those who’d like to participate. Read more, here: https://threads.com/blog/launchi...
Looks nice, it's kind of a Notion + Slack blended in a proper timeline. Not sure how easy it is to adopt it in a company that already has a lot of these tools in place but I'll be watching how this evolves. (Notion could also benefit from some kind of a similar approach)
Great comment, @simonflore. A common question we get is how does Threads play into my current tool stack? Since a thread looks like a big white text box, the number one thing they ask is how it plays with doc platforms like: GDocs, Paper, Notion, etc. Here's how we think about internally:
When it comes to communication/collaboration, there are two categories of software that we use: Tools & Communication Channels.
[1] Tools are used to create specialized knowledge (sheets, slides, figma, docs, etc)
[2] Communication Channels are used to disseminate & discuss (slack, email, meetings, etc)
Threads is a channel built for important, thoughtful updates & discussions. Our belief is that for internal communication people should be using Slack & Threads. Create knowledge and if it's urgent (i.e. I need a response immediately), post it on Slack. If it's more important that everyone has time to read and respond thoughtfully, then post it on Threads.
On Threads, you can create a dedicated thread, embed all of the relevant materials (docs, images, etc), and provide some meta context for what you're trying to accomplish. If you have a minute, give https://threads.com/how-we-use-it a quick skim. It's filled with actual threads from our organization. If you scroll half way through, you'll see a thread started by Rochelle Shen, and you can see the types of focused discussions that a team is capable of having when using a communication channel like Threads.
Really appreciate your comment. Thanks for taking the time to share it!
We've used Threads at Loom in various capacities over the past few months and i can confidently say it has been gamechanging as we've scaled.
Engineering architecture reviews, Incident investigations/reports, design feedback, Process discussions etc etc etc
Conversations that would be lost in the constant activity of Slack are able to stick around and we are able to make more thoughtful decisions around things that may not require _instant_ responses.
I would highly recommend threads for any organization trying to improve their decision making and documentation processes (and a lot of other stuff)
Congrats on @rousseaukazi and the team for making a wonderful product!
Really appreciate you sharing your experience, @garshythoel. Loom is leading the way for hybrid/remote work, so it means a lot to us that Threads has been valuable. If there's anything we can do (in addition to expediting the Loom integration ;)), please let us know!
Congrats, will be keeping track of this! Left a few comments on your landing page in relation to your VP and social proof, hope its helpful - https://app.usebubbles.com/16de0...
Product Hunt