The Questions Your New Hire Will Ask in Week One

Picture the end of a new office manager's first Friday. The owner has spent more of the week answering her questions than running the business. Not because she's slow. Because the answers were in his head and in the last person's inbox, and nowhere else.

That's the week-one problem in a small company. The new hire is smart and willing. The procedures, if they exist, cover the easy ten percent. Everything else turns into a question, and every question walks to the owner's desk.

I've watched enough of these first weeks to know the questions aren't random. They fall into a handful of buckets, and most of them can be answered before the person starts. Here's what they are and where the answers are hiding.

It isn't the login questions that cost you

Owners tend to prepare for the mechanical questions: how do I get into the accounting system, where's the printer, what's the Wi-Fi password. Those are real, but they're cheap: you answer each one once.

The expensive questions are about judgment. "The Henderson account is asking for net 60 again. Do we do that?" "This vendor says Thursday, but their email says Friday. Which do I tell the customer?" "Someone wants a quote revised for the third time. Is there a point where we stop?" The new hire can't look those up. The person who used to know the answer is gone, and the written procedure says "all accounts are net 30," which was true until it wasn't.

Gallup's research on onboarding found that only 12% of employees say their company does a good job of onboarding, and the authors note that in most jobs it takes a year or more for people to get fully up to speed. In a 15-person company you can't afford a year. Most of that time is the new hire learning, one question at a time, how the work actually flows.

The five buckets

Across front desk, customer service, estimating, scheduling and office-manager roles, the week-one questions sort into five groups. If you can answer these in advance, you've answered most of what's coming.

Who's who. Which customers matter most, who the difficult ones are, who at each account actually makes decisions, and how each of them likes to be talked to. "Dave wants a one-line answer; Maria at the city wants everything in writing." New hires reconstruct this by trial and error, and some of the errors cost you a customer.

What do we do when. The exceptions. Every business has a stated process and a real process, and the gap between them is where the new hire gets stuck. When do we waive the deposit? Who gets a rush order without a rush fee? Which late payers get a reminder and which get a phone call? The last person knew. They probably never wrote it down.

Where is it. Not the files on the shared drive, but the answers that lived in email: the latest pricing from a supplier, the version of the contract we actually use, the fix for the recurring problem with a particular product. The new hire will ask, and the honest answer is often "search the old inbox."

Who's slow. Which vendors need to be chased, which hand-offs inside the company stall, and what "I'll get right back to you" really means from each of them. New hires promise customers dates based on what vendors say, then learn the hard way which vendors mean it.

What did the last person promise. Open loops. The quote that was supposed to go out Monday. The customer who was told someone would call. The credit that was approved verbally. These are the questions that arrive as angry phone calls in week two.

What week one actually costs

Here's a rough way to put a number on it. Say your new hire asks fifteen questions a day in the first week, and each one takes you about four minutes to answer, including the time it takes to get back to what you were doing. That's an hour of your day, every day, for a week, and it doesn't stop at the end of the week. It tapers. Call it a conservative twenty hours of owner time over the first month, and that's before counting the mistakes made on the questions they didn't ask.

Those numbers are an illustration, not a study. But the direction is backed up by research on how knowledge moves inside companies. A workplace knowledge survey of about 1,000 U.S. employees found that 42% of institutional knowledge is unique to the employee in a role and not shared with coworkers, and that 60% of employees find it difficult or almost impossible to get vital information from colleagues. In a five-person office, the person who left may have been the only one who knew how a third of the job worked.

And new hires feel it. In a 2025 survey of more than 1,100 recently hired U.S. employees, 27% named being overwhelmed with new information as a top onboarding challenge, and clarity about the role and expectations was one of the three biggest drivers of feeling they belonged. Nearly four in ten had second thoughts during onboarding. A new hire who can't get answers is a new hire who starts looking around.

Where the answers already are

The good news is that for email-heavy roles, almost every one of those five buckets has a written record. The departed employee's mailbox holds the customer conversations, the exceptions as they were made, the vendor delays, the pricing threads and the open promises. It's complete and it's honest. It's also far too big to read.

You have three ways to get the answers out of it before the new hire starts.

Ask the person who's leaving. Worth doing, with limits. People don't know what they know. If you ask someone to list every exception they made last year, they'll give you four and forget forty.

Go through the inbox yourself. If the role was small and the mailbox is a few thousand threads, an evening with the search bar gets you a long way. Search for the names of your top twenty customers and read the last few threads with each. Search "deposit," "net," "rush," "exception" and "just this once." Search "waiting on." You'll find the patterns. You'll also run out of evenings before you run out of threads.

Have an AI read all of it. This is the part that's new. An AI model can read every thread in a mailbox, group them by what they were about, pull out the exceptions, the slow vendors and the open loops, and write them up in plain language. It takes a few days rather than a few weeks, and it doesn't skip the boring threads where the real patterns hide. That's what the AI Exit Interview does, and I wrote about what it looks at and what it leaves out earlier.

Whichever route you take, the output should be the same thing: a day-one document organized around the five buckets. One page of who's who and how to talk to them. One page of the real process and the real exceptions. A short list of vendors to chase and how. Every open promise with a date and a name. Hand it to the new hire on Monday morning and the questions that reach your desk drop to the ones that need you.

One more thing the record will show you

When you go looking for the answers, you'll find some you don't like. Exceptions that became habits. A customer who's been getting net 60 for three years because nobody said no. A vendor that's been late on every order since spring. A quote process with two extra steps nobody remembers adding.

A new hire starting is the one moment when nobody is attached to those habits yet. Fix them now and the new person learns the right way from the start. Wait, and in six months they'll defend the workaround as "how we've always done it." Gallup's research found that when the manager takes an active part in onboarding, new hires are 3.4 times as likely to say it went well. Deciding what to fix before you train someone into it is the most useful part of that role.

The next step

If you're hiring into an email-heavy role right now, and the last person's mailbox still exists, do one of the three things above before the start date. Even the search-bar version beats answering fifteen questions a day for a month.

If the mailbox is big, or you want the open loops and exceptions found rather than hoped for, the $250 AI Exit Interview turns it into that day-one document in a few business days. Either way, the goal is the same: your new hire's first question should be a new one.