I'mBoardDocs
Board OntologyProduct

Product Portfolio Strategy

Narrative overview of the product portfolio — which products are growth engines, which are cash cows, which are innovation bets, and which are candidates for sunset. The CEO/CPO articulation of "what game each product line is playing." Frequently structured along the McKinsey Three Horizons framing or the classic BCG growth-share matrix (stars / cash cows / question marks / dogs — per Bruce Henderson's "The Product Portfolio", 1970). Common pitfall: the portfolio narrative does not name horizons, life-cycle stages, or sunset candidates — a portfolio described entirely as "growth engines" is not a portfolio strategy, it is a wishlist. Boards should push for explicit classification of every material product. — Product KPI, I'mBoard-authored (editorial tier).

I'mBoard-authored (editorial tier)

No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.

Rogue ID: product.portfolio_strategy Type: Text Domain: Product

Definition

Narrative overview of the product portfolio — which products are growth engines, which are cash cows, which are innovation bets, and which are candidates for sunset. The CEO/CPO articulation of "what game each product line is playing." Frequently structured along the McKinsey Three Horizons framing or the classic BCG growth-share matrix (stars / cash cows / question marks / dogs — per Bruce Henderson's "The Product Portfolio", 1970). Common pitfall: the portfolio narrative does not name horizons, life-cycle stages, or sunset candidates — a portfolio described entirely as "growth engines" is not a portfolio strategy, it is a wishlist. Boards should push for explicit classification of every material product.

Formula

Narrative — no calculation. Should cover (1) classification of each material product (e.g. Horizon 1/2/3 or BCG matrix quadrant), (2) ARR concentration by product, (3) investment thesis per product, (4) any sunset candidates and timing, (5) cross-product synergies or cannibalization risks.

Why it matters

Forces explicit articulation of the multi-product story — boards offer better strategic guidance when they understand which product is being optimized for growth vs cash vs option-value. Reveals whether the company has a portfolio strategy or just a list of products it happens to ship.

How to interpret

A portfolio narrative that has not evolved across multiple quarterly updates while the market has shifted is a flag — the strategy is either uncontested or unmonitored. A narrative that pivots every update is also a flag — typically signals over-reactivity. Compare against top_product_arr_concentration — heavy concentration without an explicit portfolio-diversification thesis is a strategic risk the board should name.

  • product.top_product_arr_concentration
  • product.offensive_roadmap_pct
  • product.defensive_roadmap_pct
  • product.key_initiatives_status
  • sales.arr

Source

I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.

Stage relevance

Company stagePriority
Series ARecommended
Series BRecommended
Series C+Recommended
PublicRecommended

Suggested for stages: Series A, Series B, Series C+, Public.

Default owning functions

  • Product

Machine-readable

Product Portfolio

Container handle for the field-array of products in the portfolio — each entry tracks the product name, its portfolio classification (e.g. growth engine / cash cow / innovation bet / sunset candidate, or Horizon 1/2/3), ARR contribution, investment thesis, and lifecycle stage. The structured, per-product companion to the `product.portfolio_strategy` narrative: the narrative tells the story, this gallery makes each product line individually visible and trackable. Renders via the CollapsibleFormItemCardGallery widget (the reused gallery pattern shared with sales pipeline deals and HR key hires / openings). Common pitfall: a portfolio gallery that lists products without an explicit classification or investment thesis per item — that is an inventory, not a portfolio. — Product KPI, I'mBoard-authored (editorial tier).

Churn from Quality Issues

Percentage of customer churn (logo or ARR, define explicitly) where the primary stated reason is product or quality problems — bugs, performance, missing core functionality, reliability incidents. Distinguishes product-driven churn from pricing-driven, competitor-driven, or use-case-fit-driven churn. Common pitfall: relying on free-text exit-survey reasons. Customers commonly cite "price" when the underlying issue was reliability or missing features — boards should require both the customer-stated reason and the CSM/Account-Manager-assigned root cause, and watch the gap. The Pendo "Product-Led Growth Benchmark" and similar product-analytics publishers cover product-driven churn qualitatively, not as published numeric ranges. — Product KPI, I'mBoard-authored (editorial tier).

On this page