As a long term support guy, with a lot of Mac experience, I've also got a lot of experience of dealing with creative people. They tend to assume that because a way of doing things works for them, it will work for everyone.
I'm not actually singling out the creative industries here, as a lot of users from all industries do this, but my experience is with the creative industries.
A few times I've had to stop users using their own budgets to buy Mac Minis, with USB drives to stick in the corner of the office, and use as a file server..
The correct procedure if you want a shared area is to prepare a business case, then request it from a our systems team, who, assuming they grant the request, will ensure it is properly backed up etc.
The lack of thought for enterprise situations often extends to the design of the hardware/software they use..
I've seen a *lot* of design software that cannot be easily installed automatically, often not supporting any form of command line silent install, and having copy protection that is tripped by any attempt at a snapshot based installed (I don't like doing these anyway, as they can cause problems, but sometimes you have no choice).
I've also seen some applications that require Administrative rights over the machine to run, despite not doing anything that *should* require admin rights.. In my experiences, this is usually because they need to write to their own installation folder. I had to deal with one DVD authoring system (which was a low end professional system, not consumer) that insisted on storing user projects, and all their media in a Library, the files for which were in the Application install folder.. This had two problems. First, it needed write access to it's own folder, which is a no no.. The second is that users used our computers on a first come first served basis, so we couldn't guarantee that any given user would have the same computer they had last time, so they wouldn't necessarily have access to their projects.
I could resolve the Admin rights one easily enough.. Just reset the permissions on the Library folder to give users full control (modify did not work), but that does not solved the missing projects problem. I probably could have resolved that by moving the folder elsewhere (perhaps to a server) and replacing the library folder in the install with a symbolic link, but that would have introduced other problems, such as file locking and possibly corruption. Thankfully, after a couple of years, Adobe released the first version of Encore, and I was able to persuade the users to switch to that. Encore had it's own problems, but it did work better in our environment.