Sarah's first week as a marketing manager started exactly how she'd hoped. Day one brought the usual new hire rituals: laptop setup, team introductions, a tour of the office, and a manager who seemed genuinely excited to have her on board. By day three, she was ready to dive into real work.
That's when she hit the wall.
She needed to launch a product campaign, but first she had to understand the company's approval process. Simple enough, right? Her manager said, "Just ask around—someone on the product team should know." So Sarah started Slacking people. The first person pointed her to someone else. That person gave her half an answer and mentioned there was "someone in legal" who handled the final sign-off. After 45 minutes of digital detective work, she finally got referred to the actual expert, who was on vacation for two weeks.
The campaign deadline was in ten days.
Sarah had two bad options: wait and look incompetent, or guess and risk doing it completely wrong. She chose to guess, resulting in delayed campaign launch, skipped key stakeholder reviews, and a whole lot of rework.
This isn't a Sarah problem. It's a system problem that costs companies millions in lost productivity every year.
This Isn't Just "First Day Jitters"
We tend to dismiss the "who do I ask?" struggle as part of settling into a new job. A little confusion is normal, right? New hires just need time to figure out how things work.
Except the data tells a very different story.
Research shows that 49% of new hires who miss their first performance milestones never had formal onboarding training. When employees don't know where to find help or information, they're set up to fail before they've even started. And the consequences are severe: up to 31% of employees leave within their first six months, often citing unclear expectations and lack of support as primary reasons.
The problem extends far beyond the first week. Microsoft's 2024 Work Trend Index found that 57% of people struggle to find the information they need at work, and that's not just new hires. But for someone who's been at the company for three years, they've at least built up a mental map of who knows what. New employees are navigating in complete darkness.
Here's the real cost: it can take up to two years for a new hire to reach the same level of efficiency as their predecessor. During that time, the "who do I ask?" problem compounds daily. Forty-five minutes lost here, two hours there, questions left unanswered, decisions delayed. APQC research found that knowledge workers spend an average of 2.8 hours every week just looking for or requesting needed information.
For a company with 1,000 employees, that's 2,800 hours per week, or roughly $8.7 million per year in lost productivity at a conservative $60/hour loaded cost.
And the question that haunts every new employee isn't really "Who should I bother?" It's "Who actually knows this?" Those are fundamentally different questions. One assumes you're interrupting someone. The other assumes you could find the right person if only you knew who they were.
So why does this happen at nearly every company?
The Three Reasons New Hires Get Lost
Reason #1: Invisible Expertise
Companies have experts. Every organization does. There's always someone who knows the deployment process inside and out, someone who's a wizard at customer data analysis, someone who can navigate vendor contracts in their sleep.
The problem isn't a lack of expertise. It's that expertise is invisible.
Org charts show hierarchy and reporting structures, not knowledge and capabilities. Job titles indicate roles, not what people actually know. And "just ask around" only works if you already know who to ask around to, which requires the very knowledge the new hire doesn't have yet.
Seasoned employees have built mental maps over years. They know that Janet in finance is the go-to for budget questions, that Marcus in engineering can troubleshoot any API issue, and that while Sam technically manages customer success, it's really Priya who knows all the enterprise client quirks.
New hires have none of this. They see names in Slack channels and faces in meetings, but they have no idea who actually knows what. The DevOps engineer who could solve their deployment problem in five minutes? They don't even know he exists until someone casually mentions him three weeks in. Meanwhile, they've been struggling alone or repeatedly bothering people who don't have the answers.
Reason #2: Knowledge Lives in People's Heads (And Slack History)
Even when new hires get lucky and find the right person to ask, they're often met with: "Oh, we discussed this back in March. Let me try to find that thread…"
Critical information never gets documented. Important decisions get made in Slack conversations that are buried within days. Processes that should be written down exist only in the institutional memory of long-term employees. "Institutional knowledge" becomes code for "things Karen in accounting knows but never wrote down."
The new hire has two options: recreate the wheel or play knowledge archaeologist, digging through months of Slack history hoping to stumble on the right conversation.
The statistics on this are damning:
- 60% of employees say it's difficult or almost impossible to get essential information from their colleagues
- The average enterprise employee spends more than 100 minutes each day looking for the information they need to do their jobs
- In companies with 10,000+ workers, this number climbs even higher
And here's the cruel irony: the information usually exists somewhere. It's just trapped in someone's head, buried in an old email thread, or lost in a Slack channel that was busy six months ago but is now dormant. The knowledge is there. It's just completely inaccessible to the people who need it most.
Reason #3: The "Don't Want to Bother Anyone" Trap
Even when new employees have a good guess about who might know something, there's a psychological barrier that stops them from asking.
They don't want to look incompetent. They don't want to interrupt busy colleagues with "dumb questions." They're not sure if the senior engineer really has time to help someone who just started last week. They wonder if they should have figured this out already from the onboarding materials (that don't actually answer their question).
So they struggle in silence. They spend two hours trying to figure out something that would take two minutes to explain. Or worse: they make their best guess, get it wrong, and create bigger problems that take days to untangle.
Meanwhile, the so-called "expert" would have happily answered the question if they'd known someone needed help. Most people want to help their colleagues. But they can't help if they don't know help is needed.
This creates a vicious cycle: new hires hesitate to ask, so they stay confused longer, which makes them feel even more behind, which makes them even less likely to ask for help.
The worst part? Companies think they're solving this.
Why Traditional "Solutions" Don't Work
The Buddy System Falls Apart
Many companies assign new hires a "buddy" or "mentor" to help them navigate their first few weeks. It sounds good in theory. In practice, it rarely works well.
Buddies are typically assigned based on availability and general friendliness, not actual knowledge. They know some things, usually related to their specific role, but not everything. When the new hire asks about something outside their buddy's expertise, the buddy shrugs and says, "You should probably ask someone in operations."
Back to square one.
The new hire also feels guilty asking too many questions. Their buddy has a real job to do, and constantly interrupting them feels inconsiderate. Meanwhile, the buddy often feels overwhelmed. They didn't sign up to be a full-time teacher while also hitting their own deadlines.
The buddy system puts too much burden on one person and assumes that person has all the knowledge the new hire will need. Neither assumption is true.
Documentation Gets Outdated Immediately
The other classic solution is comprehensive documentation. Companies create elaborate knowledge bases, onboarding wikis, and process documents. New hires are pointed to these resources with a cheerful "everything you need is in there!"
Except it isn't. Or it was, six months ago, before the process changed. Or the tool was upgraded. Or the team reorganized. Or the vendor contract was renegotiated.
Knowledge bases require constant maintenance to stay relevant. Most companies create them with good intentions during onboarding planning, then abandon them as soon as everyone gets busy. Within months, the documentation is dangerously misleading; new hires follow outdated processes and create problems instead of solving them.
After finding wrong information once or twice, new employees stop trusting the documentation entirely. Better to figure it out themselves than to follow instructions that might be obsolete.
"That Slack Thread from 2023" Isn't a Solution
When neither the buddy nor the documentation helps, employees are often told: "Try searching Slack. I think we discussed this last year."
Finding the right thread is like finding a needle in a haystack, and the haystack is actively growing, plus you aren't entirely sure what the needle looks like.
Even when new hires successfully locate an old conversation, it's often unhelpful. The discussion lacks context. Key acronyms go unexplained. The people who participated may have left the company. Follow-up questions have nowhere to go as commenting on a year-old thread feels weird, and the person you'd want to ask might not even see the notification.
The pattern across all these "solutions" is the same: they treat knowledge transfer as a one-time event instead of an ongoing system. Buddy does initial handoff, done. Documentation gets written once, done. Important conversation happens, done.
But knowledge needs to be living, searchable, and connected to the people who have it, not frozen in time or locked in someone's memory.
What Actually Works
Companies that actually solve the "who do I ask?" problem do three things differently:
1. Make Expertise Visible and Searchable
In functional organizations, new hires can search by topic or problem and immediately find who actually knows the answer. Not "who has this job title theoretically covering this area," but "who has demonstrated knowledge through actual contributions."
This isn't about self-reported skills on a profile. It's about making expertise visible through real activity. When Janet consistently answers budget questions and her answers get recognized by colleagues, she becomes the visible expert on budgeting. When Marcus solves API problems in public channels, he becomes the go-to for technical integrations.
The impact on new hires is transformative. Instead of spending 30 minutes asking around, they spend 30 seconds searching and finding the right expert directly. Questions get answered by people who actually know. And managers stop being ‘knowledge traffic cops’, constantly redirecting questions to the appropriate person.
2. Capture Knowledge As It Happens
The best knowledge management systems don't require extra documentation work. Instead, they capture valuable knowledge as a natural byproduct of people doing their actual jobs.
When an expert answers a question in a public channel, that answer becomes searchable institutional knowledge. When a problem gets solved through discussion, that solution becomes findable for future employees facing the same issue. Knowledge accumulates organically rather than through forced documentation sessions that everyone dreads and no one maintains.
This is fundamentally different from hoping someone writes things down or digging through Slack history. Questions asked once benefit everyone who comes after. Decisions made in conversations become institutional memory. The expertise that used to walk out the door with departing employees stays accessible to the team.
New hires stop reinventing wheels and start building on the knowledge of those who came before them.
3. Create Incentives for Knowledge Sharing
In high-functioning organizations, helping others is visible and valued, not hidden in DMs or taken for granted.
When knowledge sharing happens in public spaces and gets recognized by colleagues, experts feel appreciated rather than bothered. New hires feel welcomed rather than burdensome. And the organization builds an institutional memory that survives turnover.
The key is to make helping others part of how people advance professionally. When answering questions well contributes to your reputation, when being recognized as an expert opens doors, when knowledge sharing is celebrated rather than invisible, people do more of it.
This doesn't mean gamifying everything or creating artificial competition. It means building systems where contribution is visible, recognition is meaningful, and the people who make others successful are seen and valued for it.
The best systems don't require extra work. They make knowledge sharing the path of least resistance and reward people for doing what they're already inclined to do: help their colleagues succeed.
The Long-Term Impact
When new hires know who to ask and can find answers quickly, the benefits compound over time.
Immediate Benefits:
- New employees reach productivity 40% faster.
- Managers spend less time fielding basic questions and more time on strategic work.
- Fewer costly mistakes from new hires guessing incorrectly or reinventing obsolete wheels.
Long-Term Benefits:
- Higher retention as employees who onboard well are 82% more likely to stay with the organization.
- Stronger institutional knowledge that survives employee turnover.
- Today's new hires become tomorrow's experts who help the next generation.
The Ripple Effect: A question answered once helps dozens of future employees. Experts identified early can be leveraged strategically across the organization. Companies build competitive advantage through preserved and accessible institutional knowledge, the kind competitors can't easily replicate.
Meanwhile, companies that don't solve this problem are trapped in a perpetual cycle of knowledge loss and inefficient onboarding. Every new hire starts from scratch. Every departure takes irreplaceable knowledge with it. Every quarter, productivity suffers as employees waste hours searching for information that should be at their fingertips.
The Choice Is Yours
The "who do I ask?" problem isn't a training issue or a people issue. It's a systems issue. And it's costing your company time, money, and talent.
You have two paths forward:
Option 1: Keep treating every new hire like they're starting from scratch. Continue losing 2.8 hours per employee per week to information searches. Accept that 31% of your new hires will leave within six months. And, hope that the buddy system works better next time.
Option 2: Build systems that make expertise visible and knowledge accessible. Turn casual conversations into searchable institutional memory. Help new hires find the right expert in seconds instead of hours. Stop losing knowledge when employees leave.
Modern teams are choosing option two. They're solving this by turning everyday discussions into institutional knowledge that persists. Instead of letting expertise stay hidden in people's heads and buried in Slack threads, they're building systems where the right expert is always one search away, and every answered question benefits the next person who needs it.
Pravodha helps enterprise teams capture knowledge as it happens and surface internal expertise automatically. New hires find answers in seconds, not hours, and your best people spend less time answering the same questions repeatedly.
When someone asks a question in Slack, Pravodha captures the conversation and makes it searchable forever. When experts consistently help their colleagues, they're automatically recognized for their knowledge. When new employees join your team, they can immediately find who knows what and search through the institutional knowledge you've been building, instead of starting from zero.
Ready to stop losing knowledge and start building it? Join our waitlist to see how Pravodha transforms onboarding and turns your team's conversations into your competitive advantage.