Onboarding: why the first 90 days decide retention (and a practical plan)

The offer is signed, the team breathes out and everyone goes back to their own priorities. Then the first day comes, the laptop isn’t ready, the manager’s diary is full and nobody is quite sure what the new person should be doing that week. We’ve seen it more than once, and it’s rarely for lack of goodwill. People simply assume the hard part is over.

It isn’t. In the first few months, a new joiner keeps comparing what they were told during the process with what they find every day. If the two match, they commit. If they don’t, doubts creep in, and sometimes they start answering other companies’ messages without anyone noticing.

Why these three months carry so much weight

Expectations peak at exactly the moment the person has the least context. Everything promised in the interviews is being tested, and at the same time they don’t know who to ask, which decisions were made before they arrived or what exactly is expected of them. First impressions set fast, too. A first day with no laptop and nobody to meet you is remembered for a long time.

There’s something else we often remind companies of. Many tech and digital candidates had other processes running when they accepted, and those contacts don’t disappear the day they sign.

Good onboarding doesn’t need a welcome deck or a hundred-page handbook. A simple plan will do, one that helps the person understand first, connect next and contribute after that.

Start before day one

Onboarding begins the moment the offer is signed. Have the laptop, accounts, tools and permissions ready before they arrive. Give them a buddy, someone on the team who isn’t their manager and whom they can ask anything without feeling judged. Send the first week’s agenda a few days ahead so they turn up knowing what will happen. And ask their manager to block real time in the diary for those weeks, because that’s the first thing to go when work gets busy.

The first month is for understanding

Nobody should expect much output between day 1 and day 30. The aim is for the person to understand the business, the product, the team and where they fit in. What helps most is meeting people from other teams (not just their own), documentation that explains how work gets done and where information lives, and a first well-scoped task with a visible result. For a technical role, a small change that reaches production. For a business role, an analysis or a short project.

Put in writing what’s expected at 30, 60 and 90 days, agreed with their manager. And at the end of the month, have an honest conversation: does what you’ve found match what we told you? If there’s a gap, this is the best time to spot it, while it’s still small.

Days 31 to 90, from contributing to settling in

By the second month the person has context and can own something, a project or an area with clear goals. Keep up the one-to-ones with their manager, weekly if you can. Ask them to share what they see with fresh eyes. Newcomers notice things the team stopped seeing long ago, and listening is the best way to show them their view counts. Check, too, whether they need training or support with any tool or process.

The third month is for confirming the hire is working and looking ahead. Hold a formal review of the goals you agreed at the start, with concrete feedback going both ways. Talk about the next six months and how they can grow. And ask what they would change about onboarding for the next person, since nobody has seen it more closely.

Signs that call for a conversation

Over these three months, a few things tend to come before problems:

• They ask few questions or have stopped joining in at meetings.
• After the first month, they’re still unclear about what’s expected of them.
• The work they’re given doesn’t resemble the role they were sold.
• Their manager can barely find time to see them.

None of these means the hire has gone wrong. All of them deserve a conversation soon, though, rather than at the 90-day review.

What changes from role to role

The three-phase outline works for almost any role. What changes is the content. For technical roles, access to the codebase and environment from day one, some pair programming and a small first delivery within days. For business and support roles, time with internal clients, access to data and metrics, and a solid grasp of the sales cycle or operating process. For leadership roles, more time listening before deciding anything, meetings with the leadership team and the team they’ll lead, and a clear mandate agreed with the person they report to.

A shared document is enough

You don’t need a platform or a dedicated People team. A document with the three phases, a named buddy and a manager with protected time already make a real difference. What actually matters is that the plan exists and that someone makes sure it happens.

If you work with a recruitment partner, share it with them. They’ll be able to tell candidates exactly what to expect and follow up after the start date. At Mimmic Talent we ask for it whenever a company lets us, and if you’d like to go through yours together, we’re happy to help.