Craft, from the company of the same name in Tel Aviv, is presented by the vendor as a better way for Product Managers to manage and plan their products in agile environment.
N/A
productboard
Score 6.6 out of 10
N/A
productboard, from the company of the same name in San Francisco, is a product management system designed to help product managers understand what users need, prioritize what to build, and rally everyone around a roadmap.
Craft is one of the more complex tools focused on digital products. Besides Craft, I've testes ProductPlan and Aha! and they are all great tools, but I think Craft is the one that merges powerful features with some ease to use. But I think that many users would benefit more …
Craft has a completely unique tool set that has functionality that really is not duplicated any where else in the industry. It cannot really be compared to any other tool I have had experience with, especially with the larger cloud infrastructure that Invision has built around …
I have previously used Aha another product road mapping/ insights driven software.
Aha had great features for the userbase of my previous products. They were allowed to create their own suggestions for the products and other users could then like or dislike the suggestion. …
Productboard is more feature-rich. It has very intuitive to use and can be connected to various applications. Showcasing your roadmap is very easy and collaboration is very easy as well.
Productboard has great UX features where you can see the roadmap in multiple ways with …
Productboard has a modern interface with a great user experience that will help you get onboard really fast especially if you are looking for one place to handle customer insights that are coming from different places and be able to score and report under value vs effort …
Productboard is leaner, easier to use, and cleaner than Aha! I switched from Aha! to productboard and did not regret the decision. Aha! may be better suited to larger operations or teams, but productboard is perfect for smaller teams and solo product managers.
Craft.io is well suited for medium to large digital product teams that have some experience with the tools and features of the agile and lean models. Users that are new to those methodologies can have some difficulties understanding the platform. It is less appropriate for small projects too. It's a great tool but I think you can shape a project management tool to your needs in theses cases and it will work better.
The best feature of productboard is organized features, it has a very simple structure and can be read and understood by anyone. If your roadmap is very dynamic and the executive team needs to be on top of it, productboard is the best application out there. But if you have a small product and features do not change very often, then maybe you can look at other alternatives since productboard is expensive.
'Sync' usually works flawlessly in syncing my artboards to Invision. Once you set up the plugin, I can easily forget about tinkering with any of the settings - it just 'works'.
'Library' is pretty great for generating a style guide from my design doc. Clicking one button makes magic happen, and creates a super succinct document for me to share between teammates and other teams.
'Data' also works wonders when trying to approximate 'real' data into a static design. It turns the painful job of having to fill in designs with 'real-world' data a piece of cake. It helps me validate rough designs using an actual approximation of real content.
Craft has a completely unique tool set that has functionality that really is not duplicated any where else in the industry. It cannot really be compared to any other tool I have had experience with, especially with the larger cloud infrastructure that Invision has built around their plugin and their platform.
I have previously used Aha another product road mapping/ insights driven software. Aha had great features for the userbase of my previous products. They were allowed to create their own suggestions for the products and other users could then like or dislike the suggestion. This created a real reflection on need for product enhancements. productboard handles this slightly differently. Each user creates their own suggestions and doesn't necessarily have visibility on other users suggestions. The product/ R&D team can then tag suggestions together into the same overall suggestion. This requires more input from product/R&D with productboard. I would however, suggest that productboard is better than Aha. Aha is great for an external user point of view; however, there may be case for users to not have visibility on wider user requirements. productboard keeps more of this element hidden and would perhaps stir up less negative correlation to seeing a system requirement/suggest having had a lot of traffic and no action, compared to a more closed system that would individually update each user on the enhancement progress.
