DM-04 Value chain analysis (Porter)
Divides the activities of one business unit into five primary and four support activities and produces a value chain showing where cost and differentiation concentrate.
What it does
Divides a business unit's activities into five primary and four support activities. Artefact: a chain; read where cost and differentiation concentrate.
When to use it
Use when you want to see which activities of one business unit create cost or differentiation.
When it does not fit
Activities fit no listed category, as in services or platforms, which shows the manufacturing-derived structure is wrong. Porter advises business-unit level because higher levels hide advantage.
Result format
The result is a chain of the business unit's five primary activities and four support activities, with what the unit does in each activity. It names where cost and differentiation concentrate along the chain.
Requirements on the material
| Property | Requirement type | Requirement |
|---|---|---|
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
Not restricted on: Structure, Content type, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.
| Minimum material | The activities of one business unit, with costs and margins where available. |
|---|---|
| Additional sources needed | none |
| Not for (rules) | none |
| Not for (text) | Activities fit no listed category, as in services or platforms, which shows the manufacturing-derived structure is wrong. Porter advises business-unit level because higher levels hide advantage. |
Choosing and ordering
| Kind of technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | frame |
| Kind of finding | pattern; gap |
| Question answered | what; how much |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return to analyse |
Library checks by stakes
Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | spot check | optional | no |
| decision-informing | spot check | optional | no |
| decision-informing | assumption and limitation statement | none | no |
| high-stakes | spot check | optional | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | expert review | needed | no |
| high-stakes | independent review | needed | no |
Failure modes and limits
| Model suitability | model alone |
|---|---|
| Typical model failure | Assigns activities to the nine categories from general knowledge and invents activity-level costs that are not published. |
| Error sources | input data; coder or rater judgement; language model |
| Certainty limits | Imprecision because activity-level costs are seldom published; indirectness when the unit is a service or platform. |
Related techniques
- pairs with DM-17 Process mapping (flowcharts, swimlane diagrams, value stream maps): Process mapping gives the activity sequence that the chain summarises
- pairs with CM1-12 Benchmarking and peer comparison (best-practice comparison, competitor analysis): Benchmarking compares activity costs with peers
Evidence and tag basis
Documented. Described on a secondary page citing Porter (1985); the page reports no criticisms, and criticisms for services and networks are unconfirmed. (Wikipedia, Value chain)
Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.