Aha! Roadmaps is used to set strategy, prioritize features, and share visual plans. It includes Aha! Ideas Essentials for crowdsourcing feedback. For an integrated product development approach, Aha! Roadmaps and Aha! Develop can be used together. The software is available with a 30-day trial.
$59
per month per user
Avaza
Score 8.1 out of 10
Mid-Size Companies (51-1,000 employees)
Avaza is a software suite targeted for all business sizes. It includes modules for project management and collaboration, resource scheduling, team chat, time tracking, expense management, quoting and invoicing. Depending on their business needs, companies can use as many, or as few, of the modules as they need. Avaza offers reporting functionality, and the project management module is designed with both list view and Kanban style task management, so users can choose…
UserVoice collects and organizes feedback from multiple sources to provide a clear, actionable view of user feedback for product teams. With a customizable feedback portal, in-app widget, and direct integrations with your email client, CRM or support tool, it’s easy for your customers and internal team members to share feedback at anytime. The UserVoice platform allows you to manage all this feedback in a single view, analyze your data to make product decisions based on customer…
ProductBoard was used in the organization when I arrived, but after assessing ProductBoard, I felt it was too lightweight for our ambitious product goals. It's also critical, especially in a startup, that we focus our limited capacity on the work that matters most. Aha! far and …
Compared to some other types of software we've tested or use in other areas of the company Aha! has a better user interface, has more customization ability and grows with the company and the work we're doing.
I initially tried to do this using Notion but without an API to integrate it is all very manually driven when any updates are made in ADO, I would have to hunt it out.
I've worked with other homemade tools and Jira, Confluence as well. They are more tailored for the developers' community than Product and Program managers.
In terms of outright features, a lot of roadmapping tools have the same feature set. We chose Aha! based on look-and-feel, the easy learning curve, and the reviews it has. Between collaboration, milestone tracking, comment threads, and content importing and exporting, we had …
Jira is centered around product development, whereas Aha! is centered around product management and road-mapping. Both allow for planning and tracking, but Aha! is more user-friendly.
Aha has more features continually being released as a Product Management tool. In comparison to ProductPlan, Aha has more complex features and increased support for getting organizations up and running on the platform. They also provide migration tools to determine what data …
Jira has a lot more bells and whistles. It was easier to see how different teams across the (larger) company were prioritizing their own work against all of the incoming requests, and to see how those ideas mapped across the current and next springs. However, it was necessary …
In terms of product road-mapping, Aha! beats its competitors upfront. Aha! is one of the best tool to visualize your product strategy. However, JIRA in terms of PRDs, gives a complete environment in its own. Aha! is for product managers only. If Tech needs to be involved, JIRA …
Aha! definitely does more than either Pivotal Tracker or JIRA. We still use JIRA to track tasks by department, but for strategy everything is in Aha! and aligns all of our other project/task trackers including integrating with Salesforce so we're able to work within every …
We selected Aha over the other options as our specific goal and need was to align as a Product Management team across all our lines of business. While other products did well, the customized abilities of Aha, price points, and Atlassian integration tools made it a clear choice.
Aha! is a better fit for the specific type of strategic planning that I do. The other tools are more intended for other grains of planning and/or execution.
Aha! is completely different compared to the other products I've evaluated. I would compare Aha! to Atlassian/Jira. It's great for agile teams to do weekly sprints and breakdown large features/product upgrades into individual tasks.
Aha! is slightly more complex and nuanced than Trello, which is nice. Trello feels like a digital sticky note system sometimes. It's more straightforward in UI and collaboration than Workfront or Workamajig without all the extra (seemingly unnecessary) features, like scoping …
Wizeline is an up-and-comer in this space. At the time we considered them, the solution was not robust enough to manage a large backlog or multiple products with a Jira integration. They are adding features rapidly, though, and every release is very robust.
Avaza's time tracking capabilities are much more detailed than Upwork's. Upwork focuses on simplicity, using a simple on/off button and a spot for taking notes about each project, but Avaza gives you more to work with, allowing you to add detailed notes and specify tasks.
I've used Trello before, but Avaza has way more features and is more applicable for cross-team collaboration. We selected Avaza for it's ability to not only project manage, but also for invoicing, expenses and it's ability to track time. We've gotten more accurate with estimate …
This is miles ahead of ActiveCollab. It has more features, the interface is easier to use and the invoicing is easier to use. Across the board better. We migrated from ActiveCollab, but that was just essentially a Fancier Wunderlist. If you just need one project and a few tasks …
I like the ease of integration into web and mobile apps for UserVoice. It's also a comprehensive bug reporting, user feedback, and knowledge base tool.
Aha! is the all around product management tool. You need something once you build out a product management role and grow beyond a small scrum team with one or two products. JIRA, Pivotal, and project management tools don't cut it for aligning [engineering] with product initiatives once the backlog starts to scale.
On the other hand, there are several unfinished features that my peers all admit to having to work around: Capacity Planning, Salesforce Integration, Roadmap Display Flexibility, User Feedback, etc. This year has been all about reporting in terms of feature releases. As Aha! grows, they will fill in these other areas, so stay tuned.
There are teams who work hard, and there are those who work smart. Avaza helps you be the latter--it's is a great tool for any team collaborating on several projects, especially multiple projects with a lot of simultaneously moving parts. It has just about everything you need - from team schedules to timesheets, down to the task and sub-task monitoring. The best part for me is that we can switch from List View to Kanban to Gantt charts!
UserVoice is well suited if you field a lot of feedback and ideas from clients. If you are a company who is building your software based on customer feedback, it is important to have a place to store and organize this feedback. I think UserVoice is ideal for a company whose feedback comes into one team but needs to be passed along to another (i.e Support to Product). UserVoice is also great for companies that are growing and growing their product quickly.
Notes - There's not a great place to leave lots of notes or instructions, almost like a Confluence page. Although not required, it would be nice to have this built in.
Learning curve - As with most new tools, there's a bit of a learning curve to become proficient.
I think Aha! works really in general, it offers a very comprehensive and well-structured platform that supports strategic product management at scale. Although there is a learning curve for new users and a few areas to be improved. Overall, it is highly usable for experienced product teams who need a robust roadmap tool.
We've always had excellent support whenever we need help from the company or need questions answered regarding the setup and installation of the product. Tickets are answered in a timely fashion and there's minimal back and forth to get issues resolved, which are rare.
Have clear goals and owners established before you start using any tool like this. Very important to get accounts and rights setup so that there's no lag time in customer response once things go live. Make sure IT is involved if you plan to use the Single-Sign On (SSO) or any of the access control tools.
productboard was used in the organization when I arrived, but after assessing productboard, I felt it was too lightweight for our ambitious product goals. It's also critical, especially in a startup, that we focus our limited capacity on the work that matters most. Aha! far and away had superior capabilities in defining strategy directly in the product and associating all of our work to the strategy. Aha! is a serious product management tool and I found productboard to be more of a simple backlog management tool.
I've used Trello before, but Avaza has way more features and is more applicable for cross-team collaboration. We selected Avaza for it's ability to not only project manage, but also for invoicing, expenses and it's ability to track time. We've gotten more accurate with estimate project hours, and therefore create more accurate proposals
I like the ease of integration into web and mobile apps for UserVoice. It's also a comprehensive bug reporting, user feedback, and knowledge base tool.