Onboarding does not start when the new person walks through the door. It starts earlier, when the company decides what it wants them to find and, above all, who will take care of it. The most common risk is treating it as an administrative checklist: account created, documents signed, introductions made, done. The real goal is different: reduce uncertainty, give clear coordinates and build autonomy without leaving the person on their own.
Before day one: remove the pointless obstacles
The first day should not be spent discovering that the computer isn't ready, that nobody knows who should hand over the badge, or that the manager's calendar is full. These are small problems, but they immediately signal how prepared the organization was to welcome that person.
Before the arrival it helps to split the tasks into three blocks: administration, work tools and context. Essential documents and information on one side; accounts, hardware and access on another; calendar, point of contact, workplace and the first organizational coordinates as the third block. Each task should be assigned to a real owner, not a generic function.
- Check access and equipment before the start date.
- Communicate who is arriving, in which role and from when.
- Prepare a simple first-day agenda, not a meeting marathon.
- Name one person to turn to for practical questions.
Day one: give coordinates before asking for performance
The first day is mainly about understanding where you are. The new person needs to know who the main contacts are, how work gets done, which tools they will use and what is expected of them in the first weeks.
Filling eight hours with presentations may seem efficient, but it often has the opposite effect: lots of information and very little room to absorb it. It is better to alternate orientation moments, focused meetings and individual time to try the tools, read materials and jot down questions.
First week: the role has to become concrete
A title and a job description are not enough. The manager should explain which activities really have priority, which decisions the person can make on their own, which require discussion and who they will work with most often.
It is also the right moment to clarify the unwritten rules that are otherwise discovered by trial and error: how updates are shared, how to ask for help, where information lives, which meetings matter and which behaviors the team considers normal.
- What are the three initial priorities?
- Who are the contacts the person really needs to know?
- What can they decide on their own?
- When and how should they check in with the manager?
30, 60 and 90 days: observable goals, not generic formulas
A 30-60-90 plan works when it describes results or behaviors that can be observed. Being autonomous says little; handling standard cases without support says much more.
The expected level depends on the role, the seniority and the complexity of the context. There is no universal table. The point of the plan is to make a progression visible: first understand, then do with support, then independently handle what is reasonable to expect at that moment.
Check-ins matter before a problem appears
Conversations during onboarding should not be triggered only when something goes wrong. A short, scheduled check-in makes it possible to catch doubts, mismatched expectations and missing information while they are still easy to fix.
Simple questions work better than an endless survey: what is clear? What isn't yet? Where do you already feel autonomous? Where do you need to see an example? Is there something you expected and didn't find? The point is not to collect feedback and file it away, but to turn it into a small action.
Day 90 is not a final exam
The 90-day conversation can close the onboarding phase, but it should not become a mini annual review. It is more useful to look at three things: results achieved, quality of working relationships and clarity of the role.
If a gap emerges, avoid phrases like they need to be more proactive or they need more autonomy without explaining what they mean. Better to agree on a concrete behavior, the support available and a moment to check together whether something has changed.
Checklist finale
- Preboarding owners and deadlines are clear
- Access and equipment are checked before the arrival
- The first day alternates orientation, meetings and individual time
- Role priorities and boundaries are explained concretely
- The 30-60-90 goals describe observable results
- Check-ins are scheduled before problems emerge
- The new person's feedback produces actions, not just notes