A general-purpose office network moves small files quickly and idles most of the day. An editing environment does the opposite: several operators pull sustained high-bitrate streams from the same storage at once, all day.
That changes the design inputs. Throughput per seat, storage performance under concurrent load, and cabling quality matter more than feature lists. Contention shows up as dropped frames and stuttering playback, which editors experience as the system being broken.
We size the core for concurrent streams rather than headline speeds, separate media traffic from general office traffic, and plan proxy and archive tiers so finished work leaves the expensive storage automatically.
The measure of success is boring: playback that behaves the same on a deadline Friday as it does on a quiet Tuesday.