Asana vs Slack: What are the differences?
What is Asana? The easiest way for teams to track their work. Asana is the easiest way for teams to track their work. From tasks and projects to conversations and dashboards, Asana enables teams to move work from start to finish--and get results. Available at asana.com and on iOS & Android.
What is Slack? Bring all your communication together in one place. Imagine all your team communication in one place, instantly searchable, available wherever you go. That’s Slack. All your messages. All your files. And everything from Twitter, Dropbox, Google Docs, Asana, Trello, GitHub and dozens of other services. All together.
Asana and Slack are primarily classified as "Project Management" and "Group Chat & Notifications" tools respectively.
Some of the features offered by Asana are:
- Updated in real-time
- Multiple workspaces
- People views
On the other hand, Slack provides the following key features:
- Create open channels for the projects, groups and topics that the whole team shares.
- Search with context
- Autocomplete makes mentioning your teammates quick and painless.
"Super fast task creation", "Flexible project management" and "Followers and commenting on tasks" are the key factors why developers consider Asana; whereas "Easy to integrate with", "Excellent interface on multiple platforms" and "Free" are the primary reasons why Slack is favored.
Pinterest, Square, and Codecademy are some of the popular companies that use Slack, whereas Asana is used by Uber Technologies, Pinterest, and Quora. Slack has a broader approval, being mentioned in 4744 company stacks & 3361 developers stacks; compared to Asana, which is listed in 662 company stacks and 328 developer stacks.
We are a small financial planning firm with remote workers. Trying to fix inefficiencies with technology and not people. We need to know where clients are in the pipeline/process (i.e., have we submitted applications and transfer forms, have we entered the costs basis of investments in the system, have we run their financial plans, where are we in the planning process, etc.) If a client calls and we have to research a question, who is handling it.
Karen, you can accomplish that with any of the three tools (I'm currently using all three). It depends on the user experience and the capabilities you're looking for. Here's a high-level rundown:Trello
- stands out for being simple, visually oriented drag-and-drop
- of the three, it's more minimalist but still flexible
- the more advanced features are free & paid add ons from Trello & other developers
- best when you need something quick and simple, and more visual
- great for more robust project management
- you can manage tasks in different views including lists, kanban board similar to trello, and gantt chart
- best when you need more control over the tasks and how your process is set up
- intends to be a replacement for many different tools, including asana & trello
- loaded with features, can do pretty much everything that trello & asana do
- highly customizable but it may take some time go set it up the way you want it
- the myriad of options could get confusing, but they provide a lot of templates (including a CRM template) and support tools to get you going faster
Ultimately you choice comes down to how much detail & control you want over your process (dates, categories, client information etc.) and how you want your team to work with the tool (simple drag & drop vs. structured lists). One idea is to start with Trello since it's the simplest, and migrate to one of the others if you outgrow it.
Hope that helps! If you have any follow-up questions please let us know!
I'm comparing Aha!, Trello and Asana. We are looking for it as a Product Management Team. Jira handles all our development and storyboard etc. This is for Product Management for Roadmaps, Backlogs, future stories, etc. Cost is a factor, as well. Does anyone have a comparison chart of Pros and Cons? Thank you.
I just switched to ClickUp for my development agency - I am the product team, and I relay everything there betwixt designers, devs, and clients.
Clickup = Jira + Confluence but better - more ways to slice and dice your data & documents, make custom views, mind map relationships, and track people's work, plan goals... I even use it to manage project finances and household to-dos.
They have a very comprehensive free tier that never expires, and on top of that they're extremely generous with trials of their paid features, have more-than-fair pricing, and top-notch customer support.
From a StackShare Community member: “We’re about to start a chat group for our open source project (over 5K stars on GitHub) so we can let our community collaborate more closely. The obvious choice would be Slack (k8s and a ton of major projects use it), but we’ve seen Gitter (webpack uses it) for a lot of open source projects, Discord (Vue.js moved to them), and as of late I’m seeing Spectrum more and more often. Does anyone have experience with these or other alternatives? Is it even worth assessing all these options, or should we just go with Slack? Some things that are important to us: free, all the regular integrations (GitHub, Heroku, etc), mobile & desktop apps, and open source is of course a plus."
We use Discord to tracking some action and errors (logs / alerting / assertion). it's free and simple to use with mobile application et notifications
Our Discord Server is our n°1 community stop; we gather feedback from our users from here, discuss about new features, announce new releases, and so on.
We even use it for internal meetings and calls !
Since now Jira is offering pretty wide free plans, it can compete with asana at small teams. And they have a significant advantage especially if you're working in agile methodology. Confluence is also a big advantage, and also comes with a free plan, so it's a pretty big thing. But we had also talked about asana and used to work with it before a lot, but we chose to go with Jira, and it's pretty good for now.
I still use slack, although I prefer discord. It can be intergrated with discord to work with clients who only want to use slack or even any other platform. API integrations are possible over at Discord.
The awful crappy dependency hell of a thing they call an API. Everything sucks. Slack is one of the worst messaging apps I have ever seen. It's incredibly slow and laggy.
Let me rant about everything I hate about slack. Even though I use it as an integration for another platform and will recommend it even though it's horrible as a whole. They are unstoppable towards companies who don't have people technically savvy enough to transition any other software.
It's so bad I am considering making my own mix of discord and slack.
Finding conversations you know you've had - but search is (Still) terrible, and if it was a direct message with a group of people, you have to remember exactly which group of people it was with
Search...absolutely awful. If they could figure out search, Slack would be unstoppable. it got better with ctrl f in conversations, but still isn't there
Badly arranged Chinese buffet of people, conversations, channels, files and links.. and search sucks too.. Break up the people into a separate window so I can have a buddy list ala Communicator or Skype. Give me some freaking organization and curation to the conversations - otherwise it's 1000 person cocktail party with everyone playing drinking games.
AGAIN! Search sucks. Spellcheck is still broken. Too many notifications.
Interface ist inconsistent between devices.
No way to forbid slack to touch my microphone settings (seriously, dont autoadjust my microphone level, it never works and i hate you so much for it)
Still no good screen sharing on linux.
The buggy red dot. Usually shift-esc will clear it (in itself a pain), but now even that hack won't help. The red dot number keep climbing even though I've read everything and used shift-esc.
I miss some features but I wish slack had a little more ability to organize, group channels, and navigate a little better.
user groups need work... If I search for a group, open it, I want to be able to not just see who is online from that group, but also a message button. I'm sick of searching that person, which closes user groups and if that person is actually AFK, I have to search for that group AGAIN and do it again... What a waste of time compared to other tools which are supporting this.
Date stamps needs to be more visible, or give us option in settings to make it more/less visible
Scrolling needs to be improved, I don't want random jumps there. Especially when time and date stamps are so tiny so it takes a while to get oriented again.
I used to really hate slack, but that's mostly because I have to use user groups a lot, most of the time I'm using slack it's to find someone who belongs to some group and message him... and that stuff is still pretty bad, even tho it was changed a bit...
oh and microphone settings... that hurts bad...
It's slow and laggy if you ever used a native program and got used to responsive user interfaces.
You can't remove someone from a call if they join by mistake
(or, to put it another way, if you start a channel call, you should be able to moderate it and remove those from it who are to meant to be there)
Video calls (using the "native" app on macOS) consume so much resources that the whole machine becomes unresponsive. A video call with the same number of people in a true native app is not a problem. So it's not the inherent bandwidth and processing power required. I mostly like Slack but for remote teams this is a problem.
You really want to know what I hate about SLACK...
The inability for the app to BLOCK DIRECT MESSAGING when outside work hours... I work for global company and I constantly get messaged after midnight by morons who think i am up at 3am
It has this Bullcrap Send Anyway function on messages which totally overrides my Do Not Disturb settings if said moron is blind of what time they are sending their damn message... I worked oncall before so the slightest him of my cell at night will wake me up...
Another annoyance on messaging... Idiots who message direct over chatting in the team channel for stuff that should be seen by the whole team working a ticket .... Or classic hey I opened a ticket not two minutes ago ' can someone look at this ticket pleaee' blah blah blah blah ... People who I don't know sending a random 'HI' and no other info about wtfh they are reaching out to me about ...
If SLACK wants to add a function to fix this I want control to block direct messages from anyone truly outside my direct team and line of management that is not a member of a group that can engage onCalls for issues ... I am so sick and tired of this I literally have to uninstall the app everyday to ensure no one bothers me after I am off work and then redownload it before the start of the next day... It's pathetic!
As it is the communication tool chosen for the course, our team will be using Slack to monitor the course announcements from our instructor as well as to communicate with the instructor and industry partners. The tool for communicating within the team will be Microsoft Teams. Microsoft Teams enables the team to share documents and edit them synchronously(Google Drive is not an option due to one team member's location). Since it also provides a group chat feature, we chose to use it as our communication tool to avoid using too many softwares.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Asana?
What is Slack?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Today the impossible happened, our beloved Slack crashed sending chaos into offices around the globe. “Wow, how am I now going to vote for the flavour of our new office candy???”, I thought. But even though it might not have felt like it, everything else around us was still working: the world was still spinning, South Korea was winning over Germany at the World Cup, and today’s quotas and goals had to be met. In these situations, people most often turn towards traditional messaging tools like messenger, WhatsApp or email and hope for the best — that Slack will be back up soon. However, these temporary remedies are not without their complications: undelivered messages that you thought were read, lost documents, mental breakdowns, wasted time, etc.… In general, for us it creates a problematic gap in our office chat history.
But what if I told you that these crashes could potentially never occur again?
Yes, this is real life, and it’s exactly what mesh technology is about so we are going to explain it. In this scenario, if Slack ran with mesh networks, its users would not have been affected by its current technology’s single point of failure, which in this case was the crash of the server.
Lol okay, how is this possible bc this is real life???
Mesh networks might not sound familiar to everyone so let’s compare it with other well-known networking topologies. Consider a Local Area Network (LAN), where devices are connected to a central access point (imagine it like a star with the central access point in the middle and the devices located at the ends). Be it LAN or wifi, the idea is the same, so when I send a message on Slack, it first arrives at the Slack server (the central access point) and from there it is sent to the recipient.
In mesh networks, devices are directly connected to each other. They form a local network using existing connectivity technologies such as Bluetooth or Wi-Fi as “connectors”. Devices can act as “routers” and forward messages and files to others, enabling the content to hop between them until it reaches a destination. This eliminates the need for a central entity.
Let’s apply this concept to today’s crisis. If slack ran on top of mesh networks, their consumers would still be able to communicate and send files even though they were not connected to the crashed server. Once it was up and running again, all their group conversations which would have taken place during the outrage would be uploaded back to Slack’s server once they were back online.
Honestly, it’s that simple. To Slack, it would not only be convenient for its customers in situations like these (because we would never have Slack crashes), it would also considerably reduce their own infrastructure costs and prevent them from having moments that they might find embarrassing.
So slack, if you see that mesh networks could potentially help you, come talk to us.
I have been using asana for a couple years and I have nothing but good things to say... except that it doesn't have a unified inbox and task list across you Organization/Workspaces :(
Amazingly easy task/project management Meetings are great, Type your meeting agenda, notes & next actions directly into asana while the meetig is taking place. Integrates with Dropbox and Google Drive.
This is the easiest project management tool I have ever used and it is very easy to get other people to use it too. I haven't has as much success implementing a habit within an organization as with asana. The biggest problem with Project management systems is that organization members don't use them enough, not with asana. Mobile apps, speedy web app, and integrations galore make it easy for people to stay up to date.
Slack is gorgeous and runs on multiple platforms - that's benefit #1. You can easily talk on your iMac then switch to your Android device on the fly.
The one thing I don't really like about it is how it handles multiple organization accounts.
I am a software consultant so I typically work with multiple teams over the months and it's odd to 'log into the right account'. It's not intuitive at all.
I would like there to be a way for users to easily pick a 'Persona' and not accidentally post to the wrong company.
Slack filled a very complicated role and did it elegantly.
Its very well designed and easy to use. Adding integrations can be complicated but their documentation with images makes it very easy.
Also I contacted support and get a relevant answer quickly!
All this on the free plan, you better bet we will be upgrading soon.
Internal Communications made easy
I first heard about Slack from my friend Matt (shout out to Final!). He was helping me out with some Rails issues so we started using Slack and I liked it. Specifically, the chat interaction. But also all the integrations. I wasn’t thinking of it as a tool to end all tools at first, just a chat tool with some cool integrations. Then I created a Slack account for StackShare, and that’s when things got real.
Sentry got easier to stay on top of, Heroku was easier to see activity from, discussions were more fluid, and the mobile app was killer. Most of the tools I use either don’t have a mobile app or have shitty ones. Slack is like a replacement for all the mobile apps my tools should have.
I don’t find Slack particularly useful for focused discussions, so I doubt it will replace email anytime soon for us. Things like product discussions/debates are best via email. It forces you to think before you type and have a clear back and forth with someone.
Small gripe: I wish Slack would disable email notifications by default, I still haven’t figured out how to turn those off.
Slack is an instant messaging and collaboration system It unifies your entire team communications, making your workflow, well, flow a lot better. It is a cloud-based set of proprietary team collaboration tools and services. Slack teams allow communities, groups, or teams to join through a specific URL or invitation sent by a team admin or owner.
Slack is our go-to communication tool and it's slowly replacing emails across all departments of the company. We built our own Slack Bot to help us with simple DevOps stuff; Honeybadger notifies us in real time of errors happening on production in our monitoring channel; CircleCI reports builds status and deployment info as well.
Team comms is essential. The R&D team is distributed over two offices, as well as the chance that people are working from home. Slack provides lots of options of keeping individuals and groups up to date. We also use it to integrate into services such as Github and Sentry.
Slack is a lifesaver, not only for our day to day team communications and it's direct links into our other tools, but for Beta testing as well, with our custom Slack bot in our beta group being an invaluable asset to avoid giving our testers direct JIRA access.
We keep ourselves out of email as often as possible, thanks to Asana. It keeps in the know, helps us manage sprints and hackathons, and helps us be transparent and productive.
I used Asana to manage the tasks, define scope of the project more over to create a learning path that will effect my project.
The central hub where all of our projects live and breath. Without Asana, we would truly be lost.
I use asana for personal projects (to collaborate on event organization) on a weekly basis.