A copied file server structure encodes decisions made for a different tool
Deep folder nesting made sense when folders were the only organising mechanism. They are not any more.
SharePoint · Small & Mid-Market
The cost of not finding things
The cost is invisible because it is distributed: a few minutes per person per day looking for things, and nobody adds it up.
Abstract
The cost of not finding things
Summary
Most growing businesses migrated a file server into SharePoint, kept the folder structure, and inherited a decade of decisions made for a different tool.
This paper argues that the resulting cost is real, distributed and therefore never counted; that the new-starter test is the cheapest way to make it visible; and that the structural fix is a redesign around how teams actually work rather than a better search configuration.
Key findings
Four things this paper argues
If you read nothing else, read these. The analysis that follows sets out the evidence for each.
The cost is distributed, which is why nobody counts it
A few minutes per person per day is invisible individually and substantial across a hundred people.
The new-starter test makes the cost visible in twenty minutes
Ask somebody who joined recently to find five common documents and time them. It makes the business case better than any assessment.
Metadata solves what folders structurally cannot
Folders encode one hierarchy. Most business documents legitimately belong in several, which is why copies proliferate.
Analysis
The argument in full
What was inherited and why it does not fit
A file server offered one organising mechanism: nested folders. Every structural decision made over a decade was made within that constraint, and the constraint no longer applies.
The consequences are recognisable in almost every migrated estate. Folder depth beyond four levels, where documents become genuinely unfindable. Multiple copies of the same document because it belongs in two places. Permissions set on individual files as the residue of one-off requests. And a naming convention that exists in a policy document and not in the libraries.
None of this was a mistake at the time. All of it is a cost now.
Making the cost visible
The new-starter test is the cheapest diagnostic available. Ask somebody who joined in the last three months to find five documents everybody uses, and time them.
Whatever they cannot find is where to start, and the exercise makes the business case more effectively than any structural review because it produces evidence rather than opinion.
The second measure worth taking is duplicate prevalence. Multiple copies of the same document mean multiple versions, and eventually a decision made from the wrong one — which is the expensive failure this whole exercise prevents.
- Time a new starter finding five common documents
- Count duplicate copies of frequently used documents
- Check folder depth: beyond four levels, findability degrades sharply
- Look for file-level permissions, which are unmaintainable and usually accidental
- Establish whether business documents live in team sites or in personal storage
Designing for how teams actually work
Sites mapped to teams or functions rather than mirroring an old drive. Metadata where a document legitimately belongs in more than one place. Permissions at site or library level rather than on individual files. Retention applied so old content is disposed of rather than accumulating indefinitely.
And an owner. An information architecture without an accountable owner degrades continuously toward the practices of whoever creates the most content, and the degradation is invisible until onboarding takes a week.
The review cadence matters too. Businesses change shape, and a structure that fitted forty people rarely fits a hundred without revision.
Framework
Something you can apply without us
Every paper in this series ends with a framework you can run internally. We would rather you used it and reached your own conclusion than took ours on trust.
Framework
Redesigning the estate
Five steps, starting with evidence rather than with structure.
1
Test
Run the new-starter test. It produces the evidence and makes the case.
2
Map
Sites to teams and functions as they work now, not as the file server was organised.
3
Tag
Metadata where documents belong in more than one place. Folders encode one hierarchy.
4
Simplify
Permissions at site or library level. File-level permissions are unmaintainable.
5
Own
A named owner and a review cadence, or it degrades back within two years.
Implications
What this means, depending on your seat
The same argument lands differently across an executive team. These are the three versions worth separating.
References
Where to check this for yourself
Microsoft's own documentation for the product behaviour described above. We would rather you verified the basis than accepted our summary of it.
01
SharePoint information architecture guidance
02
Managed metadata and the term store
03
Sharing and permissions in SharePoint
04
Retention policies and labels
05
Microsoft Search in SharePoint
On these references: each entry names a Microsoft Learn article or documentation area by title, because deep links change while titles are stable. Searching the title on learn.microsoft.com will reach the current version. Where we have cited a figure or a product behaviour, it is Microsoft's statement rather than ours; where we have given a number of our own it is labelled as such in the text.
Recognise the situation?
We will run the new-starter test with somebody who joined recently and give you the findings, which usually make the case for the work more effectively than any assessment we could write.
Discuss this paper Run the related checklist We reply to every message within one business day.
Keep reading
Related papers
The insurability of the mid-market
Insurers have quietly become the most effective security auditors in the mid-market. This paper examines what they ask, why, and what it means for how you prioritise.
July 5, 2026 · 13 pages · 14 min readRead
The mid-market ERP decision
Nobody outgrows their accounting package on a particular Tuesday. It happens through a series of individually sensible workarounds until the workarounds are the process.
February 22, 2026 · 11 pages · 12 min readRead
Build or buy the IT function
The instinct is to hire. It is not always right, and the reasoning matters more than the conclusion.
January 11, 2026 · 11 pages · 12 min readRead