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
Planview IdeaPlace
Score 8.5 out of 10
Enterprise companies (1,001+ employees)
Planview IdeaPlace offers an integrated, configurable “idea-to-impact” innovation management solution to capture, evaluate, and prioritize ideas and includes: Unified Innovation Ecosystem: Unifies innovation activity into a single value delivery system keeping an organization, processes, objectives, and customers aligned. Democratized Ideation: Captures and synthesizes ideas from everyone, whether a top-down challenge or proposed by a user. …
N/A
Pricing
Aha! Roadmaps
Planview IdeaPlace
Editions & Modules
Premium
$59
per month per user
Enterprise
$99
per month workspace owner or contributor
Enterprise+
$149
per month workspace owner or contributor
No answers on this topic
Offerings
Pricing Offerings
Aha! Roadmaps
Planview IdeaPlace
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
Startup pack available for early stage companies.
—
More Pricing Information
Community Pulse
Aha! Roadmaps
Planview IdeaPlace
Considered Both Products
Aha! Roadmaps
Verified User
Anonymous
Chose Aha! Roadmaps
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.
Planview IdeaPlace (IP) stacked up very well against our old product, for example Planview IdeaPlace features and integrations with Microsoft O365 products was major attraction. Our leadership also has a simplification agenda, so the reuse of Planview IdeaPlace for this …
Many idea management platforms have a large block of similar features. Where Spigit stands apart from a technology perspective is Pairwise and Predictions. They also have new features coming that could be game changers for the industry. Their thought leadership sets them …
Spigit is a much more user friendly site than any of the SharePoint products we've tried. Our SharePoint initiatives have failed in the past and I believe it had to do with the look and feel of the site as well as the lack of easy-to-use functionality. Spigit provides a first …
Director of Advanced Product Planning - Consumer Electronics
Chose Planview IdeaPlace
Spigit's reputation scheme and excellent pricing were the primary reasons we went with them in 2010. They also seemed eager to improve the product and meet customers' needs.
Because Spigit is used by several companies around the world, because Spigit is in the cloud, we don't need technology infrastructure for access. It is fast and scalable.
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.
If you have a community with more than 100 active users, and you're looking for ideas around operational improvements that can be acted on in a 6-12 month window, Spigit will work great, and it's one of the best options out there. If you're trying to customize the platform much, you should plan on paying Spigit's service group to do that for you, because it's not easy to do yourself. If you're looking for ideas that will take more than about a year to implement, Spigit is as good as anyone else because that's a really tough thing to do in an innovation community!
Acknowledges and supports the culture around the problem and market it is trying to serve. Just using the platform won't solve our problem, we need a cultural shift and Spigit has helped support that process.
Customer service - just overall amazing service. Responses are very quickly turned around, they've gone the extra mile many, many times. They are also very open to platform improvements and take feedback very seriously.
As the system administrator, I feel their platform incorporates a great balance of templates, out-of-the-box formatting, etc., and customizable content. In a nutshell, we are able to do what we want but we don't have to spend forever to do it. We can use what they have or we can add in our own design.
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.
If you have the time and resources there really isn't anything you can't get Aha! to do for you in regards to managing workflow and releases. The Prioritization features are top of its class, the dashboards are getting better and better every day and the team all seem to really enjoy using it to manage their workloads.
This rating was given because, Planview is an establish platform used within the organisation for number of years, therefore is a well known platform by the wider business community. Reusing Planview was ease due to user familiarity with the platform, so use of Planview IdeaPlace was logical and reduce the learning curve for users.
When we signed up for Aha!, we were assigned an Aha! team members to help us with training/questions. The meeting was set weekly, and it exponentially helped with our familiarity with Aha! Support is beneficial and has a lot of experience working with product teams.
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.
Planview IdeaPlace (IP) stacked up very well against our old product, for example Planview IdeaPlace features and integrations with Microsoft O365 products was major attraction. Our leadership also has a simplification agenda, so the reuse of Planview IdeaPlace for this capability, tick all the right boxes and help use achieved a key CIO objective.
I've seen ideas that could have come through existing channels but may have faced layers of barriers before getting to the right decision makers bypass all of that bureaucracy and get the level of support needed to proceed. In one case, the value of just one of those ideas created a 27x ROI over the annual expense of running the software and the supporting team. In other words, that one idea justifies the existence of the program for 2 1/2 more decades if there are no other wins.
Because the program can literally engage every employee, it tends to be the most visible and tangible innovation asset for the masses. Along side (and connected with) other innovation capabilities like internal incubators, R&D labs, design teams, lean programs, etc., it tends to be the tool that delivers on a strategy of total employee engagement for enterprise wide innovation. Employee perception of innovation has improved significantly since the inception of this program.
The software can be used in other ways beyond innovation ideation to drive corporate values, employee engagement, and employee feedback and insights. In nearly every deployment where I have been involved, we have found ways beyond ideation to engage crowds to generate other value for the business. In each case, this was engagement that could not have been delivered in any other way except for a crowd-sourcing technology like Spigit.