What is the challenge? |
Some stakeholders might have questions about our Aha roadmaps (e.g. a quarterly pivot table view) and it's overwhelming to click on each record to be able to view descriptions, more details, etc |
|---|---|
What is the impact? |
If reviewers are able to use the AI assistant, they can have a way to "communicate" with the roadmap without having to ping PMs all the time |
Describe your idea |
Allocate AI credits to reviewers |
Reviewers aren't in Aha! all the time and the AI would improve adoption and reduce the Q&A and effort from the product team to help them in creating reports or finding information. Remember, Aha! provides a significant amount of capability, especially if you have multiple solutions, and the AI utilization should be a choice that the PM/admins can take, allowing for credits to be utilized by specific folks, to mitigate this friction point. Leave it to the customer to decide how best to invest their credits vs making that decision for them.
It is very limiting not to enable AI for non-contributor or owners. While Aha!'s product team may be looking to increase paid licenses by forcing companies to buy if they want to use the assistant in our case for example the opposite effect is happening. Product is leveraging other products to perform discovery and refinement and whereby raising the question on if Aha is the right tool. Further, organizations are already acquiring credits based on their plans which creates a throttle or another funding opportunity if the tool is fully leveraged.