🗣

Communications

We use threads.com and gitbook.com for communications.
Threads.com has:
threads and
group messages (#General and #Engineering, potentially #Operations and #Marketing later)
direct messages
GitBook has: 
long-form entries and playbooks
Here's how to know what to use:
things that are only relevant for today => group message in #General / #Engineering
Example: "hey ESLint is breaking for me, can someone help?" 
things that are for a week up to a month => thread (see below for etiquette)
Example: RFCs, Bug Reports, Sales Notes, ...
things that are only relevant for one person => direct messages
Example: "Hey can you book my link for peer programming?"
things that are relevant forever and future hires => GitBook
Example: This entry
The "Thread Police"
​
​
One thing we've adopted company-wide is the "Thread Police" 🚓🚓🚓🚓  essentially when a conversation either goes out-of-topic or is too sync-heavy (i.e. too many people chiming in, too many different opinions etc.) we move things into an async thread. 
Threads are more structured and less noisy, async friendly and easier to follow up at a later time.
Every employee in the team is empowered to share the "Thread Police" emojis 🚓
​🚓
​🚓
 when they feel like something gets out of hand in a group chat.
Anyone who keeps talking about this topic in the sync chat afterwards goes to async-jail immediately, you do not pass Go and do not collect $200.
​
Threads Best Practices
​
Using Blocks
Using blocks allows others to reply to specific ideas and/or sections of a thread instead of a large piece of text. Simply hit "enter" to add more blocks. See the example below:
​
​
​
​

Policies - Previous

Expenses

Next - Engineering

Managing Notifications

Last modified 2m ago