Kanban Tool vs. Quip

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

Well, they are suited. 1. We use it as an effective way of collaboration between teams. 2. Can be used as an online spreadsheet. 3. It helps in accessing the data by multiple teams hassle-free. 4. Can customize the action, like editing or locking the spreadsheet to the other users based on the business need. Less Suited/inappropriate: 1. The UI is very much outdated. 2. The number of rows to be added to the spreadsheet has limitations. & We have to create a new Quip every now & then once the row limits are reached. 3. Can't do a detailed analysis like pivots tables etc. 4. Other functions like sort & filter options in Quip are not so user-friendly, unlike other spreadsheets out there in the market.

Incentivized

• 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

• Our experience with Quip has been nothing short of astounding; I love everything about this collaboration tool.
• I love that it is cross-platform and works so well on mobile devices; it makes it unhindered to make progress on to-dos, take notes, export spreadsheets and documents, and have all my information organized within one environment.
• I also love that it notifies me when someone has done something in shared documents and the incredible ease of linking documents in chats.
• Quip's user interface is friendly and comfortably navigable; it feels right.

• 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

• When using Quip Desktop, it can be slow to update with content from other users
• I think it would be cool to have a PDF proofing system integrated into Quip. Once copy has gone to design, we are basically done using Quip - I'd like to bring that all together within Quip
• Multi -select and group export of documents would be helpful

Incentivized

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

Again, this is a strong tool for software teams using Agile that are distributed across multiple geographies. It can be good for co-located teams too, but there are better platforms on the market like JIRA that provide a more built-out story.

Incentivized

It is the best collaboration tool in my company. Through it, the organization has achieved better connectivity and efficiency in its communication. Primarily, the docs feature of this software is the most utilized in the company. Slowly, dash-boarding and project management features have also been utilized. Generally, it is the best tool, very easy and fairly streamlined

Incentivized

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.

I have never used Quip's support. To be fair, we hired someone who used to work for Quip before working at our company, and he implemented it and pushed it with the team. He was very biased toward the product, and yes it was better than Google Drive, but by how much?

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.

Google Drive is an obvious choice for a collaboration suite, but it still has this old-fashioned Windows 95 feel to it, with the standard file system hierarchy and spread-sheet like lists of files. Quip has a fresh take on the user interface, and the comments and discussion on a given file or line within a file seems more integrated and seamless, rather than a bunch of boxes out in the margin away from where you're actually reading and working. Having everything just to the left of a list or paragraph makes it easier to focus and maintain context while you're working or discussing a certain point.

Incentivized

• 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.

• Quip allowed collaboration and communication between Salesforce team and the rest of IT as well as business users.
• Quip allowed collaboration on documents that was very interactive and helpful to the creation process.
• Quip frustrated us because we had so many documents that we already had but they did not work well inside of Quip.

Incentivized