How to Conduct a Product Portfolio Review: 2026 PM Framework

How to conduct a product portfolio review requires evaluating each product on three dimensions — strategic fit, financial performance, and investment opportunity — and making explicit resource allocation decisions, including the ones that involve stopping or sunsetting work.

Most product orgs review individual products in isolation. They measure a roadmap against its own goals, not against the opportunity cost of the resources it consumes. A portfolio review forces the harder question: given everything we could invest in, is this the right allocation?

This framework works for product orgs managing 2–15 distinct product lines, features as products, or investment bets across a platform.

Why Portfolio Reviews Matter

A product portfolio review is not a status meeting. It is an investment committee meeting. The outputs should be:

Continued investment decisions (with updated resource levels)
Acceleration decisions (products that should receive more resources)
Reduction decisions (products that should receive fewer resources)
Sunset decisions (products that should be wound down)

Without explicit sunset decisions, resource allocation calcifies. Zombie products accumulate — products that no one uses but that require maintenance, documentation, support, and opportunity cost.

According to Lenny Rachitsky's writing on product strategy, the most common portfolio review failure is that it produces a list of "continue" decisions with no acceleration or sunset decisions. A review that ends with everything unchanged is not a review — it is a status check with extra steps.

Step 1: Build the Portfolio Map

H3: List Every Product and Investment Bet

Start by listing everything your org is investing in. Include:

Shipping product lines and features
Platform or infrastructure bets
Exploratory or 0-to-1 initiatives
Maintenance and support load

H3: Assign Resources to Each

For each item, estimate current resource allocation:

Engineering headcount (FTEs or fractional FTEs)
Design and PM bandwidth
Infrastructure cost
Support and maintenance load

Most orgs discover in this step that their actual resource allocation does not match their stated strategy. The product they claim is highest priority is not the product receiving the most engineering investment.

Step 2: Score Each Product on Three Dimensions

H3: Dimension 1 — Strategic Fit (1–5)

Does this product contribute to the company's stated strategic goals? Score it:

5: Core to the strategy — the company's success depends on it
3: Adjacent — contributes to strategy but not central
1: Legacy — no strategic relevance to current priorities

H3: Dimension 2 — Financial Performance (1–5)

For revenue-generating products: ARR contribution, growth rate, gross margin, NRR. For platform/infra investments: cost savings, revenue enabled, or strategic leverage.

5: Growing, profitable, high NRR — clear return on investment
3: Stable, modest growth, acceptable margin
1: Declining, low margin, or high cost relative to revenue

H3: Dimension 3 — Investment Opportunity (1–5)

Given additional resources, how much upside is available?

5: High opportunity — market is large, competition is weak, the product has clear growth levers that resource investment would unlock
3: Moderate opportunity — growth possible but constrained by market or positioning
1: Low opportunity — market is saturated, competition is strong, or growth levers are unclear

According to Shreyas Doshi on Lenny's Podcast, the investment opportunity dimension is the most commonly omitted from portfolio reviews — teams evaluate what a product has done but not what it could do with more resources. This leads to under-investment in high-potential products and over-investment in stable-but-capped ones.

Step 3: Make Explicit Allocation Decisions

H3: The Portfolio Matrix

Plot each product on a 2x2 using Strategic Fit (x-axis) and Investment Opportunity (y-axis):

High Opportunity  |  Exploratory Bets  |  Accelerate
                  |  (consider)        |  (invest more)
------------------|--------------------|------------------
Low Opportunity   |  Sunset Candidates |  Maintain/Reduce
                  |  (wind down)       |  (hold steady)
                  Low Fit              High Fit

H3: Decision Types

Accelerate: High strategic fit + high opportunity. These products should receive more resources, not just maintenance investment. Identify what specific resource increases would unlock growth.

Maintain: High strategic fit + low opportunity. These products are important but capped. Optimize for efficiency — can you reduce engineering cost while maintaining quality?

Explore: Low strategic fit + high opportunity. These are bets on future strategy. Evaluate whether they should be elevated to core strategy or capped as experiments.

Sunset: Low strategic fit + low opportunity. These products should have a wind-down plan. Document the plan, communicate to users, and reclaim resources.

Step 4: Sunset Planning

Sunsetting is the hardest decision in a portfolio review. It is also the most valuable.

H3: Sunset Decision Checklist

[ ] Is there an active user base that depends on this product?
[ ] What is the contractual or regulatory obligation to continue support?
[ ] What is the migration path for current users?
[ ] How long is the wind-down period and what resources does it require?
[ ] What resources does sunsetting free up for reallocation?

According to Gibson Biddle on Lenny's Podcast, sunsetting a product is one of the most strategically courageous decisions a PM org can make — most organizations never do it because it feels like admitting failure, but the resources reclaimed from a sunset typically fund 2-3 high-growth product accelerations.

FAQ

Q: What is a product portfolio review? A: A structured investment committee process where each product in the org's portfolio is evaluated on strategic fit, financial performance, and investment opportunity to make explicit resource allocation, acceleration, and sunset decisions.

Q: How often should you conduct a product portfolio review? A: Annually at minimum, with a lighter mid-year review for major resource reallocation decisions. Quarterly reviews are appropriate for fast-moving orgs or when the market environment is shifting rapidly.

Q: What should a product portfolio review produce? A: Explicit investment decisions across four categories: accelerate (add resources), maintain (hold steady), explore (evaluate strategic fit), and sunset (wind down with migration plan).

Q: How do you decide which products to sunset? A: Products with low strategic fit and low investment opportunity should have sunset plans. Evaluate user dependency, contractual obligations, migration paths, and the resources that reallocation would free up.

Q: What is the most common failure mode in product portfolio reviews? A: Producing a list of continue decisions with no acceleration or sunset decisions — effectively a status check with no allocation changes, which means the review had no impact.