Push over Pull

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>

With Each Other, with Software

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>

Twist Tips & Etiquette

But wait, why not Slack?

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>