You’ve been stuck on a problem for two hours. You know the answer exists somewhere inside your company: someone built this system, someone made this decision, someone dealt with this exact situation before. You just have no idea who that someone is.
So, you guess. You ping the person whose name came up in a meeting last week. They don’t know, but they point you to someone else. That person is helpful but not quite right. By the end of the day you’ve interrupted three people, scheduled a call you didn’t need, and burned most of the afternoon on a question that should have taken ten minutes.
If this sounds familiar, you’re not bad at your job. You’re working in a system that was never designed to help you find expertise quickly. And in large companies, that system failure has a significant cost.
This post is about why finding the right person to ask is so hard in large organizations, and what actually makes it easier.
Why Large Companies Make Expert Discovery So Hard
In a ten-person startup, you know what everyone knows. You sit near them, you overhear their conversations, you see what problems they solve. Expertise is visible by default.
Scale that to two hundred people and the picture changes completely. Teams splinter into specializations. People develop deep knowledge that never gets written down anywhere. A senior engineer might be the only person who truly understands how a particular system was architected, but nothing in the company directory tells you that. A customer success manager might have spent months developing nuanced knowledge about a tricky client segment, but that New employees, who need expert access the most, have the weakest networks and therefore the least ability to find the right person. Senior employees, who are most likely to hold rare expertise, get interrupted constantly by people who had no better option than to guess that they might know the answer.
The Real Cost of Asking the Wrong Person
It’s tempting to treat this as a minor annoyance. A few wasted messages, a slightly longer time-to-answer. But the numbers tell a different story.
Research on workplace interruptions consistently shows The cost isn’t just the time spent answering a misrouted question. It’s the deep work that doesn’t happen on either side of that exchange.
For the person asking, the cost is slower progress, more frustration, and a growing learned helplessness around finding internal expertise. Many employees eventually stop trying to find the right person and just schedule a meeting instead, pulling in everyone who might possibly know, rather than the one person who definitely does.
For the expert who gets interrupted, the cost is even higher. The most knowledgeable people in any organization tend to become de facto human search engines, fielding the same questions repeatedly because there’s no other way for colleagues to surface their expertise. Their time gets carved up into fragments, their deep work suffers, and eventually many of them stop responding to cold pings at all, which makes the discovery problem even worse for everyone else.
Why Job Titles and Org Charts Don’t Help
The obvious answer to “how do I find the right person to ask” is “look at the org chart.” But anyone who’s worked in a large company knows how quickly that breaks down.
Job titles describe roles, not expertise. The person whose title says “Senior Engineer, Platform” may or may not be the right person to ask about the billing module. The “Customer Success Manager” title tells you nothing about whether that person has the specific knowledge you need about a particular integration. Org charts are snapshots of reporting structure, not maps of knowledge.
Directories and internal wikis fare only slightly better. They capture what someone’s job is supposed to be, not what they actually know. And they go stale almost immediately. The person listed as the owner of a system may have moved teams six months ago. The skill listed in someone’s profile may have been added during onboarding and never updated.
The deeper problem is that formal systems capture self-reported expertise, which is unreliable in both directions. Some people overstate their knowledge. Many more undersell it, listing only the skills they were hired for rather than the broader expertise they’ve built through doing the actual work. The result is a directory that’s simultaneously inflated and incomplete.
What Actually Works: Five Approaches
Given that formal systems fail, what do experienced employees actually do when they need to find the right person?
The most reliable approach is to start with the work itself, not the person. Rather than asking “who knows about X?”, ask “where has X been discussed or decided?” If your company has searchable channels in Slack or another tool, searching for the topic often surfaces not just the answer but the people who contributed to the conversation. Those people are your starting point.
The second approach is to ask in public rather than in private. A question posted in a relevant team channel or public Slack channel reaches more potential experts than a direct message to one person. It also creates a searchable record that helps the next person who faces the same question. The downside is that it requires knowing which channel is relevant, which itself assumes some knowledge of how the organization is structured.
Third, use warm introductions whenever possible. Rather than cold-pinging a name you found in a directory, ask someone you already know to point you toward the right person. This works partly because internal networks contain implicit knowledge about expertise that no directory captures, and partly because a warm introduction dramatically increases the chance of getting a timely, helpful response.
Fourth, look at who has been cited or thanked in documentation, meeting notes, or past decisions in the relevant area. The people whose names appear repeatedly around a topic are often the de facto experts, regardless of their formal title.
Fifth, for repeated patterns of expert-finding in a specific domain, invest once in building the relationship rather than repeatedly making cold contact. A fifteen-minute conversation with the right expert, used to understand both the answer to your current question and how to find related answers in the future, is worth far more than five separate cold pings over the following months.
The Systemic Fix: Making Expertise Visible
The five approaches above work. But they share a limitation: they require the person seeking expertise to do significant detective work every single time. They treat expert discovery as an individual skill problem rather than an organizational infrastructure problem.
The more durable solution is to make expertise visible at the organizational level, so that finding the right person to ask requires a search rather than a social investigation.
This means capturing expertise not through self-reporting, which is unreliable, but through demonstrated contribution. When someone answers a question, explains a decision, or walks through a process in a Slack conversation, that exchange contains real evidence of expertise. If that exchange is captured, attributed, and made searchable, it becomes a permanent signal that this person knows this domain. Over time, a picture emerges of who actually knows what across the organization that is built from evidence of real work rather than from job titles or self-submitted profiles.
Peer validation matters here too. When a colleague bookmarks someone’s explanation or explicitly recognizes their contribution as valuable, that signal carries weight that a self-reported skill tag cannot. The people who consistently receive peer recognition for contributions in a domain are, almost by definition, the ones worth asking about that domain.
This is the logic behind Pravodha’s approach to expertise discovery. Rather than asking employees to maintain skills profiles or managers to maintain directories, Pravodha surfaces expertise through the Slack conversations where knowledge is already being created and shared. Contributions get captured, attributed, and peer-validated. The result is a living map of organizational expertise that updates itself as work happens, rather than a static directory that goes stale the moment it’s published.
When someone needs to find the right person to ask, they search by topic rather than by name or title. The people who surface are the ones whose contributions have been recognized by their colleagues in that area, not the ones with the most senior titles or the loudest profiles.
What This Looks Like in Practice
Imagine you’re a product manager who has just joined a 300-person company. You need to understand how a legacy pricing system works before a customer call tomorrow morning. You don’t know who built it, you don’t know who’s touched it recently, and the internal wiki has a page that was last updated two years ago.
In most companies, your only options are to post in a general channel and hope the right person sees it, ask your manager who to talk to and wait for a response, or look through the org chart and make an educated guess.
In a company with a working knowledge infrastructure, you search for “pricing system” and find a Slack thread from four months ago where a senior engineer explained exactly how edge cases are handled. That engineer’s name is attached to the explanation, their expertise in that area has been recognized by three colleagues who bookmarked the thread, and their current Slack status shows they’re online. You send one targeted message with enough context to make it easy to respond. You have your answer before the day is out.
The difference isn’t luck or a better internal network. It’s that the organization captured the knowledge when it was first created, rather than letting it disappear into the Slack archive.
The Right Person Is Already in Your Organization
Almost every large company has the expertise it needs to answer most of the questions its employees are asking. The knowledge exists. It was created when someone solved this problem the first time, explained this system when it was built, or worked through this exact situation with a client last quarter.
The challenge isn’t a shortage of expertise. It’s that the expertise is invisible. It lives in people’s heads, in forgotten Slack threads, in the institutional memory of employees who may have already moved on. Finding the right person to ask requires either an unusually good internal network or a significant investment of time that most employees don’t have.
The organizations that solve this problem won’t do it by asking employees to fill in better skills profiles or by building more elaborate org charts. They’ll do it by capturing expertise at the moment it’s created, validating it through the people who use it, and making it searchable for everyone who comes after.
When that infrastructure exists, finding the right person to ask stops being a social puzzle and starts being a search.
That’s the kind of organization Pravodha is built to help create. If your team is losing hours every week to the expert-finding problem, we’d like to show you what a working knowledge infrastructure looks like.