What to consider when deciding between a Roadmap vs. Product Portfolio (PPM) Tool

Roadmap tools connect strategies (WHY) and product features (WHAT) before passing them to execution. However, creating a product and bringing it to market takes more than prioritization.

If you have to juggle competing goals, align multiple stakeholders, manage dependencies, track progress, and/or adjust product roadmaps from time to time, you need more than just a Roadmap Tool.

You need a Product Portfolio Management (PPM) tool – A PPM tool covers the full workflow of building products.

There are 3 types of activities involved in building products.

  1. Managing product – defines the WHY and WHAT
  2. Functional focus – defines the HOW
  3. Managing program – plans and tracks WHO, WHEN, and WHAT-IF

First, some definitions:

  • HOW – as in how the same product feature could be implemented in multiple ways, by the same engineer or a different team altogether.
  • WHO – as in the resources needed – for frontend, or backend, or data engineering, or a different team.
  • WHEN – as in the sequence and schedule, considering the HOW, WHO, and Dependencies.
  • WHAT-IF – as in the multiple product feature scenarios that can be put together in a roadmap, during both the initial plan and subsequent changes.

All 3 types of activities are essential in connecting outcomes and strategies with product and resources. This is where the multi-dimensional, responsive product portfolio management framework comes in.

Product Portfolio Management = (Product Management + Program Management) * N Team

A Product Portfolio Management (“PPM”) tool covers the WHY, WHAT, HOW, WHEN, WHO, and WHAT-IF in creating product. Enabling the collaboration between product, engineering, program, and other functions involved in bringing products to market.

There are 3 types of tools today attempting to address the needs of product portfolio management.

  1. Roadmap tools, e.g. Aha or productboard
  2. Embedded “PPM”, e.g. plugins like Big picture, Structure or Jira Roadmap
  3. Complete PPM tools, e.g. dragonboat or Jira Align

#1 – The Roadmap Tools – covering the WHY and WHAT

Roadmap tools, such as Aha and productboard, focus on product vision, strategy, idea capture, and prioritization. They work well for a top-down one-directional workflow, passing prioritized ideas from product to engineering. However, there are a few key gaps when it comes to PPM support.

  • Roadmap tools do not support iterative collaborations between product and engineering, or between product teams themselves. Each product manager often works out of their siloed workspace with their own strategy and focus.
  • Roadmap tools do not support portfolio allocation, essential in prioritizing across competing goals. For example – how do you prioritize a Feature for Retention against a Feature for New Account Acquisition?
  • Roadmap tools do not support portfolio tracking, as in various rollups and against plans. Planning a timeline and tracking progress are inherently program management activities, where roadmap tools do not focus.
  • Roadmap tools do not support multiple portfolio dimensions. While strategy is a key dimension of a portfolio, business goals (e.g. OKRs) and categories are additional dimensions that should be considered for product focus and allocation.
  • Roadmap tools are not program management tools. Hence they do not support resource and dependency planning, especially around different teams and skills which are often blockers in building products that require more than 1 scrum team.
  • Roadmap tools do not provide portfolio-level reporting and communication. Gathering progress, comparing to plan, and aggregating various updates to various stakeholders that each needs different sets of data in different dimensions can be a time-consumingactivitiy.

#2 – The embedded “PPM” – covering the HOW and WHEN

Embedded “PPM” solutions such as Structure or Jira Advanced Roadmap, are plug-ins that are embedded in the execution tool. They provide good roll-up reports for a predefined hierarchy of the portfolio.

However, they rely on the data that already resides in the execution tool. Hence they are not natively built for the fuzziness of the product ideation/ portfolio discovery phase.

The upstream of the portfolio management, such as defining portfolio dimensions like goals, strategies, categories, and their respective allocation, as well as scoring or other prioritization activities, are not part of the workflow of these “embedded PPM” tools.

Often, the access to execution tools is not company-wide. Or different functions/ teams use different tools for their day-to-day work. This creates additional collaboration, visibility, and contextual challenges for the “embedded PPM” tools.

#3 Complete PPM tool – covering the WHY, WHAT, WHO, WHEN, WHAT-IF

Complete PPM tools offer top-down, bottoms up and horizontal interactions and workflows to bring winning product features (or initiatives) to market faster.

The top-down workflow includes defining, aligning, and allocating to strategic goals, themes, and other portfolio dimensions, along with idea capture and prioritization. Prioritization needs to be within the framework of allocation.

If you don’t have allocation, you can’t execute strategies.

The horizontal workflow refers to the collaboration across product teams and between product and tech leads. This is often seen during quarterly planning. Most products are not built by 1 team or used by 1 type of user. Horizontal collaboration identifies and addresses major dependencies or resource bottlenecks to prevent “Agile Madness”.

agile madness

The Bottoms up workflow refers to the tracking, reporting, and adjusting of product roadmaps based on progress vs plans. A PPM tool is often integrated with team tools, e.g. Jira or Asana, for team execution. The execution progress rolls up to various levels of the portfolio and is shared with portfolio participants for context and visibility. The delta in plan vs. predicted timeline enables tracking and measuring of outcome to start the next portfolio iteration. 

At any given time, in the same portfolio, there could be a strategic roadmap, a customer roadmap, a quarterly roadmap, and even an engineering roadmap.

A roadmap is a snapshot of a point in time in one dimension of a portfolio.

A portfolio is evolving and multi-dimensional. Every product manager needs to take a portfolio approach in building products while collaborating with each other, engineering, go-to-market teams, customers, and external parties.

dragonboat is a responsive PPM solution supporting a responsive portfolio workflow before and after scrum. dragonboat starts with aligning and allocating to strategic goals/ OKRs and themes, supporting idea capture and product prioritization, and enabling the collaborative planning between product and engineering teams to design the best portfolio roadmap. 

* * *

Sign up a free trial, book a demo, or sign up a Responsive PPM intro class with optional certification.

Becky Flint

Becky Flint

Becky is a product and tech executive based in the Silicon Valley. She has built and scaled product and engineering teams globally for both startups and Fortune 500 companies. Currently Becky is the founder and CEO of dragonboat with a mission to empower responsive leaders and their teams to build better product fasters. Prior to founding dragonboat, Becky has held executive roles at Feedzai, Bigcommerce, Tinyprints/ Shutterfly, and PayPal.

Like this post? Please share it

Share on facebook
Share on twitter
Share on linkedin
Share on email