The first ninety days shape how a new team member feels about their job, their manager, and the company. Get them right and you have someone confident, productive, and bought in. Get them wrong and you have someone quietly browsing job boards within six months. Most onboarding programmes focus on logistics: laptop, accounts, HR forms, a stack of documents. The technical side of getting set up is the easy part. The hard part, and the part that most managers underinvest in, is the relational and contextual onboarding that turns a new hire into a real member of the team.
A great onboarding is not a checklist you complete. It is a structured experience that gives a new joiner clarity, confidence, and a sense of belonging from day one.
Preparing Before Day One
Onboarding starts the moment someone signs the offer, not when they walk through the door. The gap between offer acceptance and start date is when buyer's remorse can creep in, and it is also when you have the chance to set the tone before they arrive. A short personal note from you within a week of the offer being signed signals that they have made the right choice and that you are already invested in their success. Once you know your hiring process has landed someone, the work shifts from selection to integration.
Use the lead time to do the unglamorous prep work. Make sure their laptop is provisioned, their accounts are created, their desk or remote setup is sorted, and their calendar has the right meetings already booked for week one. Nothing makes a new joiner feel less wanted than spending their first morning chasing IT for a password reset. Also use this time to brief the team on who is joining, why you hired them, and what you hope they will bring. The team should know their name and a little about them before they walk in.
- Welcome messageSend a short, warm note within a week of offer acceptance. Confirm their start date, share what to expect on day one, and tell them you are looking forward to working with them. Keep it personal, not corporate.
- Logistics sortedLaptop, accounts, software access, security passes, and any equipment should be ready before they arrive. If any of these will be late, tell them in advance so it does not feel like an oversight.
- First-week calendarPre-book the meetings that matter: a kickoff with you, intros with the team, a session with their buddy, and a short window with stakeholders they will work with. Leave plenty of unscheduled time for absorbing.
- Team briefTell the team who is joining, what their background is, and what they will be working on. Encourage people to reach out and welcome them. A new joiner who gets five welcome messages in their first hour feels a different kind of onboarding to one who gets none.
Day One and the First Week
Day one should feel calm, structured, and welcoming. Resist the temptation to dump information on them. The job of week one is not to teach them everything about the role. It is to make them feel safe, oriented, and connected to the people they will be working with. They will not remember the details of the architecture overview you crammed into Wednesday, but they will remember whether the team was friendly, whether you were present, and whether they felt like the right call had been made.
A balanced first week
Pace the first week. Give breathing room between intros and information.
Block out the first hour of day one for yourself. Sit with them, walk them through the day, and answer the questions they did not get to ask in the interview. Introduce them personally to the team rather than relying on a Slack ping. Pair them with a buddy for the first month, ideally someone friendly who is not their direct teammate, who they can ask the daft questions to without feeling judged. By the end of week one, aim for them to have done one small piece of real work, however tiny. Shipping something, even a documentation update, builds confidence faster than another week of reading. Make sure their first 1-1 with you happens inside the first three days.
- Welcome them in personBe there on day one. If you cannot, have a senior team member step in and explain why. Disappearing on a new joiner's first day sends a message you do not want to send.
- Pair with a buddyAssign someone to act as their go-to for the first thirty days. The buddy should not be you and should not be their direct collaborator. Their job is to make the new joiner feel comfortable asking obvious questions.
- Hold a meaningful 1-1Run a proper first 1-1 within the first three days. Use it to understand what would make them feel successful, what their first concerns are, and how they like to receive feedback.
- Ship something smallA tiny first contribution by end of week one builds momentum. It could be a doc update, a process tweak, or a small fix. The point is the feeling of having done real work, not the size of the impact.
- End with a check-inOn Friday, have a short conversation about how the week felt. What was confusing? What was missing? What did they expect that did not happen? Their fresh perspective is data you cannot get any other way.
The 30, 60 and 90 Day Plan
Beyond the first week, the most useful framing is the 30-60-90 day plan. The phases are not arbitrary. They map to a real progression: in the first thirty days the goal is learning, in days thirty to sixty it is contributing, and from sixty to ninety it is owning. A clear plan gives the new joiner something to anchor against, and gives you something concrete to discuss in your 1-1s. Without it, you both end up reactively responding to whatever showed up that week.
Co-create the plan with them in week two, once they have enough context to push back sensibly. Write it down somewhere you both can see it. Manager Toolkit's journeys feature was built for exactly this, giving every new joiner a structured pathway with milestones and tasks. The plan does not need to be elaborate. Three or four objectives per phase is enough, with one or two outcomes per objective so progress is observable.
- Days 1-30: LearnFocus on context, relationships, and absorbing how things work. They should meet every key stakeholder, understand the team's priorities, and start to form their own view. Avoid loading them with delivery in this phase.
- Days 31-60: ContributeMove from observing to doing. They should own a small piece of work end to end, attend meetings with a clear role, and start adding their voice to team decisions. Mistakes here are normal and useful.
- Days 61-90: OwnThey should be running an area of work without your daily involvement. By day ninety they should be producing output that looks like the rest of the team, with a clear sense of where they add unique value.
- Build in checkpointsA formal 30, 60 and 90 day review with you keeps the plan alive. Use each one to celebrate progress, surface blockers, and adjust the plan based on what you have both learned.
Building Context, Relationships and Trust
Technical onboarding is only half the picture. New joiners need to understand the unwritten rules: who decides what, where the politics live, what is celebrated, what is quietly tolerated, and what is genuinely not okay. This is the context that distinguishes someone who is technically competent from someone who is actually effective. It cannot be written down in a wiki because most of it is not consciously known by the people who already operate in it. Your job is to surface it deliberately, not assume they will pick it up by osmosis.
What new joiners actually need
Visible (easy)
Tools and access
Org chart
Process docs
Hidden (matters more)
Who actually decides
What is rewarded
How conflict is handled
Most onboarding nails the left column and ignores the right. Reverse that.
Set them up with a series of intro calls in their first three weeks. Not just their direct collaborators but the people one or two steps removed: the cross-functional partners, the senior stakeholders, the long-tenured engineers who know where the bodies are buried. Give them permission to ask everyone the same set of questions: what does success look like for the team, what is the biggest risk right now, what would you do if you were in my shoes? The patterns in the answers will teach them more about the organisation than any document. For more on how managers can use this kind of pattern recognition over time, see our piece on why key themes matter.
- Stakeholder mapGive them a one-page view of who matters: direct collaborators, key stakeholders, internal customers, and the people whose support they will need to be effective. Add a sentence on what each person cares about.
- Cultural artefactsShare the team rituals, in-jokes, and norms that you take for granted. Where do you celebrate wins? How do you raise concerns? What does a great day on this team look like? These details ground them in the culture.
- Permission to askTell them explicitly that questions are welcome and that there is no such thing as a stupid one in the first ninety days. The first time they hesitate to ask something is the moment onboarding starts to fail.
- Real feedback earlyDo not wait until the probation review to give meaningful feedback. Small course corrections in week three are easy. Major rewrites in month three feel like a betrayal of trust.
Common Onboarding Mistakes to Avoid
Most onboarding fails in predictable ways. Knowing the patterns lets you design around them. The biggest mistake is treating onboarding as a one-week event rather than a ninety-day arc. The second is being too hands-off, mistaking abandonment for empowerment. The third is being too hands-on, hovering until the new joiner feels like they cannot make a move without checking. The right balance shifts as they grow into the role, but in the early weeks erring on the side of presence is almost always right.
The other failure mode is forgetting that onboarding is a two-way process. They are evaluating you and the team just as much as you are evaluating them. Their first ninety days form the story they will tell about working here, both internally and externally. If your onboarding is shambolic, no amount of polish later in their tenure will fully fix the impression. If it is structured and warm, they will start advocating for you before they have done their first project. For some good context on the broader environment new joiners arrive into, see how to build trust with your team.
- Information dumpingTrying to teach them everything in week one is counterproductive. They will not retain it and they will feel overwhelmed. Spread the learning over the full ninety days, paced to what they actually need next.
- Disappearing managerBooking the welcome lunch and then vanishing for two weeks is a classic. Be visible, predictable, and reachable. Frequent short check-ins beat infrequent long ones in the early weeks.
- Skipping the boring bitsTools, access, security, expense process. None of this is exciting. All of it grinds productivity to a halt if it is not sorted. Owning the unglamorous logistics is part of the job.
- Comparing to the previous personWhether the previous person was great or terrible, they are not the same person. Anchoring expectations to a predecessor is unfair to the new joiner and rarely accurate.
- Forgetting cultureProcess can be learned from a wiki. Culture cannot. If you do not actively introduce them to how the team really works, they will absorb whatever they happen to encounter, which may not be what you want them to.
Frequently asked questions
Give every new joiner a structured start
Use Journeys to give new team members a clear pathway with milestones, tasks and checkpoints from day one to day ninety.