What value realization means
It is a value realization problem in a setting where the mechanics are visible from outside. The sorting works. The reprocessing works. The demand exists, and in many jurisdictions it is mandated. And the material still does not move at the volume the technology would allow.
The OECD measured that gap for 2019: 15% of global plastic waste was collected for recycling, roughly 40% of what was collected was then lost as residue in processing, and about 9% was recycled in the end.
The number worth an executive's attention there is not the 9%. It is the 40% lost after collection — material that was gathered specifically to be recycled, at cost, and did not become anything. That loss is not a failure of the recycling technology. It happens because what arrives is too mixed, too contaminated, or too variable to process economically, and those properties were set years earlier by someone designing a product against a different measure.
Value realization is the work of converting a capability into a business result. It covers everything between “this can be done” and “this produced a return” — the decisions, incentives, contracts, measures and operating changes that determine whether a capability is used.
Most failures attributed to technology are failures of value realization. The capability was acquired, and the conditions under which it would pay were not designed.
Why a technically solved problem stays commercially stuck
Three conditions recur, and none of them is technical.
The costs and the benefits sit with different parties. Whoever bears the cost of collection, sorting or design change is often not whoever captures the value. Where the parties are not the same and nothing connects them contractually, each behaves rationally and the system produces a poor outcome.
Quality is unpredictable, so buyers discount it. A manufacturer needs consistent input to specification. Where supply varies, the rational response is to price for the worst case or avoid the material — which reduces demand, which reduces the investment that would improve consistency.
The product was not designed to be recovered. Decisions made at design — material mixing, adhesives, labelling — determine recovery cost years later. Those decisions were optimised for manufacturing cost, by people measured on manufacturing cost.
The third is the important one, and it generalises furthest: a constraint at the end of a system is usually created by a decision at the beginning of it, taken by someone measured on something else.
Why better waste management does not resolve it
Treating this as a waste problem locates the intervention at the end of the chain, where the fewest options remain. By the time material arrives at collection, its recoverability has already been set by decisions taken much earlier.
Improving collection improves the recovery of what is already difficult to recover. It is worth doing and it does not change the economics, because it does not touch the conditions that produced them.
This is a general pattern and not a comment about waste. Where an intervention is placed at the point where the problem is visible rather than the point where it is created, it improves the symptom at the highest possible cost.
What a standard at the design end actually does
The clearest illustration is a water bottle, because the recovery problem is created entirely by decisions that have nothing to do with recovery.
Three bottles on a shelf can look identical and be three different materials. Clear PET, opaque HDPE, and PLA — a bioplastic that looks like PET and behaves like a contaminant in a PET stream. Add adhesives that do not release cleanly, sleeves that obscure the material, and caps in a different polymer from the body. Each of those was a reasonable decision about brand, shelf appeal, cost or performance, made by someone with no stake in what happens at the other end.
The result is a sorting problem that no amount of sorting technology fully solves, because the input was designed to be ambiguous.
Now consider a single enforced rule: non-carbonated still water under one litre is sold in clear PET, with a compatible cap and a non-contaminating adhesive. It constrains nothing a brand competes on — not the water, not the price, not the design, not the label. It changes the end-of-life economics completely, because what arrives at recovery is now predictable enough to have a market value.
This is what closed-loop system design means in practice, and it is not a technology. It is an agreement about the specification, made where the cost is created rather than where it lands.
What closed-loop system design addresses
Four levers, ordered by how far upstream they sit.
Design for recovery. Material and construction choices that keep recovery cheap. This is the highest-leverage point and the one furthest from where the problem appears.
Connect cost and benefit. Contracts, take-back arrangements or pricing that put the cost of recovery with the party whose decisions determine it. Without this, upstream design change has no business case.
Make quality contractible. Specification, testing and certification that let a buyer purchase recycled input on stated terms. Consistency, not availability, is usually the binding constraint on demand.
Aggregate volume. Small, fragmented supply cannot justify the processing investment that would improve consistency. Someone has to hold the aggregation risk before the economics work.
None of these is a technology. All of them are design decisions about how a system is arranged.
Why this transfers
The pattern here is not specific to materials. It appears wherever a capability exists and the value does not.
An enterprise system that works technically and is not used, because the people whose workload it increases are not the people whose reporting it improves. A shared service that reduces total cost and raises it for the function asked to adopt it. An AI deployment that performs well in evaluation and changes nothing, because no workflow, decision right or measure was redesigned around it.
In each case the technology question is settled and the value question was never designed. The most reliable place to find the constraint is where the cost and the benefit sit with different people.
The questions this produces
Applicable to any capability an organization has acquired and is not getting value from.
- Who bears the cost of using this, and who receives the benefit? If they are different, what connects them?
- What decision, taken earlier and elsewhere, determines how expensive this is now?
- What would a buyer or an internal user need in order to commit — and is it availability, or is it consistency?
- Where is the intervention currently placed: at the point the problem is visible, or the point it is created?
Where this does not apply
Where the technical problem is genuinely unsolved, system design will not substitute for it. The distinction is whether the capability demonstrably works somewhere and fails to spread, or whether it does not yet work. The first is a value realization problem. The second is a research problem, and they have different answers.