Let's cut to the chase: remote teams, especially startups, are slowed down by process. In an environment where all team members have to work quickly and independently, following a set of rules to launch a project takes up precious time and brainspace.

We realize that building a product often just introduces more complexity. And even though we think Slite Discussions solves an obvious blocker for remote teams, decision-making, it might just look another tool you have to learn, another process.

So, we wanted to quickly break down a set of guidelines for how Discussions fits into existing remote workflows by putting it into the context of tools that might be a little more familiar to remote teams: Slack and Asana.

Hopefully, you'll see how Discussions can make your remote work flow better, and more flexibly, without adding complexity.

Use a decision-maker like Slite Discussions when:

• You need to bring several people together to solve a problem
• You want to do so asynchronously

Use a chat app like Slack when:

• You need an answer now
• The majority of your team is online and available, and you want to do so synchronously (via chat or huddle🎧)

💡 Check out The Slow Slack Manifesto for more async Slack tips

Use a task manager like Asana when:

• You want to break down large projects and make decisions incrementally
• You only need to discuss via highly contextualized comments on the tasks themselves
• You have a task manager that's specific to your work and department (Linear for Product teams, Github Issues for Devs, Ashby for HR, etc)

‍

Learn more about Slite Discussions in this short video: