The Aha! data model for product workspaces

Note: This article discusses the Aha! data model for product workspaces. If you want to see the Aha! data model for marketing workspaces, see this article

Product managers and engineers use Aha! to capture and curate ideas that will deliver the greatest business value. Our data model has been built to make this as easy as possible. Start by creating your workspace hierarchy and setting product strategy at each level. Then weave your product vision throughout your roadmapping process by linking releases and features to your strategy.

The Aha! data model does two things: It highlights the key building blocks in Aha! and it explains the relationships between them. The five main objects are product lines, product workspaces, releases, features, and ideas. Strategy can be set at both the product and the product line levels and then linked to releases and features.

Click any of the following links to skip ahead: 


Product lines and product workspaces

Product workspaces can be organized into product lines to create groupings. You can create as many levels as you need. For example, you might have a top-level company name, a product line under it, and then product workspaces under that. Creating logical hierarchy is important if you want to ease navigation, set up more sophisticated user permissions, and create roll-up views on the dashboard of your strategic initiatives.

You can add hierarchy by creating a product line and then selecting which product workspaces belong to it. Or you can select a product workspace and choose which product line it belongs to.


Product strategy

Strategy can be set at the product workspace and product line levels in the hierarchy and then linked to product release and feature work. 

  • Vision: Your product vision should enhance the overall company strategy, your outlook for the product, and where both are headed. A good vision is supported by details of who the customers are, what they need, and your go-to-market plan. It captures the essence of what you aim to achieve, the opportunities you have, and the threats that you face.
  • Goals: Your product goals must have a measurable end result that can be achieved within a fixed time frame. Your objectives should represent the crucial accomplishments needed to make your vision a reality. Goals can be rolled up to higher-level goals as well as linked to initiatives, releases, and features.
  • Initiatives: Initiatives allow you to specify key work that must be completed to achieve your goals. Think of these efforts as high-level projects that should be accomplished within a specified period of time — even if this is over a few months. Initiatives can be rolled up to higher-level initiatives as well as linked to goals, releases, and features.



A release is the date when a company is ready to deliver a new customer experience. This involves supporting every customer interaction point associated with the new experience. Start from the perspective of your customer and prioritize releases that will offer the most value. 



Features fall under releases and define a set of capabilities that are specified through descriptive text, images, and additional meta information. Features can also be further defined through requirements or grouped together into themes or larger enhancements through master features.



Ideas are where you collect and manage all of the potential enhancements to your product. Ideas can be promoted to either a feature or a strategic initiative, depending on the size and scope of the body of work.


Was this article helpful?
26 out of 27 found this helpful