Welcome to Threads! We wanted to share a few helpful resources on how to best get started on Threads. If you have additional questions, feel free to reach out to firstname.lastname@example.org or use this Calendly link to sign up for a time to chat!
Going from 'Critical' to 'Closed'
Threads is a modern forum for work which helps teams take critical conversation and get them closed out on time, without the meeting. Here's a quick overview of how we solve that problem:
Right now, we think most critical conversations get kicked off in chat, but chat makes it extremely challenging to revisit older conversations, understand which ones you need to prod / push, and which ones you can forget about. This leads to critical conversations failing to get closed out on time, and folks booking meeting in order to make a final call quickly. It doesn't have to be that way: Written communication should be easy to follow, easy to skim, & easy to close out.
With Threads, you have a simple recipe for ensuring critical conversations get closed out:
Write up a decision you'd like to make in a Thread.
Share broadly, but request responses from the folks who you need explicit buy-in & responses from.
Set a due date / deadline, and let Threads take care of compiling neat communication "ToDo lists" for your stakeholders. Over time, we'll build out reminders, nudge you when a critical conversation you started hasn't closed out, and suggest 1:1 topics for folks who owe you responses.
That is the core vision of Threads: To create beautiful, seamless workflows that allow you to take critical conversations, kick them off, & count on our software to seamlessly gather answers & alignment from your team.
Getting set up on Threads
There's a few core things which are helpful in getting set up on Threads:
Download the apps: Download the desktop and mobile apps here.
Create an Organization: You can create an organization which will allow everyone from your team
Set up the Slack Integration: Once you create an organization, you can search for 'integrations', and then set up the slack integration. This will allow you to link a forum to a slack channel.
Set up Security: If you are a member of a larger organization and would like to setup SSO or SCIM, feel free to reach out to email@example.com to facilitate the set up.
Craft an intro Thread: Finally, you can craft an intro Thread to get your team ramped up on the basics of Threads. We generally recommend covering the basic problem you hope to solve with Threads (covered above), plus a few use cases (which we will share below). You can even request responses from folks within your organization to understand their thoughts on using Threads.
Working on Threads
Here's a sampling of how we work at Threads:
Threads for facilitating weekly meetings
We facilitate weekly meetings by posting an agenda every week, and requesting a response from anyone who has a discussion topic. We set deadlines ahead of the meeting, and if there are not agenda topics ahead of the meeting, we cancel the meeting.
Building up Institutional Knowledge on Threads
We use Threads as an internal "stack overflow". This allows us to ask questions & answer them in a public forum, which builds up institutional knowledge for the entire team. This also prevents folks from feeling compelled to move the conversation into a different so as to not spam others. This means a more accessible & searchable repository of company knowledge.
Eng Investigations on Threads:
We also use Threads for all of our engineering investigations - this helps us take a simple observation like the site being slow and turn it into an example around how to investigate similar issues in the future.
Eng Proposal Forums:
Finally, anytime we write a PRD, we write it in Threads. This enables a much greater sense of transparency at the company, and allows anyone to weigh in on any architecture decision happening across the company. For our engineers, this means we're much less likely to go far down a path which ultimately has some flaw which one of our colleagues can spot.
Threads for faster product development:
Similar to eng proposal forums, we will host our product development conversations (questions, proposals, meeting notes, etc) in a single forum. This keeps all the conversation regarding a specific feature or project in a centralized location, and allows us to flag important considerations & get back to them on our own time.
Product Feedback on Threads:
We post product feedback on Threads because it allows us to flag issues & new ideas in a setting where it is easy for the rest of the team to add in their support, and it enables the PM to take their time & revisit the idea when they are ready to address it principally.
Threads for sharing insights & Analysis
Whenever we conduct a new analysis, we publish any insights & analysis into Threads so that we can be sure the right people can read & respond on their own time.