In order to provide a workplace that accommodates many timezones, and allows people freedom and space to work when they want to (with less meetings), it is everyone's responsibility to communicate proactively. By default, we opt for effective push communication, with pull communication being used only when necessary.
📥 Pull-based communication is when you need to manually ask someone for information. You're beholden to their availability, knowledge, etc; and you may not even know the right person to ask the question. This is often very inefficient, and may lead to confusion and misaligned priorities. ****If you're often pulling communication from people, please ask them to push their information more often.
📤 Push-based communication is when a person closest to a packet of knowledge that impacts their teammates takes responsibility for documenting their knowledge and disseminating it to their team. In this model, it should be rare that the team is asking each other for information; because everyone's done a great job of making it available. This allows us to have less meetings, and a life free of managers. Use your discretion to proactively push the right information, to the right people, at the right time.
Examples:
<aside> ⚠️
If you're constantly inundated by requests for information, or updates on project specifics, this is an indicator that you're likely not "pushing information" often enough, or in a centralized and easy to search location.
</aside>
As a remote-friendly company, it's really, really key that important conversations don't happen in sidebars. We're open, transparent, live on different timezones, and have different lives. Access to information needs to be democratized. Everyone should be able to follow and participate in conversation, and that conversation should easy to follow, and not distracting.
<aside> 💡 What this means: You should almost never use DMs or internal emails. More often than not, that information should be searchable and archivable by the whole company - and probably belongs in a Twist thread (or Notion doc).
</aside>
⭐️ Tailor your Recipients. ⭐️ When you're sending a message, do you really need to notify everyone in the whole channel? Take an extra moment, and ensure you're only notifying the few people that you know need to be informed.
Offer a TLDR (above the fold) for big messages. Twist prompts people to organize their communications (rather than spam one-liners), which is a good thing. However, if you're writing a lot of words, give a TLDR at the top so folks can quickly know if they need to engage.
**Acknowledge Communication.** People often put a lot of time and thought into their communication on Twist, so be sure to let them know you read it. If you're still thinking, it doesn't hurt to drop a quick note saying when you expect to respond to them.
Remember that Reactions don't Notify. If you need want to bump something up in someone's inbox, be sure to use a message, instead!
Use Twist Inbox Zero. This allows you to calmly track things you want to respond to, and archive things that aren't relevant. That's a stress free way to be sure you're on top of what matters.
Setup Channel's Default Recipients appropriately. When creating a new channel, you can setup the default Notification Recipients to be a subgroup of people in that channel (or no-one at all). That way, the only folks who are notified are
Prune the Channels you're in. If you find you're getting a lot of notifications for topics that aren't important to you, you've probably been pulled into a channel for a single communication that you no longer need to subscribe to. Do yourself a favor, and prune those!
It's OK to Log Off! Push-based communication combined with a culture of high-fidelity documentation means that a need for "Just In Time" communication is exceedingly rare at this company. There's no "green/yellow/grey" status dots in Twist for a reason: you're not expected to stare at it all day. If you need to do deep work, just close Twist for a while! You can also adjust notification settings and use Time Off.
When editing, make it clear what you edited. Strikethroughs are helpful, so others can understood what you changed!
Archive channels: When a client project etc is complete, archive that channel. It's a good practice to make our channel directory more digestible. Archived channels still appear in search.
Close Inactive Threads — It's a good habit to maintain the threads in channels you are active in. When a conversation is done or no longer active, close the thread and add a helpful TL;DR summary message to help with searches and context sharing.
Public over Private — If something comes up in a DM that is relevant to more people, cross-post that to a public thread to practice good Push Communication hygiene.
Use Time Off when you are OOO — In service of Push Communication, we should be able to @ mention anyone at any time, without fear of disrupting one person's PTO. When taking time off, setup your Time Off preferences so you don't receive notifications, but still can see mentions in your inbox when you are back.
We used Slack for a while. It was fine, but noisy. As we moved remote and decentralized, we started to realize that conversational context was being lost a few messages deep. It was hard to follow discussions, and it felt like you had to check Slack every 5 minutes to attempt to stay on top of everything. It was impossible to search anything effectively. We were distracted, and it was not serving us well.
<aside> 💡 Slack is great for bugging people in real-time — but if you find that your workflow constantly needs real-time communication, then that's a symptom of a bigger problem! Instead, we'd encourage you to raise that issue with your team, and find a proactive & organized solution instead.
</aside>
Slack is not designed for mindfulness and deep work. We decided we needed to move to a communication platform that places more emphasis on threading & documentation instead of instant messaging. You can read more about Twist here
<aside> 👉 Twist Tip: To improve the ease of finding information on Twist via search, add a clear, concise, descriptive conclusion message when you close a thread. This message should summarize any important information shared within a thread, as well as any discussion outcomes and action items.
</aside>