Three weeks in, the new hire is still asking the same things. Where’s that file? Who approves this? How do we bill this kind of work? Is it okay to tell the customer that?
The owner, or whoever sits closest, is answering for the fourth time and starting to wonder. Is this person not paying attention? Did we hire the wrong person?
Maybe. But I wouldn’t start there.
What the owner thinks is wrong
“They’re not getting it.” That’s a natural read when you’re the one being interrupted. It’s also the conclusion that’s hardest to undo if it’s wrong. If you decide it’s the person, you stop looking at everything else.
Blaming the person before checking expectations, process, training, tools and ownership skips most of the likely answers.
What I’d investigate
The questions themselves. I’d have the new hire, or the person answering, write down every question for two weeks. Just the question and who answered it. No judgment.
Then I’d sort them:
- No written answer exists. The answer lives in someone’s head.
- The answer exists but they can’t find it. It’s in a folder nobody told them about, or buried in an email from last year.
- They don’t have access. They’re asking because they literally can’t see the thing.
- Nobody owns the answer. They ask three people and get three answers, so they keep asking.
- It’s the person. They were told clearly, can find it, have access, and still don’t retain it.
That last bucket is real. But in most businesses, it’s the smallest one.
What’s probably underneath it
Usually the questions are about things the experienced people do without thinking. That’s the trap. The longer someone’s been there, the less they remember that any of it had to be learned. The answers feel obvious because they’ve been answered a hundred times, by the same few people, out loud.
If somebody has to email you four times after you send the onboarding packet, the packet isn’t finished.
What I’d change
Fix the top causes, not everything:
- The most repeated “no written answer” questions get short written answers.
- Put those answers where the work happens. In the tool, the shared drive, the job folder. Not in a separate binder.
- Fix access on day one, not when someone asks.
- For anything with three different answers, decide whose answer is right and write it down.
Then the next new hire gets those answers before they have to ask. Good onboarding answers the question the person is going to have before they have to ask it.
What I’d leave alone
I wouldn’t rewrite the whole onboarding program. That’s a big project, and big projects tend to produce documents nobody reads. I’d fix the answers to the questions people are actually asking. That’s a much shorter list and a much more useful one.
A good test after the fixes: give the next new hire the same first two weeks and keep the same log. If the questions shift from “where is it?” to “why do we do it this way?”, the onboarding is doing its job. Those are the questions you want.
The tradeoff
Logging questions feels slow and a little awkward at first. Some people worry it looks like they’re keeping score. It’s worth saying out loud that the log is about the business, not the person.
And some questions will always be legitimate. A new person should ask questions. The goal isn’t silence. The goal is that the same question doesn’t have to be answered by the same person five times.
The pattern
Repeated questions are data about the system before they’re data about the person. They show you exactly where knowledge is stuck in someone’s head, where access is missing, and where nobody ever decided on the answer.
This probably worked fine when the business was smaller and everyone sat ten feet from the owner. As it grows, “just ask me” stops scaling.
So try the log. Two weeks, every question written down. You’ll learn more about how your business actually works than most onboarding documents will tell you.
If the list shows a bigger pattern, a Systems Fit Call is a good place to talk it through.
