Onboarding a new employee is not handing over credentials and an operations manual. It is the process through which a person goes from being "the new one" to being "one of us": a transition made of relationships, unwritten codes and trust that has to be built.
In Italy's mandatory employment notification data, 81.9% of employment relationships that ended in 2024 had lasted less than a year, and almost half ended within three months [1]: the weight of fixed-term contracts explains a good part of those figures, but the first year remains the window in which most separations are decided. Meta-analytic research on newcomer socialization links the quality of adjustment in the first months (role clarity, confidence in one's own abilities, acceptance by the group) to the intention to stay and to actual employee turnover [2]. The data points to an opportunity more than a verdict.
The sections below cover the phases, the roles, the relational tools and the most common mistakes.
Before going further, it helps to clarify three pairs of terms that are often confused. Induction is the initial phase of formal entry: signatures, introductions, access. Onboarding is the longer process that integrates the person into the role, the team and the culture: induction is one phase of onboarding, not a synonym. Initial training transfers the technical skills the role requires; onboarding also covers relationships, cultural codes and mutual expectations. One can be complete while the other fails, and vice versa. Finally, the probationary period is the formal window of two-way evaluation; reducing onboarding to "let's see if it works out" leads to early resignations.
Design the first 90 days as a phased path
Effective onboarding is not a "welcome week" followed by nothing. It is a path with distinct phases: arrival, integration, operational autonomy. Each phase has its own goals, its own pace and its own indicators of success. Treating it as a single block is the most frequent cause of premature exits.
What changes between day 30 and day 90 for a new employee? Treating day 1 as "the onboarding moment" amounts to declaring that nothing will follow.
It is worth remembering that joining a company today almost always comes with some training: in the 2024 Excelsior survey of Italian companies, the strategy chosen most often to deal with hiring difficulties (in roughly one case out of two) is to look for people with skills similar to those required and, once they have joined, put them through targeted training [3]. The 90-day plan is therefore working with a person who is still closing a gap, not with a finished profile.
The 30-60-90 day path sets specific goals for each phase.
Days 1-30: Orientation and listening. The goal is not immediate productivity; it is understanding the context. The newcomer learns who does what, how people communicate and what the team's operational priorities are. The indicators for this phase concern the network of relationships (how many people have they interacted with?), clarity on basic processes (do they know whom to go to for each type of request?) and understanding of the goals of their own role.
Days 31-60: Operational integration. The team member starts contributing independently on well-defined tasks, receives feedback on their first outputs and sharpens their understanding of the organization's unwritten codes. In this phase it is normal for the first tensions between expectations and reality to surface: the structured mid-point conversation exists precisely for this.
Days 61-90: Consolidation and growing autonomy. The team member works with increasing autonomy, feedback becomes more specific and growth-oriented, and priorities for the next quarter are defined. Closing day 90 with a structured conversation is not an exam: it confirms that the process has worked and provides a basis for what comes next.
For the operational side of onboarding (checklists, access, technical training), the article on the practical guide to company onboarding explores that perspective in depth.
Build the network of relationships that keeps the newcomer
The people who stay through the first year are often those who quickly found an informal point of reference besides their direct manager. In research on organizational socialization, support from established colleagues is among the practices most closely associated with newcomer adjustment and, through it, with the intention to stay [2]. A relational network does not form on its own; it has to be set in motion.
How many reference figures does a new employee really need in the first months? Leaving integration to the direct manager alone is a breaking point, not a strength.
The three-figure model also works in small teams, with some adjustments.
The direct manager. Holds the operational mandate: sets priorities, evaluates performance and provides formal feedback. They are the reference for role decisions, not for the organization's unwritten codes.
The buddy (a peer). A colleague at the same level in the hierarchy, ideally with a few years at the company. Their role is not to train but to be available for the questions "you don't ask the boss": how the Monday meeting really works, whom to go to with a technical issue, how to dress for a client visit.
The mentor (optional for simple roles, recommended for complex ones). A senior figure, often outside the direct reporting line, who supports medium-term development. In very small teams this figure may be the founder, with the caveat that the double role (reporting line and mentoring) requires explicit awareness of both functions.
Setting the relational network in motion does not happen by osmosis: it takes deliberate actions. A lunch with the team in the first week, an introduction at existing meetings that is formal without being stiff, an orientation conversation with the buddy on the first day: these are small investments with a significant return on retention.
Pass on unwritten cultural codes without taking them for granted
Every company has unwritten codes (how internal emails are written, when it is acceptable to interrupt a meeting, how much you ask before you propose something) that people who have worked there for years take for granted. For the newcomer they are daily traps. Making unwritten codes explicit speeds up integration more than any manual.
Which unwritten codes are worth making explicit in the first two weeks? Assuming they can be learned just by watching exposes the new hire to avoidable mistakes.
The unwritten codes that most often create friction if they are not made explicit:
- Internal communication. Which channel is used for which type of message? When is a formal email appropriate, and when is a message on the team channel enough?
- Meetings. What do you do if you are late? Do you interrupt or wait? Do you take notes or listen?
- Autonomy and approvals. Which decisions can be made independently and which require approval? This threshold varies enormously between organizations and is never written down anywhere.
- Relationships with clients or suppliers. Is there a preferred tone? Are there contacts who need special attention?
- Working hours and availability assumptions. Is there an expectation of replies outside working hours? How is work handled when the team is on vacation?
The best way to pass on these codes is not to write them in a document (they would lose all their nuance) but to name them explicitly in dedicated conversations during the first two weeks. A one-hour session with the buddy, framed as "here are the things nobody will tell you formally," has high practical value.
To frame the broader cultural dimension these codes belong to, the link to company culture provides the necessary context.
Set two-way expectations in the first conversations
Expectations that are not communicated turn into frustrations by the third month. A structured conversation in week 2 and week 6, about what the person expects from the company and what the company expects from them, reduces the information gap that feeds early departures. The two-way nature is not a formality; it is a matter of method.
What do you really need to ask a new team member on day 60? Waiting for the end of the probationary period to align expectations means discovering problems when it is already too late.
The two-way conversation is built around four open questions, asked in turn in both directions.
- Which aspects of the work are going as expected? (Company to team member, then team member to company)
- Which aspects are turning out differently from the initial expectations?
- What are the priorities to focus on over the next four weeks?
- What do you need to work better?
The fourth question is the most valuable and the least often asked: it creates a space where the new team member can flag obstacles without this being read as a sign of inadequacy. Removing obstacles before they become entrenched is an investment with a direct return on retention.
For the role of feedback in the manager–team member relationship, the article on how to give feedback to team members explores the technical structure of these conversations.
Measure integration with indicators that go beyond performance
Measuring only operational performance in the first 90 days tells half the story. Integration includes indicators of network (whom they talk to), clarity (whether they know whom to go to) and psychological safety (whether they ask questions without fear of looking unprepared). These "soft" indicators often get little attention during the probationary period.
Which indicators should you use to assess a new team member's integration on day 90? A new employee who produces but talks to no one is a delayed goodbye.
The four non-performance indicators to check in the interim conversations:
Relational network. How many people does the new team member interact with regularly? Can they name at least one informal point of reference for each area of their work? Acceptance by the work group is one of the three adjustment indicators that socialization research links to the intention to stay [2]: a relational network that is still weak on day 60 is a signal to read, not a verdict.
Operational clarity. Do they know whom to go to for each type of problem? Do they know the real decision paths, not just the ones on the organizational chart? Uncertainty about "who really does what" creates anxiety and delays that end up weighing on productivity.
Psychological safety. Do they ask when they don't know? Do they flag a problem without fearing a negative reaction? This indicator is detected indirectly (from the number of questions asked, from the willingness to admit uncertainty), not through a direct survey.
Intention to stay. In a structured conversation on day 60, you can ask explicitly: "How do you see yourself in this role a year from now?" The answer is not definitive, but it signals how well expectations and reality are aligned.
To fit these indicators into a broader measurement system, the article on business performance measurement offers complementary tools.
Involve the existing team in onboarding without overloading it
Onboarding is not only a relationship between the newcomer and the company; it is an event that involves the existing team. Involving the team too little leads to isolation; involving it too much leads to fatigue and resentment. The point is to design the involvement, not improvise it.
How much of the existing team should be involved in bringing a new team member on board? Waiting for the team to "welcome them spontaneously" is delegating to chance.
A matrix of involvement intensity by role helps calibrate the load without creating tension.
| Role in the team | Involvement intensity | Type of contribution |
|---|---|---|
| Designated buddy | High (in the first 4 weeks) | Daily availability for informal questions |
| Direct colleagues | Medium-high | Introductions, sharing of tools and processes |
| Colleagues from other functions | Low-medium | Formal introductions, then operational collaboration |
| Senior staff/domain experts | Selective | Learning sessions on specific topics |
The buddy's involvement should be planned explicitly in their calendar, not left as "implicit availability": a colleague who feels onboarding as an unplanned burden tends to pull back exactly when they are needed most.
For the broader dimension of managing people, the article on how to manage your people provides the strategic framework.
Common mistakes in new employee onboarding
The most common onboarding mistakes are not about process; they are about posture: reducing everything to week 1, leaving integration to the manager alone, taking unwritten codes for granted, assessing only performance, not closing day 90 with a structured conversation. Recognizing them is more useful than memorizing them, because they take different forms depending on the size of the company. Dealing with them takes attention more than method.
Which mistake costs more: investing too little in onboarding or turning it into an elaborate program? Both extremes lead to the same outcome: a team member who still doesn't feel like "one of us" by month six.
The five most recurrent mistakes, each with a small correction:
1. Reducing onboarding to the first week. After the initial welcome, the newcomer is considered "settled in." Correction: schedule alignment conversations in week 2, week 6 and on day 90 as part of the process.
2. Leaving integration to the manager alone. The manager cannot also be the informal point of reference: unwritten codes are not learned from the boss. Correction: explicitly designate a buddy and plan their involvement.
3. Not making unwritten codes explicit. It is assumed that the newcomer will absorb them by watching. Correction: devote at least one explicit session to organizational codes in the first two weeks.
4. Assessing only operational performance. Relational integration indicators are ignored until the resignation arrives. Correction: introduce the four non-performance indicators in the interim conversations.
5. Not closing day 90 with a structured conversation. The path ends without a destination, and the team member doesn't know whether their onboarding is considered successful. Correction: plan the closing conversation as an integral part of the plan, with two-way questions.
Limits and conditions of applicability
The 90-day plan described in this article assumes that the organization has a minimum of structure: an identifiable manager, at least one colleague who can be designated as buddy, and the ability to devote time to the interim conversations. In companies of 2-3 people or in a very compressed start-up phase, the model needs to be simplified: the principles (relational network, explicit codes, two-way expectations) remain valid; the formal structure of the three roles does not.
The institutional sources cited (the Italian Ministry of Labor, Unioncamere-Excelsior) describe the Italian labor market as a whole; the research on newcomer socialization, by contrast, gathers international studies on organizations of very different sizes. The data on the link between onboarding quality and retention should be read as directional evidence, not as fixed benchmarks: variability across sectors and company sizes is significant.
Whether the 30-60-90 plan can be transferred without adjustments to mostly remote work settings is an operational hypothesis still to be validated: in those conditions, building the relational network requires different tools and rhythms.
FAQ
How much time should the manager devote to onboarding in the first weeks? One structured hour in the first week for the role briefing, then the scheduled conversations in week 2 and week 6. The temptation to compress everything into day 1 is common and almost always counterproductive: the newcomer cannot process everything in a single session.
How do you designate a buddy in a small team where everyone is busy? The buddy doesn't need particular skills; they need availability and a memory of what joining the company was like. In very small teams, rotating the role among the more senior team members can spread the load.
What should you do if the new team member raises problems in the mid-point conversation? Problems raised in interim conversations are a positive signal: they show that the team member trusts you enough to be honest. The appropriate response is to listen, check and remove the obstacle where possible. Downplaying the problem at that moment produces silence in the following conversations.
Does onboarding also work for highly experienced hires? Yes, with one adjustment: senior hires already have solid technical skills, but they don't know the unwritten codes of this particular organization. The plan for experienced people focuses more on the relational network and less on technical training.
Operational summary
Onboarding a new employee is a process with distinct phases over the first 90 days (orientation, operational integration, consolidation) that requires three reference figures (manager, buddy, mentor), the deliberate articulation of unwritten codes, two-way conversations in weeks 2 and 6, integration indicators that go beyond operational performance, and planned involvement of the existing team. Each of these elements helps reduce the risk of early departures, which are one of the most invisible costs in managing people.
Conclusion
Onboarding a new employee is not handing over credentials and a manual; it is the process that turns a "new" person into "one of us": a path with distinct phases over the first 90 days, a network of relationships deliberately set in motion, unwritten codes made explicit, two-way expectations, indicators that go beyond performance, and an existing team involved in the right measure.
The thread that ties these elements together is the quality of the relationship, not the amount of information transferred. People tend to stay where they get clear points of reference, not just where they were best trained. To frame the operational side of onboarding (checklists, access, technical training), it is also worth reading the practical guide to company onboarding and, on the broader side, how to manage your people.
An organization that truly takes care of onboarding is one where newcomers quickly understand how work gets done and whom to talk to, early resignations become the exception rather than the routine, and the existing team experiences every new arrival as an opportunity rather than a burden. It is a sounder organizational posture and a more sustainable path to long-term growth, within reach of organizations of any size.
Sources and references
[1] Ministero del Lavoro e delle Politiche Sociali, "Rapporto annuale sulle Comunicazioni Obbligatorie 2025 — Le dinamiche del mercato del lavoro dipendente e parasubordinato", 2025. Available at: https://www.lavoro.gov.it/documenti/rapporto-annuale-sulle-comunicazioni-obbligatorie-2025.pdf
[2] Bauer T. N., Bodner T., Erdogan B., Truxillo D. M., Tucker J. S., "Newcomer Adjustment During Organizational Socialization: A Meta-Analytic Review of Antecedents, Outcomes, and Methods", Journal of Applied Psychology, 92(3), 2007. Available at: https://pdxscholar.library.pdx.edu/busadmin_fac/27/
[3] Unioncamere — Ministero del Lavoro e delle Politiche Sociali, Sistema Informativo Excelsior, "La domanda di professioni e di formazione delle imprese italiane nel 2024", Unioncamere, 2025. Available at: https://excelsior.unioncamere.net/sites/default/files/pubblicazioni/2024/Domanda_professioni_formazione_imprese.pdf