ABBYY Mobile Web Capture vs. Slack

Slack is ideal for Scrum and agile teams that need continuous communication during sprint planning, daily stand-ups, backlog refinement, testing, and retrospectives. Slack is well-suited for maintaining team knowledge through searchable conversations and dedicated channels, where experienced team members help onboard new QA analysts.

• Customer issues: Threads feature allows us to group a particular issue in a single thread and discuss within that thread. I can use the thread link to embed in JIRA ticket for tracking progress in JIRA (which is our details engineering tracking system).
• Ability to add folder to Slack channel helps keep important information, documents easily accessible. e.g., we use this to keep a "ramp up" folder that can be used by any new joiner.
• Global search is effective when I forget which group a particular message was in.

• Would love a better integration with GitHub. For example, notifications when your PR is updated, when review is requested, @-mention in comments, etc.
• Improved "Later" tab, for example the ability to create to-do lists or making the "Later" tab into a more powerful to-do list (annotate items with notes)
• More powerful integrations, e.g. Google Calendar could render a calendar view within Slack, rather than sending the daily schedule

Incentivized

To be more transparent, I give 10 because Slack serves our collaboration needs. It provide us a good platform for team communication relaying important update within the company, it has even mobile app where you can install in your phone to monitor any updates within that team that needs your immediate attention and intervention.

Incentivized

Slack has good usability. Devs that are not familiar with the platform are able to jump into conversations and start sharing code and links within just minutes. Non developers are also able to understand the layout such as the Project Managers that are keeping the projects on track. We have not seen any tickets where employees are having trouble understanding Slack.

Incentivized

Yes, the app works 24/7. I don't even recall having any period that we could not use since the implementation. Even the maintenance periods are barely noticeable and our work is not impacted by it when it happens.

Incentivized

Slack is a soft app, we don't have many issues with it. I recall one or two people complaining about something during our usage period, but I didn't have a bad experience. When the app is slow, usually the problem is with my computer or my internet. The app works just fine.

Incentivized

Whenever I've had to troubleshoot an issue with Slack (which, to be honest, has not happened very often), their online documentation has been easy to locate, easy to understand, and effective in resolving my issue. Slack's ever-growing popularity also means that there's a large community of practice out there that can be depended upon.

Incentivized

I was not part of the implementation team, but I recall being 100% happy and excited to learn and use a new tool. I'm still am to be honest.

Incentivized

I like Slack better than ClickUp, because I would spend 30-60 minutes a day updating my ClickUp tasks. The way ClickUp was used was very micromanaging. I billed by the hour, so I was willing to put in the time to alert the boss what tasks I was working on.

One of my jobs used Hive - I mostly just ran it in the background in case anyone messaged me. I did not use it often.

Incentivized

• Slack has been incredibly helpful in connecting various tech apps and ecosystems, creating a more streamlined and responsive process.
• Slack has made it significantly easier to communicate with our team members across multiple time zones, creating a more engaging environment for our all-remote team.

Incentivized