Kanban Tool is a visual project management application based on Kanban that helps companies visualize workflow, track project progress, analyze and improve business processes. Some key features include: time tracking and time reports, real-time collaboration and Kaban analytics.
$6
per month per user
Perdoo
Score 6.0 out of 10
N/A
Perdoo aligns employees with a company's strategy by focusing teams on the OKRs & KPIs that matter most to the organization.
$0
per month
Weekdone
Score 9.9 out of 10
N/A
Weekdone is software built around the best practices of the OKR goal-setting methodology and with an aim to speed up teams’ OKR learning curve, by providing high-quality educational materials and team-tailored OKR coaching throughout the implementation process. Weekdone is headquartered in Tartu, Estonia.
Perdoo was much more focused on the core OKR process than Weekdone, and our users vastly preferred it during trial tests. Google Sheets is flexible enough to support almost any workflow, which is its biggest strength, but also its biggest weakness - we wanted a tool that is a …
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.
Perdoo would be a great tool for companies that have been through a couple of OKR cycles and have developed a somewhat mature process. It then becomes a very helpful platform to streamline all steps, from design, review, up to post-mortem. It's also a great tool for companies who want to focus on the OKR process, but are not too interested in mixing it up with other frameworks, and other features, like performance reviews, etc. For us, this focus on the core of OKR is a big plus, as it drives simplicity and makes adoption easier.
OKR roadmap: I like how clearly this lays out the connections between the different levels of OKRs (team, company, long term etc)
OKR Webinar: they have a great OKR 101 type webinar that we made all our leaders go through, even those who had worked with OKRs before, to ensure that we were all on the same page. Perdoo is very intentional and thoughtful about the terms they use.
Initiatives: I really like that Perdoo goes down to the initial level, not just OKR. Initiatives are the projects/tasks that roll up under each KR to actually get to the result.
slack updates: I like seeing the notifications come through when colleagues update something in Perdoo. fun to see progress!
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.
User setup and management and team/department creation is not a trivial effort. Requires some deliberate planning.
The deadlines for plans don't connect to the due dates for tasks in systems of record. That can get confusing when Asana says a task is due next week but Weekdone still has a due date of tomorrow.
I'd love to see more contextual support for sections like employee feedback. Maybe a sentence or two suggesting feedback based on the report's weekly entry. If a person had three Problems and only one Progress, Weekdone could suggest some corrective action to make it easier for the management to mitigate problems before they get ugly.
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
We have a lunch and learn session with Weekdone next week so they can share their tips and tricks for making the most out of the platform. Since we have been using the platform for a while already, this will be helpful so we can ensure we are making the most of the tool.
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.
I've used Lattice and I liked their OKR UI a lot, it was simple and easy to use but (at least when I used it) lacked some of the functionality that we found in Perdoo. My team got a bit frustrated with LatticeAlly was robust and had a lot of good features, we just ended up going with Perdoo because they were comparable and we loved the OKR webinar.
Weekdone started as a pilot within a single team so we didn't have a formal evaluation and selection process. When the pilot was over, we had developed a skill and affinity for the tool with no clear objections, so no other tools were considered. Our process for regular evaluation of incumbent technology at renewal time asks us to consider the cost to value ratio and user adoption/satisfaction. I don't anticipate there being any reason to consider alternatives, other than the long term viability of small software companies.
Using Weekdone has helped us meet our quarterly business objectives by tracking each employee's progress.
We have been able to shift resources based on the progress tracked in Weekdone. If we find that a particular project is taking too long or costing too much, we are able to evaluate as needed. We were not able to see this as easily without Weekdone.
