Why Your New Hires Keep Asking the Same Questions

Every new hire at your company asks the same questions during their first month. You've seen the pattern. "How do I submit an expense report?" "Who approves time-off requests?" "What's the actual process for X?" (Not what the handbook says — the actual process.)

The person answering these questions has answered them four times this year already. Maybe twelve times since they started. They're patient about it, or they're not, but either way it's the same information being transmitted one-to-one, over and over, through conversation.

This is a systems failure, not a people failure.

The onboarding doc problem

Most companies have some version of onboarding documentation. A Google Doc from 2022. A Notion page someone started and abandoned. A Confluence space with 40 pages, 35 of which are outdated.

The documentation exists. It just doesn't work. Here's why:

It covers the wrong things. Onboarding docs tend to focus on policies and tools. "Here's how to set up your email. Here's our PTO policy. Here's the org chart." That's fine for day one. But the questions new hires actually have are about processes, not policies. How does this really work? Who should I actually go to for this? What's the thing everyone knows but nobody told me?

It's too generic. Every role has specific knowledge requirements. The onboarding doc covers general company stuff. The role-specific knowledge — the stuff that actually determines how quickly someone becomes productive — is nowhere.

It's stale. The process changed six months ago. The doc didn't. Now the doc is worse than nothing because it's actively wrong. The new hire follows the old process, makes a mistake, and someone has to fix it and explain the new way. That's negative value from documentation.

What repetitive questions actually tell you

Each repeated question is a signal. It's pointing directly at a gap in your captured knowledge. Track the questions your new hires ask for one month and you'll have a perfect map of what needs to be documented.

The usual suspects:

Process questions — "How do I actually do X?" (the real way, not the handbook way)
Context questions — "Why do we do it this way?" (the backstory nobody writes down)
Exception questions — "What do I do when Y happens?" (the edge cases)
People questions — "Who handles Z?" (the unofficial org chart)
Tool questions — "Where is the thing in the system?" (the specific clicks, not the overview)

Every one of these represents knowledge that lives in someone's head but hasn't been captured in a way that's accessible to new people.

The fix isn't more documentation — it's better extraction

You don't need a bigger wiki. You need to actually pull the knowledge out of the people who have it.

The problem with traditional documentation is that it asks experts to translate their knowledge into written form. Most people are bad at this. Not because they're bad writers, but because expertise is hard to articulate. The things you do automatically — the shortcuts, the judgment calls, the "I just know" moments — are exactly the things that are hardest to write down.

Conversation works better than writing for the same reason that a good interview reveals more than a questionnaire. Follow-up questions surface things the expert didn't think to mention. "You said you check the report first — what are you looking for specifically?" "What happens if that number looks wrong?" "How often does that actually happen?"

That's what tools like Understudy do. Instead of asking your team to write, it asks them to talk. An AI interviewer guides the conversation, asks the follow-ups, and turns 15 minutes of dialogue into a structured playbook that answers the questions your next hire would have asked.

The compounding cost

Every time a new hire asks a question that's already been answered for someone else, you're paying for the same knowledge transfer twice. Or five times. Or twenty.

A 30-person company hiring 5 people a year, where each new hire asks 20 questions that take an average of 10 minutes to answer — that's over 16 hours of senior employee time per year, spent repeating information that could have been captured once.

That's the direct cost. The indirect cost is worse: the senior people get annoyed, the new hires feel like they're bothering people, and the implicit message is "figure it out yourself." Some do. Some figure out the wrong thing.

Start with the top 5

You don't need to capture everything. Start with the five questions every new hire asks. Get your most experienced person to do a 15-minute Understudy interview about each topic. That's 75 minutes of total effort. In exchange, every future new hire has answers before they need to ask.

The questions will keep coming. But they'll be new questions — signs that your new hires are getting deeper into the work, not stuck at the starting line.

Related Resources

See how Understudy compares: