Technology Without Capability: Investment Without Return
Most organisations in this sector have not yet asked the most important question about their digital investment, even after significant capital has been committed. Not whether the technology works — it usually does. Not whether the implementation delivered what was specified — it usually does that too. The question is whether the organisation is different as a result.
Whether decisions are made differently. Whether the people who need product information can get it, trust it, and act on it. Whether the investment, in other words, returned what was paid for — or whether it returned something less: a more sophisticated version of the same organisation that made it.
Technology without capability is infrastructure without purpose. The distinction sounds abstract until you look for it in practice, at which point it becomes difficult to unsee.
A platform that holds product data nobody governs is not a data asset. It is a storage cost. A supplier portal that receives information nobody has defined, verified, or taken accountability for is not a transparency system. It is a filing cabinet with a better interface. A DPP record assembled from figures that two functions dispute and neither owns is not a passport. It is a liability dressed as compliance.
In each of those cases, the technology performed as specified. The organisation did not. The return on the investment was determined not by what was built, but by what the organisation became — or failed to become — in the process of building it.
Capability, in this context, is not a technology concept. It is an organisational one — and it has dimensions that technology cannot supply.
An organisation with genuine digital capability has made choices: which products, which markets, which supplier relationships are the foundation of a data infrastructure worth building. It is not digitising everything simultaneously and calling the activity a roadmap. It knows what it is building toward and why.
Someone owns the integrity of product data end to end — not nominally, but with the mandate and the resources to exercise that ownership when commercial pressure pushes in the other direction. The accountability is real, which means it is tested, and holding.
The hardest dimension is culture. In an organisation with genuine data capability, the people who touch product information — in design, in sourcing, in operations, in sustainability — understand what it is for. They do not treat data as a field to be completed. They treat it as something the organisation depends on. That understanding is not installed by a system. It is built through what gets measured, what gets challenged, and what leadership visibly values over time.
None of those conditions are delivered by a technology investment. They are what determine whether a technology investment delivers anything at all.
The return on digital investment, across industries, has been persistently lower than the capital committed to it — not because the technology failed, but because organisations underestimated what the technology was waiting for. Systems went live into organisations that had not resolved the governance questions the systems depended on. Platforms were deployed to functions that had not agreed on what the data they would exchange actually meant. Infrastructure was built for compliance requirements without the organisational habits that would make the infrastructure grow more valuable over time rather than simply more expensive to maintain.
Fashion and textiles has followed that pattern faithfully. The investment has been real. The capability has not always followed. The gap between them is not a technology problem. It is the bill for organisational decisions deferred in favour of going live on schedule.
Digital excellence is the condition in which that gap is closed. Not permanently — excellence is not a destination — but actively, through an organisation that treats the distance between its technology and its capability as something worth measuring and closing, season after season.
That means a sourcing function that evaluates supplier relationships on data quality as well as commercial terms. A design process that builds data considerations in from the brief rather than appending them afterward. A leadership team that reviews data capability alongside financial performance, because it understands the connection between the two.
That organisation understands what the investment was for — and builds the capability to match it.
It exists in this industry. It is not the majority. The distance between the investment most organisations have made and the capability most organisations have built is where the competitive separation of the next decade will be determined.
The technology is in place. The return depends on what comes next.
Michael Shea is a digital excellence advisor, non-executive director, and leadership coach working with organisations navigating the human and technical dimensions of digital transformation. He hosts The Aeolian Discourse and writes at The Aeolian.