Best practices for managing product platforms

Coming soon: We are introducing a fresh new look for record drawer and details pages on September 30, 2020. This article describes the current experience. Preview the upcoming improvements in your account now so you can get familiar with the new way of working in Aha!

  • Switch to the new experience using a toggle in the More options button in the drawer of each record.

  • The toggle is unique to each user — so you can opt in and out as often as you like.

  • We also updated the application font in the new experience for improved text legibility.

Many organizations with multiple products will build those products upon a single platform or set of shared components. As individual products need new common features, work will be done on the platform first and then the various go-to-market products can leverage that new functionality as needed. We can use the workspace hierarchy in Aha! to create product workspaces that are separate, but linked.

Click any of the following links to skip ahead:

Key questions to answer

If you can answer "yes" to these questions, your product is likely a platform product:

  • Does your product provide generic capability that, once available, is leveraged in other product roadmaps in your company?

  • Do you independently manage this backlog of capabilities?

For example, let's say you are adding new mapping functionality to your product. Since several products will use the mapping functionality, you should build the core mapping functionality on the platform and then leverage it with each of the component products. Make enhancements on the platform, and each individual team can implement them into their respective products.


Configure the products

It is important to view features in Aha! as the unique work being done for each individual product. With capability or technology platforms, there are generally two separate features that need to be tracked in Aha! — one for the platform enhancement, and a second for incorporating that new capability into the go-to-market product.

In order to organize and track these individual features, you will first need to create a platform product workspace plus the go-to-market product workspaces that are built on the platform.

Support - Best practices for managing product platforms - inline image


Manage features and dependencies

You'll need to be able to track the work that is planned for the platform so that your individual product teams can make plans for adding the new capabilities to their products.

Add a feature to the platform product workspace to represent the enhancement made to the platform.

Support - Best practices for managing product platforms - inline image

Add features for each of the go-to-market product workspaces that plan to implement the new capabilities and create a dependency between the platform feature and the related product features.

Support - Best practices for managing product platforms - inline image


Share the roadmaps

It is likely that you'll need to be able to track and report the dependencies across the platform product workspace and go-to-market product workspaces. You can visualize the dependencies in a timeline format using the Release → Gantt view. Select the relevant workspaces and releases using the Workspace name and Release name filters and expand the releases and phases to display the dependencies.

Support - Best practices for managing product platforms - inline image

You can also create reports that include feature dependency information using the Record links column or visualize dependency relationships using the interactive dependency map.


Strategic roadmaps

    The worldʼs #1 roadmap software

    Not ready? Join a demo
    © 2020 Aha! Labs Inc.All rights reserved