Value Chain Analysis

Concept of the skill

What it is: Value Chain analysis is Michael Porter's activity-level strategy framework for understanding how a firm creates value and incurs cost. It decomposes a business into strategically relevant activities, then asks where cost advantage, differentiation, linkages, fit, value-system coordination, and margin create or weaken competitive advantage.

Mental model: Pick the unit of analysis, choose the value configuration, map the activities, then trace value, cost, margin, and linkages. Advantage is not usually one isolated activity; it is often a different configuration of activities that raises willingness to pay, lowers relative cost, captures value better, coordinates better across the value system, or reinforces a distinctive positioning.

Why it exists: Agents often jump from "we need strategy" to generic recommendations. This skill forces the work down to the activity system so claims about advantage, margin, differentiation, or operating change have a visible mechanism.

What it is NOT: It is not Five Forces, VRIO, Seven Powers, Playing to Win, Blue Ocean Strategy, BCG, Ansoff, PESTEL, SWOT/TOWS, Lean waste removal, customer-journey mapping, ESG reporting, OKRs, or a valuation model.

Adjacent concepts: strategic positioning, activity systems, value configurations, value system, virtual value chain, marketspace, primary activities, support activities, cost drivers, differentiation drivers, linkages, fit, margin, value capture, value proposition, operational effectiveness.

One-line analogy: Value Chain analysis opens the operating system of the business and asks which activities make value, cost, and advantage happen.

Common misconception: The value chain is not just inbound logistics to outbound logistics. It includes all strategically relevant activities, including support activities, and its strategic power comes from how those activities are configured and linked. For non-manufacturing businesses, the classic chain is a prompt, not a cage.

Value Chain Analysis

Domain Context

Use Value Chain analysis for business-unit strategy, product/service strategy, platform or marketplace operating-model reviews, cost and differentiation diagnosis, margin-improvement work, and critiques of strategy memos that claim advantage without showing the activity mechanism. 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 method is strongest when the user asks how a business creates value, why its cost or differentiation position differs from competitors, where margin is made or lost, which activities need to change to support a positioning choice, or how upstream suppliers, channels, partners, and buyers affect the firm's economics. It is weaker when the question is about industry attractiveness, resource rarity, durable moat type, full strategy-cascade design, market-boundary reconstruction, portfolio allocation, macro trends, growth quadrant selection, task prioritization, quantified investment value, customer emotions across a journey, or compliant emissions reporting.

Treat classic primary/support activity categories as prompts, not a mandatory org chart. A software company, marketplace, manufacturing firm, professional-services firm, hospital, financial-services firm, public-sector program, and nonprofit will map activities differently. The task is to identify strategically relevant activities at the level where cost, value, fit, and margin can be discussed, not to force every business into the same linear diagram.

For digital or information-rich businesses, also ask whether information captured in the physical chain is merely a support input or has become a virtual value chain that creates customer value in the marketspace. For platform and ecosystem businesses, map interaction orchestration, trust, liquidity, governance, data flows, and participant incentives rather than forcing everything into a sequential pipeline.

Use web research, AI research agents, and source-gathering tools as evidence aids, not as substitutes for the method. A generated activity map is a hypothesis until supported by public sources, user-provided facts, operating metrics, interviews, benchmark evidence, or direct observation. When using external research, cite the source type and keep competitor-cost claims explicitly hypothetical unless verified.

Sustainability, emissions, resilience, and regulatory exposure belong in this skill only when they materially affect an activity's cost, risk, differentiation, buyer value, or value-system coordination. Do not turn the analysis into carbon accounting, ESG disclosure, or a Scope 3 inventory.

Coverage

This skill teaches agents to:

1. Frame the business unit, offering, customer, competitor set, and strategic decision.
2. Choose the right value configuration: chain, shop, network, or a named hybrid.
3. Check whether a digital or data-rich business also needs a virtual value-chain lens.
4. Map primary and support activities at the right level of specificity for that configuration.
5. Decompose broad functions into decision-relevant sub-activities where value and cost can be discussed.
6. Identify cost drivers, differentiation drivers, value-capture effects, and margin effects activity by activity.
7. Trace linkages between activities, including trade-offs, reinforcing fit, information flows, network effects, and value-system dependencies.
8. Compare the activity configuration against rivals, alternatives, internal benchmarks, or the current baseline.
9. Distinguish operational effectiveness from strategy when an activity is simply a best practice.
10. Convert activity findings into strategic hypotheses, operating changes, or downstream analyses.
11. State assumptions, evidence gaps, freshness limits, privacy boundaries, and data needed before recommending action.

Philosophy of the skill

Value Chain analysis is useful because strategy often hides inside words like "better product," "strong brand," "efficient operations," or "great customer experience." Those phrases are not yet strategy. They become strategic only when the agent can name the activities that create the value, the costs attached to them, the linkages between them, and the trade-offs that make the configuration hard to copy without changing the business.

The method is also a guardrail against generic best-practice advice. Integrating best practices can improve execution, but a company does not become distinctive merely by doing ordinary activities competently. A good value-chain analysis asks what activities are configured differently, what those differences do to relative cost or willingness to pay, and how the activity system fits the chosen position.

The second guardrail is configurational honesty. Porter's classic chain works best for long-linked production and delivery systems. Services, expert problem-solving firms, platforms, and marketplaces often create value through shops or networks rather than a simple sequence. If the agent forces every business into inbound logistics -> operations -> outbound logistics, it may produce a tidy diagram that hides the real source of advantage.

The third guardrail is evidence discipline. AI-generated activity maps, public web summaries, and benchmark claims can help the agent draft hypotheses, but they do not prove strategic effect. The analysis must separate activity description from evidence-backed value, cost, linkage, and margin effects.

Workflow

0. Choose the value configuration

Before mapping activities, decide which value-creation logic the business actually uses. Porter's sequential value chain remains the anchor, but strategy literature generalizes firm-level value creation into three value configurations: chain, shop, and network. Most real firms are hybrids; name the dominant configuration and any secondary logic.

If the business is a value shop or value network, say so and adapt the activity model. A value-network analysis that only renames logistics rows will miss participant acquisition, liquidity, matching quality, governance, trust, safety, payments, and two-sided economics. A value-shop analysis that only renames operations will miss diagnosis quality, expertise allocation, reputation, and learning loops.

For digital, data-rich, or digitally transformed businesses, add a virtual value-chain check. This is not a fourth value configuration and not a generic "use technology" recommendation; it asks whether information captured from activities has become a value-creating marketspace asset. Use Rayport and Sviokla's five information value-adding steps as a prompt: gather information, organize it, select what is valuable, synthesize it into a usable product/service/insight, and distribute it through information-based channels. Then identify the maturity stage: visibility, where information helps managers see and coordinate the physical value chain; mirroring capability, where virtual activities substitute for or parallel physical activities; or new customer relationships, where information creates new marketspace value, offerings, or relationships. Keep the physical and virtual chains distinct, then analyze how they reinforce or cannibalize each other.

1. Frame the strategic question

Start by naming the unit of analysis and the decision the value-chain map must inform.

Business unit or offering:
Value configuration and rationale:
Virtual value-chain lens needed? Why / why not:
Customer segment or use case:
Value proposition:
Competitors or alternatives:
Current-state or target-state map:
Strategic question:
Cost, differentiation, value-capture, or margin issue:
Evidence available:
Decision this analysis must inform:

Reject vague scopes such as "the company" or "operations" unless the user explicitly wants a first-pass map. Narrow the scope until the activities can be described concretely. If the user wants both current state and target state, keep them separate; do not let an aspirational operating model blur the current evidence.

2. Map primary and support activities

Use the classic activity groups as a starting checklist, then adapt them to the business model and value configuration.

For services, software, platforms, and marketplaces, rename or replace rows so the user can see the real system. For example, operations may mean onboarding, matching, risk scoring, model training, deployment, professional delivery, or customer workflow execution. For a value shop, primary activities may be diagnosis, solution design, delivery, and evaluation. For a value network, primary activities may be participant acquisition, participant retention, matching and discovery, trust and safety, payments, infrastructure operations, monetization, and ecosystem governance.

Break broad departmental functions into specific, measurable activities when the function is too coarse for a decision. Instead of a single "Marketing" row, separate paid acquisition, content marketing, SEO, events, sales enablement, community, brand advertising, pricing, and channel management when those sub-activities have distinct cost drivers, value effects, or improvement levers. The right granularity is the level where a strategic or operating decision can be made.

For platform and multi-sided businesses, map the activities that enable interactions between sides rather than a linear transformation sequence. Typical platform activities include side acquisition, side retention, matching and discovery, trust and safety, data and intelligence, monetization, APIs/developer tools, partner programs, dispute resolution, and platform rules.

3. Attach value, cost, and evidence to each activity

For each important activity, separate description from strategic effect.

Activity:
Current activity design:
Target activity design, if relevant:
Customer value or willingness-to-pay effect:
Price realization or value-capture effect:
Cost, capital, or working-capital effect:
Quality, speed, risk, learning, sustainability, or resilience effect:
Metric or evidence:
Relevant competitor, substitute, or baseline:
Evidence strength:
Advantage hypothesis:
Uncertainty:

Do not call an activity strategic because it exists. It becomes strategically relevant when it changes relative cost, relative value, risk, speed, learning, switching cost, access, trust, quality, value capture, or margin.

Check these driver families:

Use directional economics when perfect activity-based costing is unavailable. A rough but explicit estimate is better than a polished map with no economics, as long as the uncertainty is labeled.

4. Trace linkages, fit, and the value system

Value-chain analysis is not a list. Look for relationships across activities and across firm boundaries.

Porter's value-chain framing places the firm inside a larger value system: supplier chains upstream, channel chains downstream, and buyer chains or usage activities beyond the sale. Advantage may come from coordinating across those boundaries, not only from optimizing inside the firm. Name at least three linkages before recommending action. If no linkages appear, the output is probably an activity inventory, not a value-chain analysis.

5. Compare the activity configuration

Competitive advantage is relative. Compare the activity system against a named benchmark.

Benchmark: competitor / substitute / current baseline / target model / internal best site
Activity differences:
Cost position difference:
Differentiation difference:
Value-capture or margin difference:
Trade-offs:
Fit or reinforcement:
Activities easy to copy:
Activities hard to copy:
Evidence strength:

Do not invent competitor cost structures or activity details. Use public filings, analyst reports, product experience, pricing, hiring patterns, supplier disclosures, customer reviews, benchmark studies, or user-provided evidence where available. If data is missing, label the comparison as a hypothesis and specify the evidence needed.

When assumptions are volatile, add a lightweight freshness note rather than a full monitoring program:

Analysis date:
Review horizon:
Trigger for re-analysis:
Metrics or assumptions to watch:

6. Convert findings into strategic options

Use the value-chain map to propose changes, then route unresolved questions to the right method.

End with actions, assumptions, and evidence gaps. A value-chain analysis should produce a sharper strategy conversation, not just a diagram.

7. Route downstream uncertainty

Value-chain analysis often produces hypotheses that need another method.

Do not switch frameworks mid-answer without telling the user. Finish the activity-level diagnosis first, then hand off the unresolved question.

Output Template

Value Chain Analysis

Scope:
Value configuration and rationale:
Virtual value-chain lens, if relevant:
Strategic question:
Positioning or value proposition:
Competitor/alternative benchmark:
Analysis date / review horizon:

Activity map:
- Primary activities:
- Support activities:
- Value-system dependencies:
- Virtual information activities, if relevant:

Activity-level findings:
1. Activity:
   Current design:
   Value / willingness-to-pay effect:
   Value-capture effect:
   Cost / capital / margin effect:
   Linkages:
   Evidence:
   Evidence strength:
   Advantage hypothesis:
   Uncertainty:

Fit, trade-offs, and value system:
- Reinforcing linkages:
- Value-system linkages:
- Virtual/physical linkages:
- Activities that conflict with positioning:
- Best-practice gaps:
- Distinctive choices:

Recommendations:
1. Change:
   Why this activity matters:
   Expected value/cost/margin effect:
   Evidence needed:
   Downstream method:

Residual uncertainty:

Boundary Rules

Verification

Before presenting the analysis, check:

• The unit of analysis is a business unit, offering, service, product, platform, or operating model, not a vague whole-company label.
• The value configuration is named and the activity map is adapted to it.
• A virtual value-chain lens is included only when information itself creates or distributes value.
• Current-state and target-state activity claims are kept separate.
• Broad functions are decomposed into decision-relevant activities where value and cost can be discussed.
• Primary and support activities are adapted to the actual business model.
• Each important activity includes a value, cost, risk, speed, quality, learning, sustainability, value-capture, or margin effect.
• At least three linkages or fit relationships are named.
• Value-system dependencies with suppliers, channels, partners, or buyer usage activities are considered where relevant.
• Competitor or alternative comparison is labeled as evidence-backed or hypothetical.
• AI-generated or web-researched claims are treated as source leads or hypotheses until evidence is cited.
• Operational effectiveness improvements are not overstated as distinctive strategy.
• Sustainability or emissions appear only as material activity-level drivers, not as a formal reporting framework.
• Recommendations tie back to specific activities, economics, linkages, and evidence gaps.
• An analysis date, review horizon, or re-analysis trigger is included when assumptions are volatile.
• No private data, customer data, payment data, secrets, or confidential business facts are exposed.

Do NOT Use When

References

• references/value-chain-analysis-sources.md - source notes from Harvard Business School's Institute for Strategy & Competitiveness and the HBS publication record for Competitive Advantage.
• references/upstream-displacement-2026-06-07.md - audit-loop upstream-displacement check for this concept skill.
• Harvard Business School Institute for Strategy & Competitiveness, "The Value Chain." https://www.isc.hbs.edu/strategy/business-strategy/Pages/the-value-chain.aspx
• Harvard Business School Institute for Strategy & Competitiveness, "Fit Across the Value Chain." https://www.isc.hbs.edu/strategy/creating-a-successful-strategy/Pages/fit-across-the-value-chain.aspx
• Harvard Business School faculty publication record for Rayport and Sviokla, "Exploiting the Virtual Value Chain." https://www.hbs.edu/faculty/Pages/item.aspx?num=3556
• Rayport, Jeffrey F., and J. J. Sviokla. "Exploiting the Virtual Value Chain." Harvard Business Review, November-December 1995. https://hbr.org/1995/11/exploiting-the-virtual-value-chain
• Stabell, C. B., and Fjeldstad, O. D. "Configuring Value for Competitive Advantage: On Chains, Shops, and Networks." Strategic Management Journal, 19(5), 413-437. https://sms.onlinelibrary.wiley.com/doi/abs/10.1002/%28SICI%291097-0266%28199805%2919%3A5%3C413%3A%3AAID-SMJ946%3E3.0.CO%3B2-C
• GHG Protocol, "Corporate Value Chain (Scope 3) Standard." https://ghgprotocol.org/corporate-value-chain-scope-3-standard