Bcg Matrix

Concept of the skill

What it is: The BCG Growth-Share Matrix, also called the Boston Matrix or product portfolio matrix, is a portfolio allocation framework. It classifies products, brands, or business units by market growth and relative market share.

Mental model: Define the portfolio unit and its market first. Then plot each unit on two axes: how fast the market is growing and how strong the unit's relative share is. The quadrant label becomes a cash-flow and investment hypothesis, not a final decision.

Why it exists: Agents often recommend investing or divesting from a portfolio without making the allocation logic explicit. This skill forces market definition, metric choice, cash-generation logic, and assumption checks before recommending action.

What it is NOT: It is not Ansoff, SWOT/TOWS, PESTEL, Five Forces, Seven Powers, OKRs, or a valuation model.

Adjacent concepts: corporate portfolio strategy, product portfolio management, resource allocation, relative market share, market attractiveness, cash generation, harvesting, divestment, strategic experimentation.

One-line analogy: BCG maps which portfolio units fund the system, which need funding, which are bets, and which may be absorbing scarce resources.

Common misconception: The quadrant names do not decide the strategy. They classify a portfolio position so evidence, cash economics, and follow-on analysis can decide what to do next.

BCG Matrix

Domain Context

Use the BCG Matrix for corporate strategy, product portfolio strategy, brand portfolio reviews, business-unit allocation, R&D or initiative portfolio reviews, and review of existing growth-share matrix work. Use public, aggregate, or synthetic examples only. Do not include personal data, customer data, payment data, secrets, confidential deal details, or private business facts in examples or evals.

The matrix is strongest when the user has multiple comparable units competing for resources and needs a simple view of where cash is generated, where cash may be required, and where portfolio balance is weak. It is weaker when the decision is about one product's growth path, an industry's structural attractiveness, macro forces, durable moat source, or quantified value. In those cases, route to the method that owns that mechanism.

Treat "portfolio unit" broadly. It can mean strategic business unit, product line, brand, geography, program, customer segment, investment theme, or internal initiative. The unit must be comparable enough that market growth and relative share are meaningful across the set.

Coverage

This skill teaches agents to:

1. Define the portfolio owner, portfolio units, market boundaries, and decision horizon.
2. Choose comparable market-growth and relative-market-share metrics.
3. Classify units as stars, cash cows, question marks, or dogs/pets.
4. Interpret the cash-flow and investment logic behind each quadrant.
5. Challenge weak market definitions, weak share proxies, and stale growth assumptions.
6. Compare portfolio balance without treating quadrant labels as automatic recommendations.
7. State assumptions, evidence gaps, risks, and next analysis for each unit.
8. Route valuation, competitive, growth-path, or execution questions to the right downstream method.

Philosophy of the skill

The BCG Matrix is useful because resource allocation is often political, anecdotal, or driven by the loudest unit owner. A growth-share pass makes the implicit portfolio theory visible: mature strong positions may fund future opportunities; high-growth positions may need investment; weak positions in slow markets may need repositioning, harvesting, divestment, or a clear reason to keep them.

The method is intentionally blunt. Its power is shared language and cash-flow discipline, not precision. A good BCG Matrix output names the market definition, the share denominator, the growth measure, the cash-flow implication, and the next evidence needed. It should also challenge the original assumptions: relative share is no longer always a direct proxy for durable advantage, growth rates can shift quickly, and units can move across quadrants faster than classic portfolio doctrine assumed.

Workflow

1. Frame the portfolio question

Start by naming the portfolio and the decision it must inform.

Portfolio owner:
Portfolio units:
Market boundary for each unit:
Decision horizon:
Resource decision to inform:
Market-growth source:
Relative-share source:
Known cash-flow or profitability data:
Constraints:

Reject vague scopes such as "our products" unless the user explicitly wants a first-pass brainstorm. Narrow by business unit, product line, brand, geography, customer segment, channel, or investment pool.

2. Define the two axes

The matrix depends on comparable axis definitions.

If exact data is missing, allow a proxy only when it is labeled as a proxy and the uncertainty is carried into the recommendation. Do not invent market size, market growth, share, or profitability.

3. Plot the portfolio units

Use the quadrants as hypotheses.

Do not present a "dog" label as an insult or a command. It is a portfolio-position label. Keep the tone analytical and explain the evidence.

4. Interpret cash-flow logic

For each unit, separate position from action.

Unit:
Market definition:
Market growth: high / low / uncertain
Relative share: high / low / uncertain
Quadrant:
Cash generation:
Cash needs:
Allocation hypothesis:
Assumptions:
Evidence gaps:
Decision risk:
Next analysis:

The classic logic says high-growth units require cash, high-share units can generate stronger margins and cash, and the portfolio needs both cash-generating mature positions and future growth options. Treat that as a hypothesis to test with actual cash flow, profitability, strategic fit, and competitive evidence.

5. Challenge the matrix before recommending action

Use these checks before any recommendation:

• Are the portfolio units comparable, or is the matrix mixing products, markets, geographies, and initiatives that should not share one grid?
• Is the market boundary precise enough that growth and share mean something?
• Is "high" and "low" defined by an explicit threshold or by relative comparison within the portfolio?
• Is relative share measured against the right competitor or segment?
• Does high relative share actually produce cash or advantage in this market?
• Is growth durable, cyclical, subsidized, regulatory, or temporary?
• Are there strategic reasons to keep a low-growth, low-share unit, such as platform dependency, customer retention, regulatory obligation, or learning?
• Is a quantified valuation, expected-value comparison, or Five Forces analysis needed before reallocating capital?

6. Route to downstream work

The BCG Matrix is an input to allocation work, not the whole decision.

Classification Tests

Use these tests when a quadrant is ambiguous:

Output Formats

For a compact answer:

Portfolio scope:
Axis definitions:

| Unit | Market growth | Relative share | Quadrant | Allocation hypothesis | Evidence gap |
| --- | --- | --- | --- | --- | --- |
| | | | | | |

Portfolio balance:
Recommended next analysis:

For a review of an existing BCG Matrix:

Matrix reviewed:
Market definition issues:
Share measurement issues:
Growth measurement issues:
Quadrant classification issues:
Unsupported recommendations:
Missing cash-flow evidence:
Modern limitation or assumption:
Recommended correction:

Quality Checks

• The portfolio owner, units, market boundary, and time horizon are named.
• Market growth and relative market share are defined before quadrants are assigned.
• Every quadrant label has evidence or an explicit uncertainty marker.
• Cash generation and cash needs are discussed separately from quadrant labels.
• No unit is recommended for investment, harvest, divestment, or exit solely because of its label.
• Modern limitations are acknowledged when share is used as a proxy for advantage.
• The output routes valuation, industry structure, macro environment, or product-market growth questions to the appropriate method.
• Examples remain synthetic, public, or aggregate and avoid private business data.

Verification

After applying this skill, verify:

• The task matches the declared scope, coverage, or positive examples.
• The response follows this skill's workflow or checks instead of generic advice.
• The exclusions in ## Do NOT Use When do not point to a better skill.

Do NOT Use When

Use another method when the user's actual question is: