Why Your Employees Can't Find Each Other (And What It's Really Costing You)

Someone needs to talk to the person who understands the billing infrastructure. Simple enough. But there’s no directory that tracks expertise, so it turns into three days of Slack threads and forwarded messages. By the time the right person surfaces, incorrect assumptions about how the system works have already been baked into the project, costing the team a week of rework.

The frustrating part: the expertise existed internally the whole time. Multiple people could have helped. There was just no way to know.

Past about 50 people, this becomes the norm. People aren’t unhelpful. The organization is just invisible.

How Much Time Is Actually Lost

McKinsey’s 2012 “Social Economy” report found that employees spend nearly 20% of their work week searching for internal information or tracking down colleagues who can help. The study is over a decade old, but its estimate has been widely cited since and remains consistent with more recent workplace research. Nearly a full day per week spent on organizational archaeology instead of productive work.

Even if only a fraction of that time is spent specifically on finding the right person (vs. finding documents or data), the cost adds up fast. For a 100-person company, reclaiming even two hours per person per week adds up to 10,000+ hours per year.

And it gets worse as you grow. At 20 people, everyone knows everyone. At 50, you start losing track. Once you cross roughly 150 people, most employees become functionally invisible to each other. They might share a Slack workspace, but they have no idea who knows what.

Where the Real Directory Lives

The obvious answer is “we need a better org chart.” That helps, but it’s not the full picture.

Companies manage their directory through a combination of tools that each solve the wrong problem: an HRIS that has accurate data but nobody can search, a Slack workspace where people exist but are not organized, and an org chart PDF that was accurate three months ago. None of them answer the question employees keep asking: “Who in this company can help me with X?”

The company restructures some part of its org every few months. Someone gets promoted, a team splits, a new hire starts. Documentation falls behind, and the gap between reality and what’s written down never closes.

So the real directory ends up living in people’s heads. “Oh, you need Sarah for that. She used to be on the Payments team.” This works until those tenured employees leave, go on vacation, or simply can’t keep up with the pace of change. When they’re gone, the directory goes with them. And nobody realizes how much institutional knowledge just walked out the door until the next person asks “who handles this?” and gets silence.

30 Seconds Instead of 3 Days

Imagine you just joined a 150-person company. You need to figure out who handles compliance for the DACH region. In most companies, you’d post in a Slack channel and wait. Maybe someone replies in an hour. Maybe they tag the wrong person. Maybe nobody replies and you try a different channel.

Now imagine you open the company directory, type “DACH compliance,” and see a name, a face, a description of what they work on, and a Slack handle. Thirty seconds. Done.

What makes this work is straightforward: profiles that include what people know and work on, a system that stays current without HR manually updating it every time someone moves, and a directory that’s easy enough to find that people check it before posting in Slack. The bar is low. Most companies just haven’t cleared it.

Where the Time Goes

New hires take weeks to build their internal network when there’s no directory to browse. Giving them a navigable view of the organization on day one shortens that ramp-up noticeably.

But the quieter cost is siloing. When finding someone in another department takes effort, people stop trying. They work with who they know. The classic version of this: two engineering teams independently build overlapping solutions within the same quarter because neither team knew the other was working on it. They find out at a company all-hands when someone presents their version and a hand goes up from the back of the room: “Wait, we built that too.” Weeks of engineering time, duplicated. Not because anyone was careless, but because searching for “who is working on this?” was harder than just building it yourself.

A Fix You Can Ship This Week

You can fix this problem this week. No budget approval, no vendor evaluation, no migration project. Four steps, any company size.

1. Run a quick audit

Ask five people across different teams: “If you needed help with something outside your expertise, how would you find the right person?” If the answer involves more than two steps, you have a discoverability problem. Write down the actual paths people describe. You will hear things like “I would ask my manager, who would ask their manager, who might know someone.” Count the hops. Three or more is a clear signal.

2. Build a basic skills directory

Open a new Google Sheet. Create six columns: Name, Role, Team, Email, Top 3 Skills, Currently Working On. Seed it with your own row and ask your immediate team to add theirs. Then share the sheet company-wide with edit access and a short message: “We are building a directory so you can find the right person faster. Add yourself in 60 seconds.” Most people will fill it in within a day or two if you make the barrier low enough. The “Top 3 Skills” column is the one that matters most. Titles are vague. Skills are specific. “React performance optimization” is useful. “Senior Engineer” is not.

3. Make it findable

A directory nobody can find is the same as no directory. Pin the link in your main Slack channel (or Teams, or whatever your company uses). Add it to your onboarding checklist so every new hire sees it in their first week. Include it in the welcome email. Mention it in your next all-hands. The goal is to make “check the directory” the default reflex before “post in Slack and hope someone answers.”

4. Upgrade when ready

A spreadsheet gets you surprisingly far, but it has limits. Search is clunky, there is no visual structure, and keeping it current depends on people remembering to update their row. Once you have proven the value of a searchable directory (and you will, because people start using it immediately), a CSV import into an org chart tool gives you search, visual hierarchy, and filtering for free. The spreadsheet becomes the import file. Nothing is wasted.

That billing infrastructure expert from the opening? Eventually found through a chain of Slack introductions. Three days for a question that should have taken 30 seconds with a searchable directory. Building the infrastructure so next time it does take 30 seconds is the whole point.