Your new hire learns the job from old chats

TL;DR

• Your new hire is slow because the job is not written anywhere. It lives in old chats, in one person's head, and in habits nobody explained.

• Research puts time to full productivity at about eight months for a new hire.

• A 2018 survey of 1,000 respondents found 42% of institutional knowledge is unique to the person in the role.

• Fix it by writing the job down once, in the place where the work actually happens.

• Start with the five jobs your new hire will do in week one, not a full manual.

You hired someone good. Two weeks in, they are still asking you simple questions. Not because they are slow. Because every answer lives somewhere they cannot reach.

The price list is in your head. The client history is in an old chat. The way you handle a difficult client is a habit you built over years and never wrote down. So your new hire does what anyone would do. They scroll old chats, they guess, and they come back to you for the next answer.

This is not a hiring problem. It is a storage problem. The job has no home, so the new person has to rebuild it from fragments while doing it live.

Why does a new hire take so long to get useful?

Because they are learning two jobs at once. The first is the work itself. The second is where everything lives.

On day one they need to know who the clients are, what stage each job is at, who owes what, and which client needs a call before an invoice goes out. None of that is in one place. Some of it is in a sheet. Some of it is in chat. The rest is in your head or in the head of the person who did the job before them.

So they shadow you. They watch, they take notes, they ask. And every time you answer, you stop your own work. This is the same trap as every small decision waits for you. When you are the only source of answers, hiring does not free your time. It adds a second job: teacher.

Research backs up how long this drags on. SHRM, citing Harvard Business Review research, puts time to full productivity at about eight months for a new hire. That number is for larger companies, but the shape holds for a small team too. A person who has to hunt for every answer stays slow for months, and the founder stays interrupted for months with them.

What is actually missing when the job lives in chats?

Not effort. Not talent. A record.

A chat is a timeline, not a system. You can search it, but you cannot see the current state of a job in it. You cannot see what is done, what is pending, and who owns it. The answer is somewhere in the chat is not a joke about bad search. It is the daily reality of a team that runs on chat.

Three things go missing first. The steps: what happens first, second, third for a standard job. The exceptions: which client gets handled differently, and why. And the history: what was promised, what was already tried, and what the client already said no to.

When those three live only in memory, your new hire learns the steps by making mistakes, learns the exceptions by breaking one, and learns the history by asking the client to repeat themselves. Clients notice that too. They can tell when the person talking to them does not know what happened last time.

This is also why your team never opened the app hurts twice. A tool nobody uses cannot hold the job. And a job with no home keeps falling back to chat, where the next new hire will have to dig it up all over again.

What does slow onboarding really cost?

Time first. A 2018 survey of 1,000 respondents by Panopto, reported by Dactic, found that 42% of institutional knowledge is unique to the person in the role and not shared with coworkers. The same report put the time knowledge workers lose waiting for information, or recreating what already exists, at 5.3 hours a week. That is not one person's problem. It is every person on the team, every week, paying a tax for knowledge that was never written down.

Then there is the bigger number. Research cited by Manual.to estimates that 70% of critical operational knowledge is tribal: never written down, never formally taught, and at risk of being lost when the person holding it leaves. That is the real risk hiding inside slow onboarding. If the person who knows the job leaves before the new hire has learned it, there is nothing left to learn from. You cannot take a day off is the small version of this. A departure with no written job is the large version.

And there is a cost to the new hire too. People who spend their first month guessing do not feel trusted, and they do not stay sharp. SHRM research finds 50% greater new hire productivity where onboarding is standardised. Standardised does not mean corporate. It means the new person gets the same clear steps, the same job list, and the same answers, instead of a different version depending on who they asked.

How do you move the job out of people's heads?

You do not write a manual. Manuals sit in folders nobody opens. You write the job into the place where the work happens, one job at a time.

Pick the five jobs your new hire will do in week one. For each one, write down the steps in order, the standard outcome, and the one or two exceptions that actually happen. That is it. Not the history of the company. Not every edge case. Five jobs, written plainly, in the system your team already opens each day.

Then change one rule: the written steps are the source. If the steps are wrong, you fix the steps, not just tell the person the right answer in chat. Every correction improves the job for the next hire too. After a month, the written jobs cover most of the week. After three months, a new hire can start a standard job without waiting for you.

This also fixes the follow-up problem at its root. Nobody owns the follow-up happens when follow-ups live in memory. When a job has written steps and a named owner, the follow-up is visible to everyone, including the newest person on the team.

What should the first week look like in one system?

Day one: the new hire sees their jobs, their clients, and the current state of each job, without asking anyone. Day two: they do a small standard job end to end, following the written steps, and you check the result, not the process. Day three: they handle a client message with the history in front of them, so they do not ask the client to repeat the story.

By the end of week one, they should be able to answer three questions without you: what is pending, who owns it, and what happens next. If they cannot, the job is still in your head, and week two will look exactly like week one.

The test is simple. Go quiet for one morning. Do not answer questions until lunch. If work moves, the job has a home. If everything waits for you, it does not. That test tells you more than any training feedback form.

What if your team is only two or three people?

Then this matters more, not less. In a big company, a slow hire is a cost. In a small team, a slow hire is half your capacity stuck in training, and you are the trainer.

You do not need a training department. You need one page per standard job, kept where the work is done, updated when the job changes. Start with the job your new hire does most. Write it today, in plain words, as you would explain it on a call. Tomorrow, when they ask, point to the page instead of answering from memory. The first time feels slower. The tenth time, it is the reason you finally get your mornings back.

A business that can train a new person without the founder in the room is a business that can grow. A business where every new hire has to learn from old chats will stay exactly the size of its founder's memory.

Start with one job. Write the steps. Put them where the work happens. Your next hire will thank you, and so will the one after that.

Frequently Asked Questions

My new hire shadows me. Is that not enough?

Shadowing teaches what you do, but it does not leave anything behind for the next person. It also teaches only what happened on those days, not the exceptions that happen once a month. Written steps plus shadowing work well together. Shadowing alone means every hire starts from zero again.

How detailed should the written steps be?

Detailed enough that a good new hire can do the job without calling you, and no more. Steps, the standard outcome, and the common exceptions. If the page reads like a legal document, nobody will use it. If it skips the tricky step, the new hire will still call you about that step.

What if the job changes all the time?

Then the written steps change with it, the same day, before the next person does the job. A page that lags behind reality is worse than no page, because your team will trust it and do the old job with confidence. One update habit matters more than one perfect first version.

Should I write everything down before I hire?

No. Write the five jobs the new hire will do in week one, then add jobs as they come up. A full manual written before anyone starts is usually wrong in the details and too long to read. A short set of real steps, grown from real work, stays accurate because it is used every day.

What if my new hire still asks me everything?

Check whether the answers actually exist in writing, in a place they can reach. Most of the time, the page is missing, out of date, or buried in a folder nobody opens. Fix the page first. If the answers are there and easy to find, then it is a coaching conversation, not a systems problem.