How Aha! helps us make better client and partner connections
We had a problem
Our product team answers to a lot of people. We were bombarded with emails and IMs, but had no way to manage or review requests. We also didn't have a way of quantifying how influential a request was, or how often one was being made. This led to a lot of repetition and wasted time.
Despite several teams depending on us, our work felt silo-ed in the past. We didn't have an easy way to share our roadmap with people outside of our team. This always led to lots of questions, as outside teams felt disconnected from our work.
Aha! as a solution
The Ideas Portal, repository, and workflow are great. We use the Jira integration to push features as stories to Jira. Then, our development team picks them up from there. It's great, because our roadmap updates in real time! And the Ideas Portal allows everyone to submit their thoughts on how releases might be improved. We use Aha! to prioritize the best ideas and encourage constant dialogue. This means that even when ideas are not implemented, this choice is shown within Aha! so that questions can be asked and answered.
Aha! gives me the ability to manage and measure feature requests and ideas in a meaningful way. I’m able to build roadmaps, and connect large efforts back to the source or original requests. It helps me make connections with the customer, employee, or partner who originally asked.
Aha! has also helped enhance our strategic goals. The product team tracks, scores, and shares these goals with all who have a stake in each release. We share the end result through Aha! notebooks, a feature that is also a huge help — it lets us share roadmaps that are tailored to their appropriate audiences. That takes a lot of work off of our plate.
Life is good
Aha! gives me the ability to manage and measure feature requests and ideas in a meaningful way. It helps me make connections with the customer, employee, or partner who originally asked. You can’t compare communication now to what it was pre-Aha! Now that we have visual roadmaps to keep all teams on track, there’s a lot less confusion and even fewer headaches.
Thanks to Aha! I’m able to build brilliant roadmaps, and connect large efforts back to the source or original requests.
The two-way Jira integration is a lifesaver. As soon as there’s a link between Aha! and Jira, any updates in one system are reflected in the other. This means that we can send features to Jira in bulk; map features to different issues; enable capacity planning; and create several integrations right within Aha! This has improved workflow and morale between our product and engineering teams.