How to onboard a new team member

Nobody quits in week one. They decide in week one and quit in month seven, by which point the story has become 'it wasn't the right fit': comfortable for everyone, true for nobody. What follows needs no budget, no HR platform and nobody's permission.

Before they arrive: the week you actually control

The single biggest predictor of a good first day is whether anyone prepared for it. Do these five things before they walk in, in this order.

1. Write the 90-day plan down. One page. Three headings: what you'll learn by day 30, what you'll own by day 60, what you'll deliver by day 90. It will be wrong in places. Write it anyway, and say so.
2. Chase access yourself. Laptop, logins, pass, calendar invites, the seventeen tools nobody remembers. 'IT is working on it' on day one tells a new person exactly how much this place plans ahead.
3. Name a buddy, and ask them properly. Not the person with the most free time, the person who knows how things really work. Say: 'I'd like you to be Priya's buddy for six weeks. That's thirty minutes a week and being the person she can ask stupid questions without me hearing. It's real work, so I'm taking something else off you.'
4. Book the meetings now. Daily fifteen minutes for week one, twice weekly to day 30, then weekly. Put them in the diary before they start so they never have to ask for your time.
5. Tell the team something useful. Not the CV. Say what changes for everyone else: 'Priya joins Monday. She's taking renewals, which means Sam stops splitting his week. Assume she knows nothing about our tooling and everything about renewals.'

Day one: what to say in the first thirty minutes

Do not open with the org chart. Open with the frame that will carry them through the awkward weeks.

Say: 'Here's what I care about in your first ninety days. That you understand what we do and why. That you meet the people you'll depend on. And that you finish one small real thing. I am not expecting output this month. I'm expecting questions, and if you're not asking any I'll assume something has gone wrong.'

Then give them the permission most people never get: 'You'll spot things that look stupid. Some of them are, and we've stopped seeing them. Some have a boring reason behind them. Write them down and bring me the list at day 30, before you've been here long enough to stop noticing.'

Close with the logistics people are embarrassed to ask about: hours, lunch, cameras on or off, how fast you expect messages answered. Say the last one out loud: 'If you're stuck for more than thirty minutes, that's the signal to ask. Buddy first, me second.'

The same moment, done two ways

Week one: shrink the world

A new starter's problem in week one is not lack of information. It is far too much of it, arriving unsorted. Your job is to reduce, not to add.

• Give them one thing to read, not nine. Name the four wiki pages that matter and tell them to ignore the rest until month two.
• Schedule six to eight introductions across the week, each with a stated purpose: 'Meet Tomas so you understand where the data comes from.' Unbriefed coffee chats are a tax on both people.
• Have them shadow one real piece of work end to end, even if they follow a third of it. Sequence beats explanation.
• End each day with five minutes: 'What surprised you today?' You are training the habit of speaking up while it is still easy.
• Don't let them sit silent in group meetings all week. Beforehand, say: 'I'll ask for your first impression near the end. You're allowed to say it's too early to tell.'

The purpose of the first month is not productivity. It is to build a person who asks questions out loud. Everything else is downstream of that.

Days 8 to 30: engineer the first win

Find them something small, real, visible and finishable inside three weeks. Not a training exercise: something the team genuinely needed. A new person who has shipped something has standing to ask questions. A new person who has shipped nothing by day 30 starts performing confidence instead of admitting confusion, and that is where the rot begins.

When you hand it over, be explicit about the stakes: 'This is real, it goes to a customer, and it's small enough that if it goes wrong we'll survive it. Show me a draft at the halfway point, not at the end.'

The day 30 conversation, in four questions

1. 'What's still confusing that you feel you should have figured out by now?' The wording matters. It gives permission to still be lost, which 'any questions?' never does.
2. 'What's on your stupid list?' The observations you asked for on day one. Act on at least one in front of them, even a small one, or you have taught them that noticing is decorative.
3. 'Who have you not met that you keep hearing about?' Gaps in the network show up here before they show up in the work.
4. 'What have I got wrong in the 90-day plan?' Then change it in front of them. A plan that survives contact with reality unaltered was never a plan, it was a document.

Give feedback here too, even if it is all positive, and make it specific. The SBI model is useful precisely because it forces you off 'you're doing great' and onto something the person can repeat. If there is a problem, say it now: month-one feedback lands as coaching, month-five feedback lands as an accusation.

Days 31 to 90: hand over, then get out of the way

By day 60 they should own something with their name on it, where you are consulted rather than copied in. By day 90 they should be the person others go to for at least one thing.

• Transfer ownership publicly: 'From Monday, renewals decisions are Priya's. If you come to me I'll send you to her.' Ambiguous handovers leave the new person doing the work and the old one keeping the authority.
• Move from telling to asking, along the lines of the GROW model: what are you trying to achieve, what have you tried, what are your options, what will you do.
• Let them fail on something recoverable and be visibly calm about it. How you handle the first real mistake sets the psychological safety level for years, and they are watching closely.
• Run a real 90-day review: what they own now, what they'll own by month six, one honest development area. Not a rating. A recalibration.

Onboarding remotely

Two things break by default. Ambient learning disappears, because nothing is overheard, and asking for help costs more, because every question is a deliberate interruption rather than a turn of the head. Compensate deliberately: over-schedule contact for two weeks then taper, narrate your reasoning out loud in calls ('the reason I'm pushing back is something that happened in March'), invite them to listen in on meetings they could skip, and make asking cheap by replying to basic questions with warmth rather than a link.

When it goes wrong: four common failures and the recovery move

Onboarding rarely collapses. It drifts, and the drift is detectable if you know the shapes.

1. They go quiet in weeks three to five

The novelty has worn off, they have realised how much they don't know, and asking now feels like admitting they should have learned it already. Silence reads as competence right up until it doesn't.

Recovery: name it without accusation. Say: 'You asked a lot of questions in week one and almost none this week. I don't think you've suddenly understood everything. What's changed?' Then reset the norm: 'I'd rather you asked me something obvious than spent an afternoon guessing.'

2. The buddy quietly stops showing up

Their own work got busy, sessions slipped, and neither party will raise it. The new starter concludes they are an imposition.

Recovery: take it off the new person entirely. To the buddy: 'The Thursday sessions have slipped three weeks running. Is that workload, or is it not the right pairing? Either answer is fine, I just need to know which.' Then protect the time or reassign, and tell the new starter it was your scheduling error, not their demand on someone.

3. They are drowning but performing confidence

Everything is 'good' and 'nearly there', and then a deadline arrives and it isn't. Asking about feelings will not surface this. Asking about artefacts will.

Recovery: stop asking how it's going and start asking to see things. 'Walk me through the actual file.' 'Show me where you got to on the third one.' Then remove the shame: 'For the record, month two is meant to feel like this. If it felt easy I'd worry we'd hired below the role.'

4. The team has not made room for them

Work still flows to whoever used to do it, the new person is underloaded, and everyone is too polite to admit handing over is slower than just doing it. This one is the manager's fault, and it is fixed with authority rather than encouragement.

Recovery: say it in the team meeting, not in a 1:1. 'Three renewals questions came to me this week that are Priya's. I'm forwarding them. Sam, that means you stop picking them up even when it's faster.' Check again in a fortnight, because it will drift back once.

5. It really is the wrong hire

Sometimes it is. The honest move is early and direct, not a slow eighteen-month fade: 'Here's the gap I'm seeing, here's what different looks like, here's when we'll review it.' People deserve to know they are off track while there is still time to do something about it.

Why reading this won't be enough

You now know what to say, which is about a third of the problem. The rest shows up when the new starter's eyes fill up in a 1:1, when you have to tell a respected colleague to stop hoarding work, when you have to hold silence for four seconds after a hard question instead of rescuing everyone with a joke.

Those are performance skills, not knowledge. They shift through rehearsal, feedback and a second attempt, which is why managers can read twenty articles on giving feedback and still soften every difficult sentence into meaninglessness in the actual room. It is also the whole point of experiential learning: you run the conversation, it goes badly, somebody tells you exactly where you lost the room, and you run it again ten minutes later. The second version is always better. The twentieth is a different manager.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.