The Onboarding Problem Nobody Wants to Talk About

I am sure you’ve seen a story just like this. You hire someone. Smart person, great experience, genuinely excited to start. By the end of week two, they told you they felt like they were bothering everyone with questions.

That stuck with us. Not because it was unusual, but because it’s so common that we’ve stopped noticing it. New people join, they don’t know where to find things, they ask around, and eventually they figure it out. We call that “onboarding.” It’s really just surviving the first few weeks.

Two months of being lost

Most onboarding programs focus on the big stuff. Here’s your laptop. Here’s your email. Here’s a meeting with your manager. Here’s an overview of the company. Maybe there’s a slide deck. Maybe there’s a buddy system.

What they don’t focus on is the daily stuff. Where do I find the process for X? What’s the policy on Y? Who do I ask about Z? How do we actually do the thing I was hired to do?

New hires spend the first four to eight weeks in a constant state of low-level confusion. They can do parts of their job, but they keep hitting walls where they need information that nobody has shown them and they can’t find on their own.

Research keeps putting the cost of this somewhere painful. New employees take months to reach full productivity. The ones who have a bad onboarding experience are significantly more likely to leave within the first year. And the people around them, the experienced staff answering the same questions every time someone new joins, they burn out quietly.

It’s one of those problems that everyone experiences and nobody fixes properly.

The training gap

Here’s how onboarding usually works. In the first week, you sit through training sessions. Somebody walks you through the systems, the processes, the key information. It’s a lot to take in. You nod along, take some notes, and try to remember as much as you can.

Then training ends and real work starts. And within days, you’ve forgotten half of what you were told. Not because you weren’t paying attention. Because that’s how brains work. You can’t retain 40 hours of information delivered in a week.

So you go looking for it again. Except the training materials live in one system and the day-to-day reference docs live in another. Maybe the training was a series of PowerPoints that someone shared in an email. Maybe there’s a learning management system that you logged into once during orientation and haven’t opened since.

The knowledge you need to do your job exists. It’s just not findable when you actually need it.

The shoulder-tap tax

Every question a new hire asks costs the team time. Not much individually, maybe five minutes here, ten minutes there. But it adds up.

I manage a team of 40 people. If we hire four people a year, and each one of them asks, let’s say conservatively, five questions a day for their first month, that’s 400 interruptions. Each one pulls an experienced person out of what they were doing. Some of those questions lead to longer conversations. Some of them get answered differently by different people, which creates confusion.

And here’s the part that really bothers me: most of these questions have been asked before. The answer exists somewhere. It was probably explained to the last person who started, and the person before that. But because it wasn’t written down in a place people can actually find, every new hire goes through the same cycle of asking, waiting, and hoping they get the right answer.

We’re essentially rebuilding institutional knowledge from scratch every time someone new joins. That’s expensive, even if it doesn’t show up on a spreadsheet.

Why a wiki doesn’t solve this

“Just put it in the wiki” is the standard response. And it’s not wrong, exactly. Having a central place for knowledge is better than not having one. The problem is that wikis are terrible at onboarding.

A wiki is a flat collection of pages. There’s no structure to guide a new person through what they need to learn. No way to say “start here, then read this, then do this quiz to make sure you understood it.” No way to know if someone actually read the policy update or just marked it as done.

New hires open the wiki, see 300 pages with no clear starting point, and close it. Then they go ask someone.

What they need isn’t a pile of documents. They need a path. A structured sequence that takes them from “I just started” to “I know where to find things” in a reasonable timeframe. And after that path is done, they need the same content to be there as reference material when they forget something three weeks later.

That’s two different needs served by the same content. Training and reference. Most tools only do one or the other.

What good looks like

The best onboarding I’ve seen works like this. New person joins. They get a structured learning path that guides them through the essential content in a logical order. Each step links to an article or document that actually explains the thing. At the end of each section, there’s a short quiz or acknowledgement so both the person and their manager know they’ve covered the material.

Once the learning path is done, all of that content stays searchable. When they need to look up the refund policy in month three, it’s right there. Same article they read during onboarding. No separate training system to log into. No outdated PowerPoint to dig up.

And because the training content and the reference content are the same thing, it stays current. When the process changes, the article gets updated. Everyone benefits, not just the next new hire.

Read acknowledgements mean you can track who has read what. For regulated industries or any team that needs compliance tracking, that’s not optional. You need proof that people have read and understood the policy, not just proof that you sent them a link.

The honest bit

Perfect onboarding doesn’t exist. People will still have questions. Some things can only be learned by doing. And there will always be a period where new hires feel a bit lost, no matter how good your documentation is.

But there’s a big difference between “I feel lost because this job is complex and I’m still learning” and “I feel lost because I can’t find basic information that should be easy to access.” The first one is normal. The second one is a failure of systems, not people.

Most teams accept the second one as inevitable. It isn’t. It just requires thinking about onboarding as more than a one-week event. It’s the first three months of someone’s experience. And the tools you give them during that time shape whether they feel supported or stranded.

The new person I mentioned at the start? They’re doing great now. But it took longer than it should have. And the “bothering everyone” feeling they described? That’s the real cost. Not just the time lost, but the confidence dented. The impression formed. The quiet thought that maybe this place doesn’t have its act together.

We can do better than that.

The KnowledgeScout Team