charlieviettq/awesome-agent-skill / .claude/skills/biz-value-chain
"biz-value-chain"
Verified"Apply Porter's Value Chain Analysis to identify competitive advantage sources within an organization's activities. Use this skill when the user needs to find where value is created or lost in their operations, analyze cost structure by activity, optimize internal processes, or identify outsourcing candidates — even if they say 'where do we make money' or 'which activities should we keep in-house'.".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.3 KB |
| examples/sample_scenario.md | markdown | 6.5 KB |
| references/framework-comparison.md | markdown | 9.7 KB |
references/framework-comparison.md
View on GitHub# Framework Comparison: Value Chain vs Adjacent Strategy Tools
Value Chain Analysis is an **internal, activity-level** lens. The frameworks below operate at different levels of analysis. Using the wrong tool produces answers to questions you didn't ask.
---
## The Core Distinction
| Dimension | Value Chain | Five Forces | BCG Matrix | PESTEL | SWOT |
|-----------|------------|-------------|------------|--------|------|
| Unit of analysis | Internal activities | Industry structure | Product portfolio | Macro environment | Org vs environment |
| Primary question | Where do we create/lose value? | Is this industry worth competing in? | Where should capital flow? | What external forces shape us? | What's our strategic position? |
| Time horizon | Current operations | Current + near-term | Strategic planning cycle | Long-term | Snapshot |
| Output | Activity-level recommendations | Attractiveness score | Invest / hold / divest signals | Risk/opportunity map | Strategic options |
| Insider vs outsider | Insider (requires operational data) | Outsider (industry data) | Insider (revenue + growth data) | Outsider (desk research) | Both |
---
## Decision Tree: Which Framework First?
```
User asks a strategy question
│
├─► "Should we enter / stay in this industry?"
│ └─► Porter's Five Forces
│
├─► "Which products / BUs should we invest in?"
│ └─► BCG Matrix
│
├─► "What external trends threaten or help us?"
│ └─► PESTEL
│
├─► "What are our overall strengths and weaknesses?"
│ └─► SWOT (then drill into Value Chain to source the S/W)
│
└─► "Where do we make / lose money inside our operations?"
"Which activities give us competitive advantage?"
"What should we outsource?"
└─► Value Chain Analysis ◄── you are here
```
---
## Head-to-Head: Value Chain vs Porter's Five Forces
### What they share
Both are Porter frameworks and use the same definition of competitive advantage: the ability to deliver superior value at acceptable cost.
### Where they diverge
**Five Forces** answers: *Is the industry structure favorable?*
It looks outside the firm at suppliers, buyers, substitutes, new entrants, and rivalry. It tells you *whether* there is profit to be captured, not *by whom* or *how*.
**Value Chain** answers: *How do we capture profit in our specific operations?*
It looks inside the firm at the activities that produce and deliver value. It tells you *where* your advantage or disadvantage lives.
### Sequencing rule
Five Forces first, then Value Chain:
1. Use Five Forces to decide if the industry is worth competing in (average profitability, structural forces).
2. Use Value Chain to decide how to win *within* that industry.
If Five Forces shows a structurally unattractive industry (e.g., commoditized suppliers, strong buyer power, low barriers), a Value Chain analysis can still reveal whether *your firm specifically* can outperform the industry average through activity-level differentiation.
### Worked example: Taiwanese contract electronics manufacturer (EMS)
**Five Forces result (abridged):**
- Buyer power: HIGH (Apple, HP concentrate purchasing)
- Supplier power: MEDIUM (components somewhat commoditized)
- Rivalry: HIGH (Foxconn, Pegatron, Wistron compete on price)
- Industry conclusion: structurally unattractive, thin margins
**Value Chain response:**
Despite unattractive industry structure, Value Chain reveals:
- Operations: proprietary process automation (cost advantage vs. peers)
- Technology Development: yield improvement IP reduces defect rates below industry average
- HR Management: specialized engineering talent retention programs
These activity-level advantages let the firm earn *above-industry* margins even in a structurally difficult industry. Five Forces would have said "avoid" but couldn't tell you *how* to survive if you're already in.
---
## Head-to-Head: Value Chain vs BCG Matrix
### What they share
Both help allocate resources across the firm.
### Where they diverge
**BCG Matrix** operates at the **business unit or product line level**. Its axes are relative market share and market growth rate. It produces portfolio signals: invest more (Stars), harvest (Cash Cows), divest (Dogs), monitor (Question Marks).
**Value Chain** operates at the **activity level within a business unit**. It produces process-level signals: strengthen, optimize, outsource.
### The nesting relationship
BCG Matrix → decides which BUs/products get resources.
Value Chain → decides how each surviving BU should configure its activities.
```
Portfolio level (BCG):
BU A: Star → invest
BU B: Cash Cow → harvest
BU C: Dog → divest
Activity level (Value Chain, applied to BU A):
Inbound Logistics → outsource (not an advantage source)
Operations → strengthen (proprietary process = differentiation)
Technology Development → invest (enables Operations advantage)
```
### Error to avoid
Using Value Chain to decide *which* BUs to fund is a category error. Value Chain cannot tell you that BU A deserves more capital than BU B — it has no market-level data. Conversely, BCG cannot tell you *which activities* inside BU A to improve — it has no operational data.
---
## Head-to-Head: Value Chain vs PESTEL
### What they share
Both can surface threats and opportunities that affect costs and willingness to pay.
### Where they diverge
**PESTEL** catalogs macro forces (Political, Economic, Social, Technology, Environmental, Legal). It is a scanning tool that identifies *external* changes that may require strategic adjustment.
**Value Chain** maps *internal* activities and evaluates them against competitive benchmarks. It is a diagnostic tool that identifies *where* to act.
### Sequencing rule
PESTEL flags the external force → Value Chain identifies which activity it impacts.
| PESTEL signal | Activity affected | Value Chain response |
|--------------|-------------------|----------------------|
| Rising logistics costs (Economic) | Outbound Logistics | Benchmark vs competitors; consider 3PL renegotiation |
| New labor regulations (Legal) | HR Management | Assess cost increase; may reduce vs-competitor advantage |
| AI coding tools mature (Technology) | Technology Development | Opportunity to lower cost of internal software development |
| Carbon tax legislation (Environmental) | Operations, Inbound Logistics | Identify high-emission activities; cost risk |
### Error to avoid
PESTEL alone produces a list of trends with no operational specificity. "AI is transforming everything" is a PESTEL observation. "Our Technology Development activity currently costs 8% of revenue; AI tooling could reduce this to 5% while improving output quality" is a Value Chain finding. Always land PESTEL observations inside the Value Chain map.
---
## Head-to-Head: Value Chain vs SWOT
### The relationship
SWOT is often a **summary layer** built *on top of* Value Chain (and Five Forces + PESTEL).
- Strengths/Weaknesses → sourced from Value Chain activity assessment
- Opportunities/Threats → sourced from Five Forces + PESTEL
A SWOT that lacks underlying analysis produces vague, unactionable results. A SWOT built from Value Chain data is specific and defensible.
### Mapping example
Value Chain finding → SWOT entry:
| Value Chain finding | SWOT entry |
|--------------------|------------|
| Operations: proprietary formulation process, cost 12% of revenue, **Better** vs competitors | **Strength**: manufacturing differentiation |
| Outbound Logistics: fragmented carrier relationships, cost 18% of revenue, **Worse** vs competitors | **Weakness**: logistics cost disadvantage |
| Technology Dev: current spend 3% revenue, below industry benchmark of 6% | **Weakness**: underinvestment in process R&D |
| Procurement: long-term supplier contracts lock in below-market input prices | **Strength**: input cost advantage |
The SWOT summary is then:
- **Strengths**: operations differentiation, procurement cost advantage
- **Weaknesses**: logistics cost, R&D underinvestment
Without the Value Chain step, a SWOT would likely produce the same two strengths and weaknesses but at a level too vague to act on ("we're good at manufacturing" vs. "our proprietary formulation process runs at 12% of revenue and performs measurably better than competitors on output quality").
---
## Combined Usage Pattern
Most real strategy engagements use multiple frameworks in sequence. A typical ordering:
```
1. PESTEL Scan macro environment for relevant forces
↓
2. Five Forces Assess industry attractiveness and competitive dynamics
↓
3. Value Chain Diagnose where inside the firm advantage/disadvantage lives
↓
4. SWOT Synthesize internal (Value Chain) + external (Five Forces/PESTEL) findings
↓
5. BCG Matrix (if multi-BU) Allocate resources across portfolio
↓
6. Strategy options
```
This sequence is not mandatory — a single-BU company starting from an operations problem may skip directly to Value Chain. But if you find yourself using Value Chain to assess *industry attractiveness* or BCG to assess *which process to outsource*, you have applied the wrong tool.
---
## Quick Reference Card
**Use Value Chain when:**
- Question is about internal activities, processes, or operations
- Comparing your activity configuration vs. competitors
- Deciding what to outsource or invest in internally
- Sourcing the "Strengths" and "Weaknesses" in a SWOT
**Do NOT use Value Chain when:**
- Deciding whether to enter an industry → Five Forces
- Allocating capital across multiple BUs/products → BCG Matrix
- Scanning for macro-level risks or trends → PESTEL
- Need a high-level strategic position snapshot → SWOT (but build it from Value Chain)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |