The new hire started three weeks ago. She's smart. She's going to be great.
She is also, right now, the most expensive thing in the building — and not because of her salary.
Every day she asks somebody four or five questions. Where do we keep the vendor W-9s. What's our policy on earnest money over $50,000. Who approves this. What do I do when the lender's portal rejects the upload. Is this normal. Each question costs the asker six to twelve minutes, once you count the interruption and the return to focus, and each question is asked of whoever is nearest and looks least busy — which is almost always your most senior, most capable, most expensive person, because that's who knows the answer.
Twenty questions a week, at ten minutes of a $70-an-hour person's time, is about $120 a week. That's not the number that hurts. The number that hurts is the sixty other times that senior person was pulled out of what she was doing, and the twenty minutes it took her each time to get back into it.
Ninety days of that, and you've spent a meaningful fraction of a senior person's quarter on onboarding — and the new hire, for her part, has spent ninety days feeling like a burden.
Why the handbook didn't help
You have a handbook. It's forty pages, it was written in 2022, it's in a folder called HR – FINAL, and it does not contain the answer to any of the questions above.
That's not because whoever wrote it was careless. It's because the knowledge that actually runs your company isn't policy — it's operational, situational, and it changes. The handbook can tell her the PTO policy. It cannot tell her that the lender portal rejects uploads over 25MB and that the workaround is to split the PDF, which everyone knows, and which is written down nowhere.
That kind of knowledge lives in three places: people's heads, old email threads, and Slack messages from fourteen months ago. All three are technically searchable and practically not, because a new person doesn't know the right words to search for. That's the definition of not knowing something.
What's actually possible now
This is one of the cleanest applications of the current technology, and it's dramatically underused at small companies.
Take everything: the handbook, the SOPs, the process docs, the closing checklists, the email threads where somebody explained something well, the Slack history, the recorded training sessions, the notes from the last software rollout. Put it into a system that can read all of it and answer questions in plain language, with citations back to the source.
Now the new hire asks the system: what's the process when the lender portal rejects an upload? And she gets the answer, and a link to the thread from last March where somebody figured it out.
She doesn't interrupt anyone. She doesn't feel stupid. She gets an answer in fifteen seconds instead of waiting until someone's free.
The two rules that make it work
Cite everything. An answer without a source is a liability, especially in any business with a compliance dimension. She needs to be able to see where the answer came from and how old it is, because a 2021 answer about a state disclosure requirement may be actively wrong now. The system's job is to find the source; her job is to judge it.
Capture the gaps. This is the part almost everyone skips, and it's what turns a nice tool into a compounding asset.
When the system can't answer, log the question. Every week, someone looks at the unanswered list. Those questions are exactly the institutional knowledge that exists only in someone's head — and now you have a prioritized list of what to write down, generated by real demand instead of by a documentation project nobody wanted to do.
Within six months, the unanswered list goes quiet, and you have something you have never had: a company that knows what it knows.
What this is really protecting against
The new hire is the visible cost. The invisible one is worse.
At a twenty-five person firm, an enormous amount of what makes the company work exists in the heads of three or four people. Everyone knows this. Nobody does anything about it, because writing it down is a project with no deadline, and there is always something on fire.
And then one of them leaves. Not dramatically — she gets a better offer, or she moves, or she retires. And you discover, over the following six months, exactly how much of the business was living behind her eyes. The workarounds. The vendor relationships. The reason you stopped doing it the other way in 2019.
That's an existential risk to a small company, and it's the kind of risk that never makes it onto a risk register because it isn't an event, it's an erosion.
What your senior people do instead
They stop being a helpdesk.
Right now, your best operator is fielding eight interruptions a day, each of which is trivially answerable and none of which is her job. She's good about it — she'd never complain — and she is being systematically prevented from doing deep work by the very fact that she's the person everyone trusts.
Take the interruptions away and she gets her focus back. And she gets something else: she gets to teach the interesting things. The judgment calls. The "here's how you read this client." The part of mentorship that's actually mentorship, rather than being a search engine with a pulse.
Your company already knows the answers. It just can't tell anyone.