We use Aha! to manage and optimize our product management for development of Enterprise software.

I first used Aha! four or five years ago - and it was good then, but has come a long way. I really like how Aha! brings together the why of product strategy with the how of product management. It enables our team to collaborate, stay informed, share, and stay on track in these areas in ways that are very difficult to do with JIRA alone, or some combination of product specifications and JIRA. It's intuitive and the support is very responsive, knowledgeable and friendly. There is a lot of customization possible, although I have not dipped into that much yet. But it is clear that as the size and scope of our development organization and product line grow that Aha! has everything needed to manage, prioritize & focus our efforts. Integration with Atlassian JIRA is also strong and a good option. We looked at only using Aha! - including for managing our development tickets & sprints - but that is not a fit at this point. Keeping the clutter & detail of all the workstream & ticket management for development separate is a better solution. I definitely recommend Aha as best in class for product management.

The one major improvement that I see is the need for some type of Knowledge Base / Documentation tool set similar to Confluence. Write now, I find that I have to keep meeting notes in separate documents, as these will tend to cover multiple tickets, and have other work to assign tasks and so on. With Confluence + JIRA, you can both document meetings and develop specifications in one place, and then link this to all of the tickets that are related.

We are introducing the product management function accross the business. Therefore introducing the departments and senior management to the functions of Aha has been my priority. The multiple benefits have included, multi person access as a reviewer / viewer. Transparency of the portfolio roadmap, clarity and confirmation of epic and feature details and the development priorities. A prime benefit has been the capabilityof the tech team and CTO to cost up the features and epics in more detail than previously, supporting investment requests.

For my role as Head of Product Management: The strategic view of the product portfolio is all important for the company to see and for me to report. The functions I use most are the strategic and portfolio roadmaps, goals and linked initiatives. I absolutely love the dashboard function, especially for executive resporting. And now use the different workspaces for the different departments who are dependant on the product management scheduling, this is also an added bonus.

I really wish the functions would allow clarity for Strategic objectives, rather than goals and support the framing of dependant team and individual OKR's. I also find it difficult to delete releases and features on the Strategic level workspace. It would benefit the different types of users to have the functionalities that they need and navigate to it easily. From my role as head of to the associate product manager, we have different uses and feature requirements.

Would never recommend.

Cool logo. Good space to house personas and competitor analysis.

In the initial onboarding process I would contact customer support for clarity, seeing as how I've never used such a software. I had one phone call, fairly short. I was later tasked with sole responsibility for the software - evangelizing and coaching others on how to use it. When I reached out to support for more clarity, the reps did EVERY possible not to get on a call with me. They would email me back every other day - directing me to instructional videos - refusing to get on the phone. I needed to integrate with Jira, "Please HELP!!??"- guess what? "We have some videos that can help you. Awful support. As well, not very user friendly, not customizable, and just down right inferior cosmetically.

easy to use and integration with development toolexcellent service and response time

don't have much yet. would prefer lower cost