wardley-maps.sgit.ai / Method / De-commoditisation

De-commoditisation

Original contribution 17 May 2026 W8 · glossary

a thing can be commoditised at one phase of evolution while still being meaningfully custom-built at the next phase… I am going to call this pattern de-commoditisation.

The claim

Standard doctrine reads the evolution axis as a one-way street. A component moves left to right — genesis, custom-built, product, commodity — and once it arrives at commodity, the strategic question about it is settled: buy it, do not build it, and put your attention somewhere the value still is.

The observation here is that arrival at commodity is a statement about one phase, and the phase after it can be wide open. Encryption is a commodity. Encrypting this data, for this recipient, under these revocation rules, with an audit trail somebody will read in a dispute, is not. The commoditised component is real and the custom work above it is also real, and a map that shows only the first is telling you something true and unhelpful.

The second half of the idea is the sharper half, and it is about what the map leaves out:

The Wardley Map shows the commodity. The shield is what the map does not show. Both matter.

The attrition shield is the accumulated custom work that sits on top of a commoditised component and is expensive to reproduce — not because the component is hard, but because the fit is. It is invisible on a map drawn at component granularity, because it is not a component. It is the shape of the connections.

Why it is worth naming

Because the alternative reading produces bad decisions in a specific direction. If commodity means settled, then a team looking at a value chain full of commodity components concludes there is no engineering left to do and no defensible position to hold, and either outsources the lot or gives up on the product. Both conclusions can be wrong at the same time, and the map will not tell you which.

The pattern also explains something a straight reading of the axis makes puzzling: why businesses built entirely on commodity components can be hard to displace. Not because they own anything scarce — they do not — but because the arrangement is the asset, and the arrangement is the thing the map does not draw.

The counter-argument, which has not been answered

The honest distinction, if there is one, is probably this: ILC describes a market dynamic — commoditisation enables new businesses — whereas de-commoditisation as stated here describes a single product's internal shape, where custom work and commodity work coexist in one value chain rather than in successive generations. That is a real difference if it holds. It is also exactly the kind of distinction that sounds better than it is, which is why it is on this page as a question rather than in the conclusion.

What would falsify it

• A worked ILC example that produces the same guidance. If you can take a case where de-commoditisation says "the custom work above the commodity is the defensible asset" and ILC says the same thing in Wardley's own vocabulary, the pattern is a rename and should be dropped.
• A case where the shield turns out to be a component after all. If in practice the accumulated custom work always decomposes into components that can be positioned, then the claim that maps structurally cannot show it is wrong, and the answer is to map at finer granularity rather than to add a concept.
• Evidence that the shield is not durable. The pattern quietly assumes the custom layer is expensive to reproduce. If agentic tooling makes reproducing integration work cheap — which is precisely what the rest of this corpus argues is happening — the shield thins, and de-commoditisation becomes a description of a temporary state rather than a position worth holding.

That third one is not hypothetical, and it cuts against the site's own interests. It is listed anyway.

Related

• The custom-axis verdict — the same instinct applied to the axis itself rather than to what sits on it.
• The skill lifecycle — where the commodity/custom distinction becomes a cost diagnostic you can read off an invoice.
• The commodity illusion (W10) — the reading technique that surfaces this on a map you already have.