The World's #1 Product Roadmap Software

Would you recommend this product?
1 Review5.0/5
We have been humbled by the feedback and growth of Aha! -- we now serve over 100,000 users. I wanted to take a moment and provide a quick update since it's been awhile since Aha! was hunted and we have made quite a few significant additions. Here are a few of them: - Reports to analyze everything product management without using spreadsheets - Portfolio management tools (release dependencies, release templates, and the ability to clone an entire release) - Idea management integrated with your roadmap to capture feedback from employees and customers - Visual roadmaps for IT, Manufacturing, Marketing, and Consulting teams (with the ability to customize the terminology to match what your team uses everyday.) - A Kanban board for agile or scrum teams integrated with your strategy and goals - Product notes (wiki-like docs) for unstructured information and planning notes - Activity streams and a new search engine for auditing changes - 23 integrations including: JIRA, Visual Studio TFS, Pivotal Tracker, Rally, Salesforce, Trello, and Slack If you are not already an Aha! user, you can sign up for free 30-day trial here: http://www.aha.io/product/signup
Upvote (14)Share
I have yet to find a great project management tool, especially those that accurately and effectively communicate roadmaps without ridiculous overhead. Anyone have experience using this?
@rrhoover I bet the overhead is just what comes with the territory with certain companies and problems. With how the corporate companies I've worked at operated, this doesn't seem too bloated. Personally I just need me some trello and maybe elegantt with that.
I've used Aha! to test out product management features and overall I was impressed. Product management is complex work, so there really is no simple, one page solution in my opinion. I mean, think of how many tools are typically used to enable product management: email, documents, file sharing, collaboration sites, ticketing systems, and potentially other specialized tools. A lot of separate, "simple" tools can be put together, but there's a jot of disjointed parts and overhead involved in managing all those "simple" tools. I think Aha does a good job at putting together a guided framework by which product and development can work together on. The product is flexible, though it still may not be perfect for every team's style. I think there is some overhead to learning the product and adapting to it. You can't spend 5 minutes and become an expert in it. You really have to dig in and test it at a deep level. The payout would be in the longer term from avoiding the complication involved in more traditional methods.
My main problem is that tools that do a good job of managing the nuts and bolts of the project seldom do a good job of managing the bigger picture roadmap of the product. There are tons of project management tools, but very few of the latter, which Aha seems to aiming for. Haven't used it, but it looks interesting. It does seem like every startup has an Excel sheet with their product roadmap on it and it seems that Aha aims to improve on this. Will have to give it a try.
@shedd did you end up liking it?
We've been using Aha! for maybe 8 to 12 months. We really like the top level planning it allows us to put down on paper. Many of the things Aha! is great at modeling are the type of things that live solely in soft conversations or in executives and the leaderships' minds. By writing this stuff out, and going down from level to level we are able to refine vision to objectives to goals and then to releases. It can get as fine grained as you need it. I specifically find it useful for release planning - getting a large scale of view of our release schedule is super valuable and makes it easier to report on to stakeholders and to the team.
@tannerhearne You mentioned release planning but are devs able to provide a timescale for certain features? It's something we don't use at the moment but I'm starting to find the need...
@stevenjmesser We work together to identify the timelines for releases. It helps to be able to see things in front of us, as well as behind. There's the big annual view that shows all releases on there and it makes it really easy to see all that we've shipped. Ultimately, I rely on my engineers to help build timelines, because they are the best equipped to know the difficulty, about of unknown pieces, etc. that need to go into timelining a release.