Asana vs Slack vs Email: where team communication belongs, with cards for Asana, Slack, Teams, or Chat, and Email and the Dynamically Done logo

Asana vs Slack vs Email: Where Team Communication Belongs

“I know Brian sent me that link. Where is it?” If you’ve said that out loud, your team has an Asana vs Slack problem.

You know what comes next. You scroll back through your phone. Then it’s old meeting transcripts. After that you search Slack, and then your email, which is hard to search on a good day. And the whole time, that link should have been sitting in the task you were working on.

That hunt is the most frustrating thing I see on small teams. And it almost always happens on teams that are paying for Asana but still running everything through Slack and email. So here’s the short version of Asana vs. Slack (and email, Teams, Google Chat, texts, and calls):

  • Asana is for anything about a specific task, written as a comment on that task.
  • Slack, Teams, or Google Chat is for quick, time-sensitive pings, brainstorming, and the dog, kid, and weekend talk.
  • Email is for people outside your team and anything formal.

The rest of this post walks through each one, how I handle the messy middle (like vendors who will never log into your Asana), and the login routine that keeps it all from piling up. If you’d rather watch, here’s the video. It’s under five minutes.

Asana vs Slack vs Email at a Glance

ToolUse it forExampleWrong place for
AsanaConversations about a specific task@mentioning a teammate on the task with the Drive link they needQuick “are you on the call?” questions
Slack, Teams, or Google ChatQuick, time-sensitive pings, brainstorming, and team chatter“Running five minutes late to the 2:00”Files and details someone needs to finish a task next week
EmailExternal and formal communicationSending a vendor what they need from youInternal back-and-forth about a task your team is working on

What Belongs in Asana?

Anything about a specific piece of work belongs in Asana, as a comment on that task. That gives you one record of the work, the questions people had, and where things stand, all in one place.

I’m going to get specific here, because this is where teams trip. Asana has main tasks and subtasks, and the conversation should roll up to the main task. The person who picks up a subtask later may not have been included in the conversation, because at the time nobody thought they needed to know. When they get to their subtask and need a piece of that information, it’s sitting right there on the main task.

When you write that comment, three habits make it useful:

  1. @mention the person. Use their name and tell them exactly what you need from them.
  2. Link everything they’ll need. The Google Drive file, the doc, whatever you’re trying to send over. Put the link in the task.
  3. Make it doable from My Tasks. The goal is that someone can log into Asana, open My Tasks, and get stuff done without coming back to ask you a question.

The bonus you get for free is task activity. Every Asana task keeps a running history: when it was reassigned, when the due date changed, every comment added. When the conversation lives in the task, that history becomes your one source of truth for that piece of work.

Asana vs Slack: What Belongs in Your Chat Tool?

Quick, very time-sensitive questions and pings belong in your chat tool. That’s true whether your team uses Slack, Microsoft Teams, or Google Chat.

Past that, it depends on your team culture, and I’d let your team decide. For some teams, chat is where brainstorming happens. For a lot of teams, it’s also where you talk about your dogs, your kids, and your weekend. Hopefully you’re having some fun with your coworkers in there!

When Should You Use Email Instead of Asana?

Use email for external or formal communication, which usually means anyone who isn’t in your Asana.

One of my clients asked me, “Well, what happens with our third-party vendor that’s supposed to provide us something for this task?” Their vendors aren’t added into Asana, so that conversation happens in email.

The work still gets tracked in Asana, though. Here’s how I do it:

  1. Add a task like “Send email to vendor.”
  2. Add a follow-up like “Vendor replied,” with more detail if it needs it.

That way I can make sure the vendor hasn’t dropped the ball, even though every message with them lives in my inbox.

How Do You Get Emails Into an Asana Task?

The easiest way is the Asana Chrome extension. If you use Google Chrome, it lets you add context from any website or email in your browser into a specific task, which helps a lot when the vendor conversation above needs to show up where your team can see it.

The Asana Community Forum write-up of the extension’s 2024 update describes a “Create task” shortcut that shows up at the top of emails in Gmail, and says the extension is free on every Asana plan. I walk through it step by step in my Asana Chrome extension video.

My Asana Login Routine: Inbox First, Then My Tasks

Every time I log into Asana, I check my inbox first, and I keep going until that red dot goes away.

My inbox shows me every update since the last time I logged in. In the video, that was a new project summary and a few late tasks. Everything is clickable, so I can open it, see what’s going on, and deal with it right there. Once I’ve read everything and feel up to speed, I archive it. The dot goes away, and then I move to My Tasks and start working from there.

According to Asana’s help center, your inbox has three tabs (Activity, Bookmarks, and Archive), and you can turn any notification into a follow-up task. If you want the full walkthrough, I have a whole video on the Asana inbox.

Why Does Your Whole Team Need the Same Rules?

An Asana vs Slack rule only works when everyone follows it. If half your team comments in Asana and the other half sends the update in Slack, you’re right back to hunting for Brian’s link.

Think of it like a house with a junk drawer in every room. You know the spare key is in one of them. You just have to open every drawer in the house to find it. Picking one place for each kind of message is how you get down to one drawer, with a label on it, that everyone on the team knows to open first.

I know it seems silly to be this particular, and it is a little particular! But the cost of the hunt is real. Asana’s own Anatomy of Work research found that people spend about 60% of their time on “work about work,” which includes things like searching for information and switching between apps, instead of the skilled work they were hired to do. Every round of “where did Brian put that?” lives inside that number.

The goal is that everyone on the team gets their information from the Asana inbox instead of their email inbox, as much as possible.

Who This Isn’t For

This is written for small teams that already use Asana and want it to be the place work lives. If your team doesn’t use a work management tool at all, the split won’t map cleanly. If your company has a formal communication policy for legal or compliance reasons, that policy wins over anything here. And this post doesn’t cover connecting Slack to Asana, which is its own topic.

Asana vs Slack FAQ

Can Asana replace Slack?

For conversations about specific tasks, yes. That’s what Asana comments are for. Most small teams still keep a chat tool for quick, time-sensitive pings and everyday team chatter, and that’s okay.

Should I comment on the subtask or the main task in Asana?

Comment on the main task. The people working on the subtasks can see it there, even if they weren’t part of the original conversation.

Do vendors need to be in our Asana?

Not usually. Keep the vendor conversation in email and track the work in Asana with a task like “Send email to vendor” and a follow-up like “Vendor replied.”

Is the Asana Chrome extension free?

Yes. According to the Asana Community Forum write-up of the 2024 update, it’s free on all Asana plans, and it also works in Microsoft Edge.

What should I check first when I log into Asana?

Your inbox. Clear it until the red dot goes away, then move to My Tasks and work from there.

Start With One Rule

My biggest tip: start with one rule. Conversations about a task go in that task’s comments. Once your team is doing that, the “I know Brian sent me that link” hunt gets a lot shorter, and you can layer in the rest.

If your team pays for Asana and still runs everything through Slack and email, that usually comes down to how it was set up, and that’s the work I do with small teams as a Certified Asana Expert. Learn about working with me on your Asana implementation.

This post may contain affiliate links.