The Team That Had Six Tools for Sharing Files and Used None of Them Properly

The operations manager at a small professional services firm put it well during our first conversation: "We have too many places to put things, so nothing ends up anywhere useful."

She wasn't exaggerating. Over the previous few years, the team had accumulated SharePoint, OneDrive, Dropbox, a shared network drive, email attachments, and a Teams channel where files occasionally got posted and never found again. Six places files could live. Which meant, in practice, that nobody knew where anything was.

The irony was that the team weren't careless. Each tool had been adopted for a reason — Dropbox because someone found it easy, the network drive because it had always been there, SharePoint because the IT team had set it up and asked everyone to use it. The problem wasn't attitude. It was that nobody had ever made a clear decision about which tool was for what, enforced it consistently, or removed the alternatives.

So everything lived everywhere. And nobody could find anything.

When we mapped how the team actually worked, the pattern became clear. A document would be drafted in OneDrive, shared by email as an attachment, revised by two people simultaneously, and then uploaded to SharePoint by a third person who hadn't seen the email chain. The network drive held files that hadn't been touched in three years but couldn't be deleted because nobody was sure what was still needed. The Dropbox folder was being maintained by one person and ignored by everyone else.

Searching for the latest version of anything took longer than it should. Sending something to a client sometimes meant attaching the wrong version. Onboarding new staff meant explaining a system so complicated that most people eventually gave up and did whatever felt easiest — which usually meant creating a seventh place for files to live.

The fix started with a decision, not a deployment. Before touching any technology, we worked with the team to agree a simple rule: SharePoint for anything that belongs to the organisation, OneDrive for personal working drafts only. That was it. Two tools, one purpose each, clearly understood.

Then we made it easy to follow that rule. The SharePoint structure was rebuilt around how the team actually worked — not around department names or system defaults, but around the projects, clients, and processes that defined their day. Finding something became a matter of knowing where the work lived, not searching six locations and hoping.

Dropbox was cancelled. The network drive was archived and switched off. The email attachment habit took longer to shift, but once files had a reliable home, sharing a link rather than a copy became the path of least resistance.

The time saving was real but almost beside the point. What changed more noticeably was the low-level anxiety that had become background noise for the team — the slight uncertainty every time someone went to find a file, the nagging doubt about whether the version they were working from was the right one, the occasional client embarrassment when the wrong document went out.

None of that is visible on a productivity report. But it drains energy, quietly and constantly, in every organisation that lets it take hold.

The lesson here isn't about SharePoint. It's about what happens when tools accumulate without decisions being made about how they'll be used. The answer is never to add another tool. It's to make a clear choice, remove the alternatives, and make the right way the easy way.