Most managers treat onboarding as a formality: send a welcome email, point someone at the wiki, and hope they figure the rest out. The result is predictable. New hires spend their first weeks lost, unsure who to talk to, unclear on expectations, and quietly wondering whether they made the right decision. By the time anyone notices, the damage is done. Research consistently shows that the majority of new employees decide whether they will stay at a company within their first few weeks. That window is short, and managers who waste it rarely get a second chance.
Onboarding is not an HR process. It is the first and most formative management experience a new hire has with you. Get it right and you accelerate someone's contribution by weeks. Get it wrong and you may lose them entirely.
Why the first 90 days matter
There is a well-documented pattern in employee turnover: a disproportionate number of people who leave a job do so within the first year, and many of them mentally check out far earlier. The first 90 days are when a new hire forms their impression of the team, the culture, and the manager. They are watching everything: how organised you are, how clearly expectations are communicated, how much you care about their experience versus simply filling a seat.
A poor onboarding experience does not just slow someone down. It actively undermines their confidence and engagement. People who feel lost in their first weeks become hesitant to ask questions, reluctant to challenge ideas, and less likely to build the relationships they need to be effective. The cost of this compounds over months.
- Early impressions stickA new hire who feels welcomed, informed, and supported in their first week carries that experience forward. One who feels forgotten or confused carries that too.
- Ramp time is a management problemSlow ramp-up is rarely about the individual. It is almost always about the environment they were dropped into. Clear context, introductions, and early goals compress time-to-contribution significantly.
- Turnover is expensiveReplacing someone costs months of productivity, team disruption, and hiring effort. Investing a few hours in structured onboarding is one of the highest-return activities a manager can do.
- Trust is built earlyThe first few weeks set the tone for the entire working relationship. A new hire who trusts their manager from the start is more likely to be open about challenges, ask for help, and give honest feedback.
Before they start
The onboarding experience begins before the new hire walks through the door, or logs on for the first time. Nothing signals disorganisation more clearly than a first day where the laptop has not arrived, accounts have not been created, and nobody seems to know who is responsible for what. These are entirely preventable problems, and they set a tone that is difficult to undo.
Preparation is where most onboarding falls apart, not because managers do not care, but because there is no system. The same tasks need doing every time someone joins, and yet they are reinvented from scratch each time. This is where an Onboarding Journey in Manager Toolkit earns its keep. You set up milestones and tasks once, covering equipment, access, introductions, reading material, and first-week plans, and reuse the structure for every new hire. Each task can be ticked off as it is completed, so nothing falls through the cracks.
- Equipment and accessLaptop, email, Slack, code repositories, internal tools. All of this should be ready before day one. Create Actions for each item and assign them to whoever is responsible, so there is clear ownership.
- First-week scheduleMap out their first five days: who they are meeting, what they are reading, what they are shadowing. A new hire with a clear schedule feels expected. One with an empty calendar feels like an afterthought.
- Buddy or onboarding partnerAssign someone on the team, not the manager, who can answer the small questions: where things are, how things work, who to ask about what. This takes pressure off the new hire and distributes the onboarding load.
- Context documentsPrepare a short list of essential reading: team norms, current priorities, recent decisions, org charts. Do not dump fifty documents on them. Curate the five or six things that will genuinely help them understand the landscape.
The first week
The first week is about orientation, not output. Resist the urge to throw a new hire straight into the deep end. They need to understand the team, the work, the relationships, and the expectations before they can contribute meaningfully. Managers who rush this phase often end up spending more time later correcting misunderstandings that could have been avoided with a proper introduction.
Schedule a proper 1-1 within the first two days. Not a casual chat in passing, but a dedicated catchup where you cover what success looks like in the role, how you prefer to work together, and what they should focus on first. Use Manager Toolkit's catchups feature from day one. It establishes the rhythm early and gives the new hire a clear signal that regular, structured conversation with their manager is normal here, not something that only happens when there is a problem.
- Introductions with purposeDo not just introduce people by name and title. Explain why they matter to the new hire: "This is Sarah, she leads the platform team. You will work closely with her on the migration project." Context turns introductions into useful relationships.
- Set expectations clearlyTell them what you expect in the first month. Be explicit: "I do not expect you to ship anything in week one. I want you to understand how we work, meet the key people, and ask questions." Removing ambiguity reduces anxiety.
- First 1-1Cover three things: what they are hoping to learn, what concerns they have, and what you are expecting from them in the short term. Log it in a catchup so you can return to these points in subsequent conversations.
- Small early winsIdentify one or two low-risk tasks they can complete in the first week. A small pull request, a minor fix, a document review. Early completion builds momentum and confidence without overwhelming them.
The first 30 to 60 days
After the initial orientation, the focus shifts from understanding the environment to contributing within it. This is where many onboarding efforts quietly collapse. The first-week schedule ends, the buddy drifts back to their own work, and the new hire is left to navigate on their own. Without deliberate structure through the first two months, the ramp-up stalls.
Set early development goals using Targets in Manager Toolkit. These should not be the same goals you would set for someone who has been in the role for a year. They should reflect where a new hire ought to be at the 30-day and 60-day marks: understanding the codebase well enough to work independently, building relationships with key stakeholders, completing a meaningful piece of work end-to-end. Keep your catchups weekly during this period. The temptation is to reduce frequency once the first week is over, but this is precisely when regular check-ins matter most. Use these conversations to ask how they are finding things, what is confusing, and where they need support. Track recurring themes with Key Themes so you can spot patterns, both for this individual and across future hires.
- Structured goalsSet two or three clear targets for the first 30 days and another set for 60 days. Make them specific and achievable: "Complete onboarding to the deployment pipeline" is better than "get up to speed".
- Weekly catchupsKeep 1-1s weekly through the first two months at minimum. These are the new hire’s primary channel for raising concerns, asking questions, and getting feedback. Skipping them sends a signal that they are not a priority.
- Expanding contextBy week three or four, the new hire should be attending relevant team meetings, understanding the roadmap, and starting to form opinions. Encourage them to ask questions in group settings. It builds their visibility and confidence.
- Feedback both waysAt the 30-day mark, have an explicit conversation: "How has your onboarding been? What worked? What was missing?" This feedback is invaluable for improving the process for the next person, and it shows the new hire that their perspective matters.
Making onboarding systematic
The biggest problem with onboarding in most teams is that it is reinvented every time. A manager hires someone, cobbles together a plan from memory and good intentions, misses a few things, and then does roughly the same thing six months later when the next person joins. The quality of the experience depends entirely on how busy the manager is that week and how good their memory is. That is not a system. It is luck.
Manager Toolkit's Onboarding Journey template exists to solve exactly this. You define milestones for each phase, pre-start, first week, first month, first quarter, and populate them with the tasks that need to happen every time. When a new hire joins, you create a journey for them and work through it together. Nothing is forgotten because the structure is already there. Actions that come out of catchups and check-ins are tracked alongside the journey, so the whole onboarding experience lives in one place rather than scattered across emails, notes, and memory.
Over time, this compounds. You begin to see what works and what does not. Key Themes surface patterns across multiple hires: perhaps new starters consistently struggle with a particular tool, or the first-week schedule is too packed. Each onboarding improves the next. The result is not just a better experience for new hires, but a more efficient and confident manager who does not have to start from zero every time someone joins the team.
Structure every onboarding
Use the Onboarding Journey to guide new hires through their first weeks with milestones, tasks, and regular check-ins.