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).
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
Type: Text
Domain: Product
Definition
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.
Formula
Container — field-array of product items (name, classification, ARR contribution, investment thesis, lifecycle stage). No aggregate calculation; the surface makes each material product line individually visible and classifiable at the board level.Why it matters
Forces explicit, per-product classification — boards offer better strategic guidance when every material product line is named with its game (growth / cash / option-value / sunset) rather than buried in a single narrative. Surfaces whether the company has a real portfolio or a list of products it happens to ship.
How to interpret
Read alongside the product.portfolio_strategy narrative and product.top_product_arr_concentration — heavy ARR concentration in one item without an explicit diversification thesis on the others is a strategic risk the board should name. A portfolio with every item classified as a "growth engine" is a wishlist; expect at least some cash cows and explicit sunset candidates in a maturing company.
Related KPIs
product.portfolio_strategyproduct.top_product_arr_concentrationproduct.offensive_roadmap_pctproduct.defensive_roadmap_pctsales.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 stage | Priority |
|---|---|
| Series A | Recommended |
| Series B | Recommended |
| Series C+ | Recommended |
| Public | Recommended |
Suggested for stages: Series A, Series B, Series C+, Public.
Default owning functions
- Product
Machine-readable
- This KPI as JSON:
/api/ontology/product/portfolio.json - All Product KPIs:
/api/ontology/product.json - Full catalog:
/api/ontology/index.json
Growth & Differentiation %
Percentage of the planned roadmap (typically next 1–2 quarters) allocated to offensive bets — net-new capabilities, market expansion, differentiation moats, new monetization. The "what proportion of the plan is about winning" view. Common pitfall: counting "improvements to existing features" as offensive when the change is really table-stakes parity work. Boards should expect a McKinsey-style horizon framing (Horizon 1 = core, Horizon 2 = adjacent, Horizon 3 = transformational) or an equivalent classification, and apply it consistently. Per the original McKinsey "Three Horizons" framing (Baghai/Coley/White, "The Alchemy of Growth", 1999), a healthy portfolio funds all three — over-indexing on any one is a strategic risk. — Product KPI, I'mBoard-authored (editorial tier).
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).