Portfolio

Origin & evolution

The financial metaphor is load-bearing. Cooper, Edgett, and Kleinschmidt made it explicit in Portfolio Management for New Products (1998), arguing that a company should manage its product investments the way an investor manages a financial portfolio. They set out three goals that still anchor the field: maximise the value of the portfolio, achieve the right balance of projects, and keep the portfolio aligned with strategy. The contribution was treating product selection as continuous resource allocation🥧Resource AllocationProgram ManagementAn allocation of team capacityView reference →, not a series of one-off launch decisions.

The balance question got its most durable framing from McKinsey. In The Alchemy of Growth (1999), Baghai, Coley, and White described three horizons: Horizon 1 defends and extends the core business, Horizon 2 builds emerging high-growth ventures, and Horizon 3 seeds options for the long term. The model named a recurring failure: successful firms over-invest in the profitable core and starve the future, so the portfolio quietly ages. A balanced portfolio spreads bets across all three horizons at once.

Both ideas share a premise. A portfolio is not a list of everything in flight; it is a deliberately shaped set, chosen so that value, risk🎲RiskComplianceA risk to the product or businessView reference →, and time-horizon are balanced on purpose. Portfolios also nest: a large organisation runs a portfolio of portfolios, each with its own balance to strike.

How it works in practice

A company holds three products and frames them as a portfolio across the horizons. The analytics tool is Horizon 1, throwing off cash and getting maintenance investment. The collaboration app is Horizon 2, taking the largest share of new headcount to compound its growth. A small AI experiment👾AI ExperimentAI & Machine LearningAn AI-focused experimentView reference → is Horizon 3, funded as a cheap option on a future market.

Run as one portfolio, the picture is honest: roughly 70% of spend defends the core, 20% builds the growth bet, 10% buys the option. When the AI experiment needs🫀NeedUserA user need, pain, desire, or constraintView reference → more money, the cost is visible as a transfer from one horizon to another, not a quiet overrun. The portfolio view turns three separate budgets into a single strategic allocation a leadership team can argue about and adjust.

Portfolio vs. its neighbours

• Product is a single offering inside the portfolio. The portfolio is the balanced set; a product is one member. A product can succeed on its own terms while still being the wrong thing for the portfolio to keep funding, which is exactly the judgement portfolio management exists to make.
• Organization🏙️OrganizationPortfolioThe top-level organisational entityView reference → is the entity that owns and funds the portfolio. The portfolio is what gets allocated; the organisation is the allocator. One organisation can hold more than one portfolio, split by business unit or geography.
• Product area🪀Product AreaPortfolioA grouping of products by organisational axisView reference → is a structural slice of work inside the organisation. A portfolio is an investment grouping that may cut across areas, since the same area can contribute to several products and the portfolio is organised by bet rather than by team.

In the graph

In the Unified Product Graph, a portfolio sits in the portfolio region between the organisation above it and the products below. The organization_invests_via_portfolioOrganizationinvests viaPortfoliohierarchy edge records who funds it, portfolio_contains_productPortfoliocontainsProducthierarchy ties it to the products it holds, and portfolio_contains_portfolioPortfoliocontainsPortfoliohierarchy lets portfolios nest so a portfolio-of-portfolios can be modelled directly. That structure makes balance queryable: a team can ask how investment is spread across products and sub-portfolios, and see at a glance whether the whole set is concentrated in one horizon or genuinely balanced.