Planview LeanKit helped us find ourselves and quickly became the centre of our transformation towards Agile.
June 24, 2020
Planview LeanKit helped us find ourselves and quickly became the centre of our transformation towards Agile.
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Planview LeanKit
Over the last two years, we kanbanised a lot of our business processes with Planview LeanKit. Our first and to date most successful implementation was in Service Operations. But since then, we started to use Planview LeanKit virtually everywhere, from Sales and Consulting over Project Management - both as meta and project specific boards - up to top-level management meeting organization.
So far, most tries to use Planview LeanKit as a way to realize potential in a business process were a success, independent of department. In all use cases it helps to visualize work where our other tools merely list and obfuscate data and To-Dos. It also supported our transformation towards Agile Management.
So far, most tries to use Planview LeanKit as a way to realize potential in a business process were a success, independent of department. In all use cases it helps to visualize work where our other tools merely list and obfuscate data and To-Dos. It also supported our transformation towards Agile Management.
- Planview LeanKit is particularly good in visualizing a process and the work that is in it. While the column structure seems simple, it still manages to capture the essence of our work and in a way de-abstracts it.
- The multiple ways of customizing boards, lanes, cards and reports mean Planview LeanKit can be made fit to any process.
- With descriptions and comments it is a great tool to facilitate project work and collaboration in a comprehensive manner.
- The reporting offers many ways to keep track of the current state and development potential of a board and its process.
- The Planview LeanKit support is particularly fast to respond, answers (and asks) very knowledgeable and like-able.
- Over the last two years I saw Planview LeanKit develop a lot of great features that were really helpful. The product constantly evolves.
- Planview LeanKit currently can't or should not be used as a central spot for data and collaboration. Particularly attachments are not well-handled.
- The portable side of Planview LeanKit is really lacking.
- We would appreciate some options to group or stack cards.
- ROI for Planview LeanKit was easily achievable with just a month of setting up.
- We could rapidly cut down on unnecessary work in all fields.
- We can easily monitor current the health and input and adjust our capacities as necessary.
- Value throughput in innovation management has grown.
Originally, we had evaluated two other tools next to Planview LeanKit: Kanbantool and Kanbanflow. The latter was a close contestant for productive use, as it was also very customizable and a joy to work with and look at. It also had lower user fees and a mobile integration.
In the end, we picked Planview LeanKit because of several reasons:
Aesthetics: The look was much more clean and professional.
Reporting: It was obvious from the start that we could use Planview LeanKit as a tool for improvement.
API: We needed to integrate the Kanban into our central systems and Planview LeanKit API was (and still is) a way to do it.
Card Headers: This sounds like a simple thing, but the headers above the titles fit our work perfectly and looked perfect, which helped the decision.
In the end, we picked Planview LeanKit because of several reasons:
Aesthetics: The look was much more clean and professional.
Reporting: It was obvious from the start that we could use Planview LeanKit as a tool for improvement.
API: We needed to integrate the Kanban into our central systems and Planview LeanKit API was (and still is) a way to do it.
Card Headers: This sounds like a simple thing, but the headers above the titles fit our work perfectly and looked perfect, which helped the decision.