The Team That Had Six Tools for Sharing Files and Used None of Them Properly
"We have too many places to put things, so nothing ends up anywhere useful."
— Operations manager, small professional services firm
The situation
She wasn't exaggerating. Over the previous few years, the team had accumulated six separate places where 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.
Six places files could live
- SharePoint — set up by IT, rarely used correctly
- OneDrive — personal files mixed with team files
- Dropbox — maintained by one person, ignored by others
- Network drive — files untouched for three years
- Email attachments — multiple versions, no single truth
- Teams channel — files posted and never found again
What we found when we mapped the workflow
Version chaos
A document drafted in OneDrive, shared by email, revised simultaneously by two people, then uploaded to SharePoint by a third who hadn't seen the email chain.
Onboarding breakdown
New staff were given a system so complicated that most people eventually gave up — which usually meant creating a seventh place for files to live.
Client risk
Sending something to a client sometimes meant attaching the wrong version. Searching for the latest file took longer than producing it should have.
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.
What we removed
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 answer was never to add another tool. It was to make a clear choice, remove the alternatives, and make the right way the easy way.
One place for everything
SharePoint became the single source of truth. Six locations reduced to one that everyone trusted and used.
Onboarding simplified
New staff could get up to speed without six months of tribal knowledge — because the system finally made sense.
The quiet stuff changed too
The low-level anxiety about whether you had the right version — the background noise — got significantly quieter.
The lesson
This isn't a story about SharePoint. It's about what happens when tools accumulate without decisions being made about how they'll be used. The time saving was real but almost beside the point. What changed most noticeably was the low-level anxiety that had become background noise — 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. None of that is visible on a productivity report. But it drains energy, quietly and constantly, in every organisation that lets it take hold.
Does this sound familiar?
If any of this resonates — the wrong versions, the chasing, the tools nobody quite trusts — it's worth a conversation. Most of the problems we fix are more straightforward than they feel from the inside.
No obligation. No hard sell. If it's not the right fit, I'll tell you.
