The Real Cost of "I Didn't Know Where to Look"
Every week, someone on your team wastes 20 minutes hunting for a form, a policy, a phone number — something that exists somewhere but might as well not. They ping a coworker. The coworker doesn't know either. Eventually someone digs it out of an old email chain or asks you directly. You answer. Again.
That's not a people problem. That's a systems problem. And it's costing you more than you think.
When business owners tell me "my team doesn't know where to find information," they usually say it with a mix of frustration and resignation — like it's just the nature of running a small operation. It's not. It's fixable. But the fix has to be intentional. You can't solve it by sending another "please check the shared drive" email.
"The single biggest source of friction in a small business isn't staffing or cash flow — it's information that lives in people's heads instead of a system everyone can reach."
I've walked into home health agencies where intake staff kept critical client notes in personal notebooks. I've worked with contractors whose onboarding docs lived in five different inboxes. The chaos looked different each time, but the root cause was always the same: no single place, no clear ownership, no habit built around it.
Why Shared Drives and Group Chats Always Fail
Most teams try to solve this with a shared Google Drive or a Teams channel. That works for about three weeks. Then someone creates a subfolder with a vague name. Another person saves something to the wrong location. New hires don't know the structure exists. The drive becomes a digital junk drawer, and people stop trusting it.
Group chats are worse. A critical policy gets posted in Slack or Teams, gets buried under 200 messages, and disappears forever. Searching for it works — until someone uses a slightly different word than what was in the original message.
The Problem Is Findability, Not Storage
Here's the distinction that matters: most businesses don't have a storage problem. They have a findability problem. The information exists. People just can't reliably get to it when they need it, in the role they're in, in the moment they're working.
Good information architecture means building around how people actually look for things — not how an administrator organized a folder tree in 2021.
What "Findable" Actually Means in Practice
- A new hire can locate the answer to a common question without asking a manager
- A caregiver in the field can pull up a client protocol from their phone in under 60 seconds
- A billing coordinator doesn't need to remember which version of a form is current — the system surfaces it automatically
- When a process changes, the update lives in one place, not scattered across attachments in old emails
None of that requires expensive software. It does require a deliberate structure built for your specific team and workflows.
What Actually Works: One Home Base, Clearly Organized
The teams I've seen get this right all share one thing: a single, designated home base for information. Not a backup. Not an "official" version of something that also lives three other places. One place. Everyone knows it. Everyone uses it.
For most small businesses and home health agencies, that home base is either a SharePoint intranet or a lightweight internal portal — something with role-based navigation so a scheduler sees what a scheduler needs, and a clinical supervisor sees what they need, without wading through irrelevant content.
Structure Before Content
The mistake most owners make is dumping content into a new system before thinking about structure. They migrate the chaos. Then they wonder why it's still chaotic.
Before you add a single document, answer these questions:
- What are the five most common things your team looks for each week?
- Who needs access to what — and who shouldn't see certain things?
- What's the one question you personally answer more than once a week that you shouldn't have to?
Build the structure around those answers. Everything else follows.
AI Can Do the Heavy Lifting
One of the biggest shifts we've made for clients at Sola AI Consulting is adding an AI-powered search layer on top of their internal content. Instead of clicking through folders, a team member types a plain-language question — "what's our policy on missed visits?" — and gets the answer pulled directly from internal documents, instantly.
That's not science fiction. It's running right now in SharePoint environments with tools like Microsoft Copilot and custom-built integrations. The result: fewer interruptions, faster onboarding, and staff who actually trust the system they're working in.
Before building or migrating to any information system, audit the five questions your team asks most often. Design your navigation and search around those questions — not around how you think about your business internally. The system has to match how your people think, not how you do.
Building the Habit That Makes the System Stick
A portal no one uses is just expensive decoration. The system only works if people actually go there first — before they text a coworker, before they dig through email, before they ask you.
That habit doesn't build itself. Here's what works:
- Make it the only place. If a policy exists in the portal and also in an email attachment and also in a binder, you've created three competing sources of truth. Pick one. Remove the others.
- Train around real tasks. Don't just show people the system. Walk them through the actual task they do every day, using the system. "Here's how you find the updated intake form when a new client calls."
- Reward using it publicly. When someone finds the answer themselves instead of asking, acknowledge it. It sounds small. It's not.
- Assign ownership. Someone — one person — is responsible for keeping each section current. Without ownership, content goes stale and trust collapses fast.
I've worked with agencies where full adoption took less than two weeks once the structure was right and leadership modeled using it themselves. Culture follows leadership. If you're still answering questions that live in the portal, your team learns that the portal isn't the real answer.
The businesses that solve this problem for good stop treating information access as an afterthought and start treating it as infrastructure — as essential as their scheduling software or billing system. Once your team knows exactly where to go, and that answer is always there when they arrive, the noise drops. People get faster. You get your time back. If you're ready to build that kind of system inside your business, we can help you figure out exactly what it should look like for your team.