"Does anyone have the latest version of the onboarding checklist?"
Two Teams messages. One reply with a file from 2024. A third person who thinks it's on the shared drive, under HR, or maybe Admin. Somebody finally emails it from their own desktop, and now there are two latest versions.
Five minutes, three people, one document. Now multiply that by every document your firm touches in a day.
The day a week nobody budgets for
McKinsey's estimate is that knowledge workers spend about 19 percent of their week searching for and gathering information. Call it a day out of five. In a 12 person firm that's roughly two full-time salaries spent looking for things the firm already has.
Nobody sees it as a cost, because it never shows up as a line item. It shows up as the afternoon that disappeared, the report that went out with last quarter's numbers, and the one person everyone interrupts because she knows where everything is.
I've watched this in firms of five people and in teams inside a global financial-services company, and the pattern is the same. The firm has the information. It has it six times, in six places, and nobody's sure which copy is right.
Where it all lives right now
Take a look at where a typical firm's working information sits on a Tuesday afternoon:
- Desktops and Downloads folders, one per person
- Personal OneDrives that nobody else can see
- Email attachments, forwarded and re-forwarded, each one a fork
- The shared drive or office server, with a folder structure from whoever set it up in 2016
- Teams and chat threads, where the decision was made and never written anywhere else
- A spreadsheet with six tabs that's really a database
Every one of those was a reasonable choice at the time. Together they mean the answer to "where is it?" depends entirely on who you ask.
What findable actually means
Findable is a short list, and none of it is technical:
- One home per document. The onboarding checklist lives in one place. Everyone links to it. Nobody emails it.
- Names that mean something. "2026 Client Intake Form," not "intake_v3_FINAL_Mark edits.docx."
- A few tags instead of nine folder levels. Document type, client, year. Filter, don't dig.
- The current version is obvious. Version history behind the scenes, one current file in front.
- Permissions by group, not by person. The program staff group can see program files. Add a new hire to the group and they can see everything they need on day one.
- Search that works. Which it does, once the first five are true.
Most firms already pay for the tool that does all of this. They use it as a place to dump files.
Setting it up in Microsoft 365
This is most of what I do on the Microsoft 365 side of my practice, and it's less dramatic than people expect. No migration project with a code name. A structure, then the files move into it.
SharePoint sites match how the firm is organized: one per team or function, plus one everyone reads. Inside each site, document libraries with two or three metadata columns instead of a folder tree. OneDrive syncs the libraries to every computer, so staff still see a folder on their desktop and keep working the way they did. Teams channels point at those same libraries, so the file discussed in chat is the file in the library, not a copy.
Retention policies quietly retire the 2016 drafts. Permissions get set by group once, and the shared admin login that everyone knew gets retired too.
Then the office server gets turned off. That's usually the day people notice the difference, because working from home stops requiring a VPN and a prayer.
What the workday looks like after
A new hire finds the onboarding checklist without asking anyone, because it's in the New Staff library where the site told her to look.
The person who used to be the human index gets her afternoons back. She's still the expert. She's no longer the search engine.
The "which version?" argument stops, because there's one file with a history instead of eleven files with names.
The Friday report pulls from the list that's updated all week instead of from an email chain, and it's right.
None of that is a productivity hack. It's the firm getting back the day a week it was already paying for.
Findable is what makes AI useful
Here's the part that changed the math in the last two years.
Microsoft Search already looks across SharePoint, OneDrive, and Exchange while respecting each person's permissions. Copilot can answer from your documents. A Copilot Studio agent can be pointed at a single library and answer questions from it. A Claude project can do the same with a folder of plain files. So instead of searching at all, a staff member types:
What's our process for a client who wants to change their billing date?
And gets the answer, with a link to the source document.
Ask any AI a question about your business. Does it answer like a teammate, or like a stranger who met you five seconds ago? The difference is entirely whether the firm's knowledge is organized somewhere the AI can read it. A stranger is what you get from six copies in six places. A teammate is what you get from one home per document.
AI doesn't fix messy information. If the same procedure exists in three documents with three different steps, the AI has three answers to choose from, and it will pick one with confidence. Organizing first is what makes the AI worth turning on. That's what I mean by an AI operating system: the firm's knowledge written down where the AI can read it, under the firm's own control. And once agents are reading it, they need an owner too, which is the agentic AI management side of the work.
Where to start on Monday
Don't start with the whole firm. Start with one team.
List the 20 documents they touch most. For each one, decide one home, one owner, and one name. Move those 20 into a library with two metadata columns. Point the team's channel at it. That takes about a week, most of it deciding, not moving.
Then do the next team.
Within a quarter the firm's working information has one address, the search bar returns the right thing, and the AI you're already paying for finally has something to read. The day a week comes back one team at a time.