How to Onboard a New Hire So They Stay

The new hire started Monday. You spent forty minutes with them, introduced them around, pointed at the documentation, and said the thing everyone says: 'Take your first few weeks to get up to speed, and ask me anything.' Then a customer escalation ate your week.

By Thursday they've read every document twice, attended four meetings they didn't understand, and produced nothing. They're not going to tell you they feel useless, because week one is the worst possible time to admit you feel useless. So they wait, and you interpret quiet as settling in. Six weeks later you wonder why they seem tentative, and at month seven they leave for a role that 'was a better fit.'

'Ask me anything' pushes the entire cognitive load onto the person with the least context in the building. They don't know what they don't know, they don't know who owns what, and they don't know which questions will make them look slow. So they ask almost nothing.

The second failure is delayed contribution. Long ramp periods are meant kindly and land badly — competent adults get their sense of belonging from being useful, and every week without a real contribution reduces confidence rather than building it. The third is social: remote or hybrid, people who don't form two or three real working relationships in the first month never fully arrive, and no amount of documentation substitutes for that.

Underneath all of it: onboarding is usually designed as information transfer when it's actually about building competence, relationships, and a sense that the bet the person made in joining was correct.

Week one is orientation and one shipped thing. Week two is their first real ownership — something small with their name on it that nobody else is going to rescue. Weeks three and four are about widening the map: who owns what, where decisions get made, which conventions are real and which are habit. By day thirty they should be able to describe the team's priorities without looking anything up.

Days thirty to sixty are where competence turns into judgment. Hand them something with genuine ambiguity in it and let them make the calls, then review the reasoning rather than the output. This is also the window to correct anything drifting — a working style that does not fit, a gap in a skill you assumed, a relationship that is not forming — while correction still reads as coaching rather than as a verdict.

Days sixty to ninety are about full load and honest assessment. By day ninety, both of you should be able to answer the same two questions the same way: is this working, and what does the next six months look like. If the honest answer to the first is no, this is the point at which saying so is still a kindness to everyone involved.

By week two they are asking questions of someone other than you. A new hire who routes everything through their manager has not been connected to the team yet.

They correct something. The first time a new person says the documentation is wrong, they have crossed from visitor to member, and you should thank them loudly for it.

At thirty days they can tell you what their job is in one sentence that matches yours. If the two sentences differ, you found it in the month where it is still easy to fix.

Get something they built into someone else's hands in the first week. Not a mock task, not a training module — real output, used by a real colleague. It compresses weeks of tentative belonging into a few days, and it gives you an early, accurate read on how this person works while you still have time to shape it.