Blog / Tech, New & Old /

Then vs now: sharing files at work

Say it’s the mid-1990s. You’ve finished a report and your colleague needs it by lunch. You copy it to a floppy disk, walk it across the office, and hope the disk isn’t one of the ones that have gone bad. When she hands it back with changes, you now have two files with the same name and no idea which one is right.

That scene is gone, but the problem underneath it, who has the latest version, is exactly the one we still fight. Here’s how file sharing changed, step by step, and which lessons haven’t expired.

Stage one: sneakernet

“Sneakernet” is the joke name for moving files by carrying storage media on foot. Floppy disks held about 1.44 megabytes, which was fine for a document and useless for a photo album. Later, Zip disks and writable CDs held more, and USB flash drives from the early 2000s made it cheap and fast to carry large files in a pocket.

What it did well. It worked without a network. It was simple, and you knew exactly who had the file, since you were holding it.

What went wrong. Disks failed and viruses spread by passing between computers. Copies multiplied, and nobody knew which was current.

Stage two: the office network and shared drives

In many offices, computers were connected to a file server. A shared drive appeared as a letter on your machine, and everyone could open the same folder. Access could be set by person or team, and the IT department took backups.

What it did well. One place for the files, backed up properly, with access rules. For a team in one building, it worked well and many offices still use it.

What went wrong. You usually had to be on the office network. People still copied files to their desktops to work on them, and the “real” copy drifted away. Folder structures grew into deep mazes that only one person understood.

Stage three: email attachments

Email arrived in offices in the 1990s and soon became the default way to pass a document around. Attach, send, done. For most workplaces, it still is the default for many one-off files.

What it did well. Everyone had it, and it came with a message and a timestamp. It worked outside the office.

What went wrong. The famous result: report_v2_final_FINAL_revised2.docx. Five people reply with five versions, and somebody has to merge them by hand. Mailboxes had size limits, and large attachments bounced. Sensitive files sat in inboxes forever.

Stage four: FTP and the web

For larger files, and for people building websites, FTP (file transfer protocol) let you upload to a server and give someone the address. It was the backbone of how websites were published for years. A lot of web work in the 2000s was dragging files into a window. Web-based file sharing services followed, offering links to download big files.

Stage five: cloud storage and live documents

Dropbox launched in 2008, and its pitch was simple: a folder that syncs everywhere. Google’s online document tools, which grew out of acquisitions in 2006, let several people edit one file at the same time in a browser. Google Drive launched in 2012, and Microsoft later moved Office towards cloud storage and shared editing.

What it did well.

  • One file, many editors. Instead of sending copies, you send a link, and everyone works on the same document.
  • Version history. You can see who changed what and restore an earlier version.
  • Access from anywhere. Phone, laptop, home or office.
  • Permissions. View, comment or edit, set per person.

What goes wrong.

  • Sprawl. Everyone creates folders, and nobody can find anything.
  • Permission mistakes. “Anyone with the link can view” is convenient, and a classic way to leak documents.
  • Dependence on connection. If your data is slow or expensive, or power is unreliable, a cloud-first workflow is harder, something that’s familiar in many places, including Nigeria.
  • Ownership. When someone leaves, their files can disappear with their account.

Stage six: chat tools and everything-in-one workspaces

Tools such as Slack and Microsoft Teams gather files, messages and meetings in one place. You drop a file into a channel and the conversation about it sits beside it. That’s convenient, but files become buried in chat history unless there’s a clear place for the final versions.

What the old ways still teach

  1. One source of truth. Whatever the system, decide where the current version lives. Everything else is a copy.
  2. Naming matters. A clear pattern (project, subject, date) beats creative filenames. When version history exists, use it instead of putting versions in the name.
  3. Backups are not sync. A synced folder copies deletions and mistakes everywhere. You still need a real backup; then vs now: backing up your files goes through the difference.
  4. Control access on purpose. Review who can see what, particularly with shared links.
  5. Plan for leavers. Files belong to the organisation, not to one login.

A simple setup for a small team

  • One shared drive or workspace with a short, agreed folder structure.
  • Live documents for anything that several people edit; attachments only for final, read-only copies.
  • A filename pattern written down in one line.
  • Permissions reviewed every few months.
  • A separate, tested backup.

If you run websites for clients, add a rule that files with passwords or personal data never travel by email.

Key takeaways

  • File sharing moved from floppy disks to shared drives, email, FTP and finally cloud documents.
  • Each step solved a problem and created a new one, mostly about versions and access.
  • The core question hasn’t changed: where does the current version live?
  • Sync is not backup.

Where does the “final” version of your most important document live right now, and would a colleague find it?