Flowdock vs. Kanban Tool

Flowdock is well suited for small teams and to environments that doesn't need too much reliability. I think it has some management problems that can make your life difficult if you have to manage a big amount of users. If you want just a tool communication with basic features (without using any integration or robust features) it can be suitable for you. You should try Flowdock using its free version for a small team and compare with others similar products. Flowdock delivers team chat and collaboration features, but is not necessarily the best product. Maybe some usability problems that disturb me won't be so relevant to you.

Incentivized

Kanban is well suited for a fast-paced working environment for larger teams who want continuous communication with users. Kanban is good for rapid development and daily meetings for updates and statuses. Kanban is less suited for smaller teams or groups who don't require collaboration and constant communication with involved users. Kanban is time-consuming and it takes additional effort outside of your regular work to maintain and manage the tool.

Incentivized

• Mobile app experience
• Software integrations
• Notifications

• It provides a good basic overview of where tasks are on a timeline (particularly helpful for a pull-based approach).
• It provides a good collaborative space to have multiple folks commenting on multiple tasks.
• It does a good job of managing very basic visual elements of an agile development cycle.

Incentivized

• One thing a little bit annoying is that a lot of links to others Flowdock sections (preferences, external services, etc) will open a new window/tab. Each click may take you to a new window and you can get lost easily.
• There isn't a quick access list to members of your organization to start a private chat. I took a while to find how to do that. The interface and usability could be better.
• There isn't an app for Windows Phone.
• Sometimes you try to load some conversation and it doesn't show anything. It is not frequently but happens sometimes.

Incentivized

• Kanban does not show the task or story clearly. You have to open the project separately to view the details of the project.
• Kanban gives a higher level project management view but it lacks customization and personal settings features.
• I would like to see Kanban provide mobile access to their tool, data, and board. This would be very useful for all companies and provide an increase in efficiency and productivity.

Incentivized

I go with the flow because I'm a newer employee and Flowdock works as advertised. If it were my decision to choose a team communciator for the organization, I'd recommend we go with Slack for its robust features and ever-changing/evolving software integrations. Slack is the outright innovator in the space and will continue to hold that role for some time.

We are more likely than not to renew our use of Kanban. Even with its limits, it still is a good product that fulfills our needs.

Incentivized

The integration with Teams is well suited. This works wonderful for my
company. Our team can easily prioritize tasks based on their importance.
It help our team identify and reduce inefficiencies in workflow. With
great visibility in data our team can make informed decisions. Ensuring
clear accountability and responsibility of team members

This is the best tool I had a chance to work with- since I started to use it I saved a lot of time and I made my work go smoothly.

Slack is a similar software.

Private chat or channels are well implemented in both softwares and both are also very easy to setup.

Besides of some usability problemas I think Flowdock is still better than Slack in this user experience and design.

The second point is the price. Flowdock is half price of Slack ($3/month). If you are a student or a non-profit organization, you are able to get some special license.

Incentivized

We've only tried JIRA Agile and KanbanFlow before. Kanban Tool was the one that our team actually liked and enjoyed working with. Also - it's been much easier to get started with and to understand than some of the other two (JIRA in particular). Although JIRA has many more features that we would have possibly used, the user feedback on it was so poor we were afraid that the negativity would create time wasted and less "job satisfaction" amongst the team.

• Our company uses it by default.
• I enjoy the ability to communicate outside of text messages...keeps the conversation on in it's own bucket.

• Better communication and organization of ongoing projects.
• We are a very small team, with many areas to work on. Having everything in one system gives us a lot of visibility.
• Greatly reduced costs from using other tools that were much more expensive.