Product portfolio management: 5 lessons from Roman Pichler to keep strategic alignment as you scale

In theory, expanding your product portfolio should bring more opportunities, more leverage, and more revenue. In practice, this is not always achieved: Each team defends its own roadmap, cross-sell becomes an afterthought, and "strategic alignment" becomes a slide nobody remembers.

That tension was the starting point for airfocus's latest webinar, "From product management to portfolio strategy: How to keep strategic alignment as your team scales." Jamie Lyon, Chief Product and Strategy Officer at Lucid Software, sat down with Roman Pichler, one of the most respected voices in product leadership, to talk about what product portfolio management actually looks like when a company manages more than one product.

Missed the live session? Watch the recording here.

Here are five of our favorite takeaways from their conversation.

1. A portfolio strategy should answer three questions

Pichler defines product portfolio strategy simply: “It describes how we want to maximize the value of a group of products.”

A great example of a product portfolio strategy is Microsoft 365, which bundles Word, PowerPoint, Excel, and more.

To make that concrete, he uses a framework he built called the Portfolio Vision Board. Beneath an overarching vision, Pichler says an effective portfolio management strategy needs to answer three questions:

1. Which markets or market segments should be addressed? 

2. What value should the portfolio create for the users and customers, and the business? 

3. What makes the portfolio stand out against competing offerings?

He's also careful to note that what a strategy leaves out matters just as much as what it includes: "Strategy is not only about saying what we do but equally about saying what we don't do."

Without that clarity, Pichler warns, companies end up with "a loose collection of products that are siloed," and individual teams start pulling in different directions.

Use this Product Vision Board, originally created by product management expert Roman Pichler, to help you describe your product vision and strategy. Capture key details about your target group, user needs, product features, and business goals all in one place.

2. Portfolio strategy sits between business strategy and product strategy

One of the clearest frameworks Pichler shared was the Strategy Stack. This framework is helpful to “think about how to connect the portfolio strategy to other key strategies in the organization.” 

Here’s how he maps this:

• Top layer: business strategy, owned by the CEO and executive leadership team

• Middle layer: portfolio strategy

• Bottom layer: product strategy, implemented through an outcome-based roadmap, and eventually a backlog

The relationship between the layers is directional: "Higher-level strategies guide lower-level ones in this model." Product managers can and should own strategic decisions for their own products, Pichler says, but "whatever they decide has to align with or fulfill the overarching portfolio strategy."

In other words, the role of portfolio strategy is to connect individual product strategies–for instance, Word, PowerPoint, and Excel–to the company's broader business strategy. As Pichler puts it, "It sits in that space in between."

3. Portfolio ownership should default to your most senior product leader

Who should actually own a product portfolio management strategy? Pichler's default answer: "The person who represents the product management function at an executive level, that's the default portfolio manager.” This person can be a chief product officer, a VP of product management, or a director of product management, depending on the titles each company uses.

That doesn't mean the decisions happen in isolation. Pichler recommends forming a portfolio team that includes the product managers for each product, so the people closest to the work help shape the strategy that will guide them. The payoff, he says, is better portfolio decisions and alignment: Product managers "not only understand the portfolio strategy" this way, but are "more likely to actually implement it and follow it because they have helped shape it."

Only once a portfolio grows too large, or a leader is stretched across too many portfolios, Pichler suggests bringing in dedicated, full-time portfolio managers.

4. The right level of detail depends on how cohesive your product portfolio is

Watch "From product management to portfolio strategy: How to keep strategic alignment as your team scales" with Roman Pichler on demand.

Pichler gets this question recurrently: How detailed should a portfolio strategy actually be? Unlike product strategy, he says, there's no generic answer because it depends on the balance between two forces: 

• Alignment versus autonomy

• Integration versus speed

Give product teams too much freedom, and you risk ending up with “products that are incompatible and just don't work well together, and it's very hard to bundle or cross-sell them.”

At the opposite extreme, if you demand too much shared strategy, roadmap, and objectives, then "it's going to take anybody forever to get anything done."

Pichler’s rule of thumb is to calibrate against cohesion. For example:

• A tightly bundled suite like Microsoft 365 can support a stronger, more prescriptive portfolio strategy.

• A looser collection of products like Adobe Creative Cloud usually needs a lighter touch.

5. Having portfolio visibility doesn’t mean you have a portfolio strategy

airfocus Portfolio management rolls up roadmaps, OKRs, and dependencies across every team and product line, in one live view. Ask anything, dig anywhere, visualize at any level. AI flags risks, surfaces opportunities, and keeps you on course, at scale.

"A key pattern I see is that there is no portfolio strategy," Pichler says. And in most cases, this stems from the assumption that portfolio visibility guarantees a cohesive portfolio strategy.

It's possible to have portfolio dashboards for real-time visibility into how every team is tracking, and still have no actual portfolio strategy connecting them. 

His fix isn't complicated, just consistently skipped: Articulate the strategy clearly, and revisit it. Rather than treating strategy as a one-time exercise for the next several years, Roman recommends reviewing and adapting portfolio strategy "every three months as a rule of thumb," as well as the subsequent portfolio-level KPIs, not just individual product metrics, to see whether the strategy is still meeting customer needs. 

The bigger picture

When asked later in the session how to integrate an acquired product into an existing portfolio without disrupting the acquired team's momentum, Pichler pointed back to the same idea that had run through the whole conversation: Decisions like that are "impossible to make in isolation." They need a portfolio strategy already in place to make sense of them.

That's really the throughline of the session: Product portfolio management isn't a document you write once. It's an ongoing discipline for deciding what a group of products should do together that no single product could do alone, and it only works when the people building those products help shape it. 

Watch "From product management to portfolio strategy: How to keep strategic alignment as your team scales" with Roman Pichler on demand.

Portfolio management with airfocus

Keeping a portfolio strategy connected to what your product teams are actually shipping gets harder as you scale. airfocus's portfolio management software gives product leaders real-time visibility across multiple teams and products, so strategy and execution stay in sync as your org gets more complex.