The first day, prepared in advance
Nothing on a good first day is difficult. All of it has to be done before the person arrives, which is why it so often is not.
A new employee's first day sets an expectation about how organised the company is, and it is almost impossible to revise that impression later. Someone who spends their first morning waiting for a laptop has learned something about the place, and they were paying close attention.
None of the individual items are hard. The failure is one of sequencing: the work has to be done in the week before, and in the week before there is always something more urgent.
The week before
Set a single named owner for the arrival — not a department, a person — and give them a list.
- Equipment ordered, delivered, set up and tested. Logged into, not just unboxed.
- Accounts created: email, whatever systems they need, door access, phone if relevant.
- Payroll set up, with whatever the person needs to provide requested in advance rather than on the day.
- Contract issued and returned. The first day is not the moment to be reading terms.
- Desk, locker, parking, whatever physical arrangement applies — allocated and actually available.
- The first-week schedule written and shared with the people who appear in it.
The single most common first-day failure is an account that exists but does not work. Someone should log in as the new person, from the device they will use, before the day starts.
Tell the team a person is arriving
In a small company this is skipped because everyone is assumed to know, and reliably one or two people do not. A short note the week before — who is starting, what they will be doing, who they will work with most — takes two minutes and prevents the arrival being explained six separate times. For a related product-level perspective on proactivity at work, see read more.
The shape of the day itself
The failure modes are opposite and both common: an empty day where nobody has time for the new person, and a saturated day of back-to-back introductions that nobody could retain.
A workable shape is a slow start with the practical things, a proper introduction to the immediate team, a genuine break in the middle where somebody has actually arranged to have lunch with them, one real piece of work in the afternoon, and a short end-of-day conversation with their manager.
The afternoon task matters more than it appears. It should be small, achievable and real. Finishing the first day having actually done something is the difference between joining a company and being processed by one.
Explain the unwritten things
Every workplace has conventions nobody documents: whether people take lunch at their desk, how much notice is normal for a day off, whether the Friday afternoon message thread is optional, who to ask about what, how formal the writing is. For broader independent guidance on this point, consult OSHA training resources.
New people spend weeks working these out by observation and getting some of them wrong. Stating them explicitly — ideally by a peer rather than a manager, who often does not know what the conventions look like from below — removes a low-grade anxiety that otherwise runs for a month.
Assign a peer, not just a manager
The manager answers questions about the work. A peer answers the questions people are reluctant to ask a manager: where things are, how something really gets done, whether it is normal that a process is like this.
Name someone, tell them they have the role, and give them the time. A buddy arrangement that exists on paper but comes with no adjustment to the person's workload is not an arrangement.
Then keep going
The most common onboarding pattern is a well-organised first day followed by nothing. The new person completes their induction, is shown to a desk, and is thereafter treated as fully arrived — usually about three weeks before they are.
The first day is the opening of a process that runs for months, and the structure that carries it is the ninety-day plan rather than the induction checklist.