AsyncGo is designed to make it easy to get up and running with your team. It doesn’t require getting rid of any of the other tools you use, though you may decide to do so later, and it doesn’t require changing any of the behaviors of anyone outside your team.

Within your team, there are three main applications that adopting AsyncGo will change your usage of.

There are documentation sections for Basics, Onboarding, Roadmap, Topics, Teams, User Settings, Integrations, Templates, and Markdown.

On this page you can find:

Reducing usage of video conferencing (Zoom, Teams, etc.) and meetings

The first and most fundamental - don’t schedule that meeting that you’re considering having, especially if the meeting is within your own team. Instead, open up a new topic and place the meeting agenda there.

If you’re including someone from outside of your team, then you have a decision to make. If you think the person is up for participating then you can always invite them to your team. From that point on they will be able to participate as a normal user.

With all your free time that you’ve freed up from meetings, consider scheduling a coffee chat or two with someone that you’d like to have a more free-form, human conversation with. It’s a much better use of your time than work meetings where everyone is staring at documents or quietly working on something else in the background.

Replacing ongoing discussion agendas (Google Docs, Notion, etc.)

With AsyncGo, you also don’t need a register of topics that are in discussion. A lot of companies use a Google Doc for this, with a long list of topics that they keep coming back to and/or archive off for later reference. Instead, use the topic list in AsyncGo itself to keep track of all the various things you’re discussing.

One of the most powerful features of AsyncGo is how the complete list of discussion topics is right there for anyone to see, and they can choose to participate at any time if they have something to contribute.

Reducing usage of chat (Slack, IRC, etc.)

Chat is an insidious one. It almost feels async, but anyone who has felt overwhelmed at the pace of threads happening in chat will attest to the fact that it’s more realtime than they’d let you believe. To get the most out of AsyncGo, whenever there’s a deeper topic that you want to give time for people to reflect on and participate at their convenience, don’t start a Slack discussion. Instead create a new topic in AsyncGo and link to it from your channel.

Realtime chat is great for the things it’s good at, which is quick clarifying questions and short interactions, so try to save it for that. Avoid it for deeper thought.

How to tell you’ve got it right

You shouldn’t worry about this too much, the benefit will be felt by everyone once you make the change. That said, some good practical measurements are:

If these measures aren’t improving, it’s time to look at where the interruptions are coming from. If they are coming from other teams, you could consider including the high-contact ones into AsyncGo as well, then work together on creating focus time together. In most companies there are just a few sources of interruptions that, when dealt with, reduce the total interruptions dramatically.

A note on monitoring throughput and productivity

A common question from managers working with remote teams for the first time is how to know if your team members are really working, or how to tell if they are taking the opportunity of being away from the office to avoid work.

The reality is that most people increase rather than decrease the amount of work done when moving to remote, since the lines between personal and work life can become blurred. As a manager you’ll be better off spending your time helping your team establish these boundaries in order to avoid burn out and ensure everyone is well rested and at their best.

That said, of course occasionally you will have performance issues with someone. Although it may be tempting in this case to want to track the hours they are spending logged in and active, that’s at best only a secondary, poor version of what you should actually be measuring: the outcomes they deliver. This is complex enough that it requires engagement between the manager and employee who needs help, and isn’t something that a metric here would help. If you’re interested in this topic you can read our blog post on how to think about productivity for remote teams

Because of this, we don’t plan to have metrics in AsyncGo about individual performance. Instead, we will add metrics that speak to overall team activity and collaboration. You can expect to see these in an upcoming release, in the meantime we’d love your feedback on what you’re looking for.