People remember their first week for a long time
The feeling of “they were expecting me” or “they forgot about me” forms in the first days, and it shapes both how quickly someone becomes productive and whether they stay. Almost everything needed for it is prepared in advance and takes a couple of hours.
The typical failure looks the same everywhere: no access, no equipment ready, the manager in meetings, no tasks and nobody to ask. A week later the person is pretending to be busy and losing confidence.
Before day one
| What to prepare | Why in advance |
|---|---|
| Equipment and accounts | Waiting for access eats the first week |
| Access to systems and chats | Otherwise they cannot see how the team works |
| A plan for week one | What they are doing at 10am on Monday |
| A buddy or mentor | Someone to ask the “stupid” questions |
| Introductions | Who does what and who to ask about what |
| A first small task | An early result gives them something to stand on |
The first-week plan
Not “read the documentation” but concrete steps by day: who to meet, what to read, what to do, what to ship. The first task should be small, useful and finishable — it gives the person a sense that they are already contributing.
Always name a buddy: someone they can ask anything without feeling they are interrupting a manager.
Expectations and feedback
Say out loud what a good result during probation looks like and how it will be assessed. Unstated expectations are the main cause of a failed start: the person tries hard in the wrong direction.
Give feedback after a week and after a month, not only at the end of probation. Early correction is cheaper and kinder than a late conclusion.
What is often forgotten
Show the mundane: where the food is, how to book a room, how holiday works, who fixes laptops, how the team communicates and when it is fine not to reply. Those details take up more of a newcomer’s attention than anyone expects.
When onboarding is done well
Access and equipment are ready before day one, there is a week plan and a first task, a buddy is named, expectations are spoken about, feedback comes in the first week, and the team knows who joined and what they will do.