When file infrastructure becomes the bottleneck
Older file systems, network-attached storage and VPN-based workflows can slow collaboration as teams become more geographically dispersed. Repeated delays, outdated copies and manual workarounds consume staff time, create rework and make file oversight harder, turning once-sensible infrastructure into a potential business bottleneck.
The article describes project teams waiting for multi-gigabyte files to transfer, duplicating folders and reconciling different versions, with an architecture firm’s shared building model as an example. It argues that organisations should identify where file transfers and avoidable rework cause friction before deciding how to modernise, since replacing all existing storage may be impractical. These issues will be discussed at an invitation-only executive dinner in London on 24 November, moderated by Joe Fay.
In short
- Legacy storage and VPN workflows can slow distributed teams.
- Duplicate files and outdated copies lead to extra work.
- Organisations are urged to identify workflow friction before modernising.
Steelman: both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
Modernising file infrastructure can reduce delays, version confusion and manual rework that cost teams time, especially when colleagues are spread across locations. Better collaboration tools may also improve oversight and make it easier to share large working files, while a targeted assessment can focus investment on the areas causing the most friction.
The case against
Slow transfers and version problems do not necessarily justify replacing established storage systems, which may still meet important needs reliably and at lower cost. A broad modernisation can bring expense, disruption and new management demands, so organisations may reasonably prefer incremental fixes or process changes until they can show that the benefits outweigh those costs.
Explained simply
Organisations use file systems and network-attached storage to keep shared documents and large project files, while virtual private networks let staff access them remotely. These arrangements can work well when teams are small or work in one place, but delays may arise as more people collaborate from different locations.
For example, an architecture team may need to share a large building model, and slow transfers or separate copies can make it harder to know which version is current. Staff may spend time waiting, checking files and repeating work, while managers have less visibility over how files are handled.
The challenge is to find where existing systems are causing avoidable delays and rework, then weigh changes against the cost and practicalities of replacing storage. Different organisations may face different pressures depending on the size of their files, how their teams work and what infrastructure they already have.