DIGITAL TRANSFORMATION · CORE INSIGHT 01
What Fashion Companies Actually Need to Transform Before They Digitise
Digital transformation in fashion does not begin when companies digitise an existing process. It begins when they redesign how work, information and decisions move through the organisation – and then use technology to enable that new system.
Digitisation and Transformation Are Not the Same Thing
Fashion companies often describe the introduction of new technology as digital transformation. A new PLM platform, a 3D design environment, a digital approval process or a connected product-development tool may represent significant progress.
But implementing technology and transforming the system in which that technology operates are not the same thing.
Digitisation changes the medium through which work is performed. Transformation changes the logic of the work itself.
A physical sample may become a 3D asset. A spreadsheet may become a shared platform.
An email approval may become a digital workflow. Yet if the same information is duplicated, the same decisions remain unclear, the same responsibilities overlap and the same bottlenecks continue to shape the process, the organisation has digitised an existing system rather than transformed it.
This distinction matters because technology can make a well-designed system faster and more visible. It can also make a poorly designed system faster at producing complexity.
THE TRANSFORMATION LAYER
The Real Transformation Layer Sits Beneath the Technology
Technology operates on top of an organisational system. If that system remains unchanged, digital tools inherit its inefficiencies. Real transformation requires companies to redesign five interconnected layers before technology can enable them effectively.
01
PROCESSES
How work actually moves from concept through development, validation, approval and production – including the steps that add value and those that simply preserve legacy ways of working.
02
DECISION RIGHTS
Who makes which decisions, when those decisions are made, what information they require and who has the authority to change them.
03
INFORMATION FLOWS
Where product information originates, how it moves between teams, where it is duplicated and which system becomes the trusted source of truth.
04
ROLES & RESPONSIBILITIES
How design, product development, technical, sourcing and management responsibilities need to evolve when the operating model becomes digital.
05
DEPENDENCIES
Which activities depend on others, where work waits unnecessarily and which historical dependencies should disappear rather than be transferred into a digital workflow.
These layers form the operating system of product development.
Technology should enable that system – not define it.
What Happens When Companies Digitise the Existing System
When technology is introduced without redesigning the underlying system, the organisation does not remove complexity. It often creates a second layer of it.
Existing processes continue to operate while new digital workflows are added alongside them. Teams enter the same information into multiple systems. Decisions move between platforms, spreadsheets, messages and meetings. Digital assets are created, but physical processes remain the final authority. New tools promise visibility, yet critical information still depends on individual knowledge and manual coordination.
The result is a hybrid operating model: part digital, part legacy, and often more difficult to manage than either system would be on its own.
This is why technology adoption can appear successful while transformation outcomes remain disappointing. The platform may be implemented. Teams may be trained. Usage metrics may increase. But the organisation still carries the same structural friction – now distributed across more tools.
FRAGMENTED WORKFLOWS
→
DUPLICATE WORK
→
MANUAL WORKAROUNDS
→
SLOWER DECISIONS
→
LOW ADOPTION
Technology has changed. The operating logic has not.
A Simple Example:
From Physical Sampling to 3D
Consider a fashion company introducing 3D product development to reduce physical sampling.
At first, the change appears straightforward. Designers and technical teams create digital garments, review fit virtually and generate increasingly accurate representations of products before physical samples are produced.
But if the surrounding operating model remains unchanged, the organisation may simply add 3D to the existing process.
A digital garment is created – but a physical sample is still required for the same approval. Comments are captured digitally – but decisions continue through email, meetings or spreadsheets. Product data exists in the 3D environment – but is manually re-entered elsewhere. Teams develop new digital capabilities – while responsibilities and approval authority remain designed around the physical workflow.
The company now has two workflows instead of one. The problem is not that 3D failed.
The problem is that the organisation changed the representation of the product without redesigning the system through which that product is developed and approved.
DIGITISED PROCESS
3D added to the existing
workflow
3D creation
↓
Physical sample
↓
Existing approval process
↓
Manual data transfer
↓
Production
TRANSFORMED SYSTEM
THE WORKFLOW REDESIGNED AROUND DIGITAL VALIDATION
3D creation
↓
Digital validation
↓
Defined decision point
↓
Connected product data
↓
Physical sample only where required
The objective is not to digitise every existing step. It is to determine which steps should still exist in the digital operating model.
Technology Should Enter Last
Once the operating model has been redesigned, technology has a very different role.
Instead of being asked to solve organisational problems, it becomes infrastructure for a system that has already been defined.
The sequence matters.
A company should first understand how work needs to move, where decisions should happen, what information those decisions require, who owns them and which dependencies need to be removed or redesigned.
Only then does the technology question become useful:
What digital environment can enable this operating model most effectively?
This reverses the logic behind many transformation programmes. Instead of beginning with platform capabilities and adapting the organisation around them, the organisation defines the system it needs – and technology is selected and configured to support it.
OPERATING MODEL
→
INFORMATION
→
DECISIONS
→
TECHNOLOGY
Design the system first. Digitise it second.
BEFORE THE TECHNOLOGY
Five Questions the Organisation Must Answer First
Before selecting, configuring or scaling digital tools, the organisation needs clarity on the system those tools are expected to support. Five questions expose whether that system has actually been designed.
01
HOW SHOULD WORK MOVE?
Which activities create value, which exist because of legacy processes, and how should work move from concept to production?
02
WHERE SHOULD DECISIONS HAPPEN?
Which decisions are required, when should they be made, what evidence should support them and who has authority to make them?
03
WHAT INFORMATION IS REQUIRED?
What information must exist at each stage, where should it originate and which system should become its trusted source?
04
WHO OWNS WHAT?
How should responsibilities change when work, validation and collaboration move into a digital operating environment?
05
WHAT DEPENDS ON WHAT?
Which activities depend on previous decisions, data or approvals – and which dependencies can be removed rather than digitised?
If these questions cannot be answered clearly, the organisation is not yet ready to make technology the centre of its transformation.
THE TRANSFORMATION SEQUENCE
Transformation Is a Sequence, Not a Technology Project
Once the operating system has been understood, transformation can be approached in the right order.
The sequence does not begin with software selection. It begins with redesigning how the organisation needs to operate – and progressively builds the conditions in which technology can create value.
Each stage creates the foundation for the next.
01
UNDERSTAND THE CURRENT SYSTEM
Map how work, information, decisions, responsibilities and dependencies operate today.
→
02
REDESIGN THE OPERATING MODEL
Define how work should move, where decisions should happen and which legacy dependencies should disappear.
→
03
DEFINE THE INFORMATION MODEL
Establish what information is required, where it originates and which system becomes its trusted source.
→
04
DESIGN THE DIGITAL ENVIRONMENT
Select and configure technology around the redesigned operating model rather than adapting the organisation around the tool.
→
05
SCALE THE NEW SYSTEM
Embed the new workflows, decision rights and responsibilities across teams – then measure and improve how the system performs.
Transformation starts with the system.
Technology enters when the system is ready.
CONCLUSION
Digital Transformation Begins Before the Technology
Digital transformation does not begin when a company selects a platform, introduces 3D or connects its systems.
It begins when the organisation questions how work should move, how decisions should be made, what information should connect the process and which responsibilities and dependencies still make sense.
Technology becomes transformative only when it enables a better operating system rather than digitising the limitations of the existing one.
For digital transformation in fashion, this distinction is fundamental. The objective is not to become more digital. It is to build an organisation capable of working differently because digital capabilities now exist.
Transform the system first.
Then let technology scale it.
PUBLICATION
AUTHOR
Sonya Monina
Founder, Sonya Monina Lab
Digital Product Strategy · 3D Product Development · Digital Transformation
ABOUT THIS INSIGHT
This insight examines why digital transformation in fashion often underperforms when technology is introduced without redesigning the operating system around it. It forms part of Sonya Monina Lab’s research into digital product development, organisational transformation and the operating models required to support them.
SONYA MONINA LAB · INSIGHTS · DIGITAL TRANSFORMATION
FROM INSIGHT TO IMPLEMENTATION
Ready to Redesign the System Behind the Technology?
If your organisation is introducing digital tools, 3D workflows or new product-development systems, the question is not only what technology to implement – but what operating model that technology should enable.
Sonya Monina Lab works with organisations to redesign the systems, workflows and decision structures behind digital transformation.
EXPLORE ADVISORY →