Pull up a chair and let me ask you something. Think of the last person who joined your team. What do you remember about their first week? If the honest answer is “laptop came late, someone forgot to add them to the group, and they sat in a corner reading documents,” then you already know what most onboarding looks like. And you also know why some people resign within the first six months, even though they were happy enough to accept the offer.
Let us separate two things that get mixed up. Orientation is an event: the welcome talk, the ID card, the policy acknowledgement, the tour. Onboarding is a process: everything that turns a stranger into someone who knows the work, knows the people and knows how decisions get made here. Orientation takes a day. Onboarding takes weeks, sometimes a full quarter, and it does not finish just because the HR checklist is ticked.
It starts before the joining date
In India, the gap between acceptance and joining can be two or three months because of notice periods. That is a long silence. The candidate has said yes, but the current employer may be making a counter-offer, and a competing recruiter is still calling. This stretch is usually called preboarding, and it has a simple purpose: keep the person feeling chosen.
You do not need anything fancy. A short note from the hiring manager every couple of weeks, an introduction to one future teammate, the joining-day schedule sent a week ahead, the document list sent early so nobody is scrambling for relieving letters on Day One. Most important, make sure the laptop, email ID and system access are ready before the person walks in. Nothing says “we were not expecting you” like a new joiner waiting two days for a login.
Week one: remove friction, do not pour in information
Here is a mistake you will see often. The first week gets packed with compliance modules, product decks and ten introductory meetings. By Friday the new joiner remembers none of it. People learn better when information arrives close to the moment they need it.
A sensible week one has fewer goals. Make sure the person can log in, get paid correctly, find their way around, and has met their manager for a proper conversation about expectations. Assign a buddy, someone at a similar level and not the manager, whose only job is to answer small questions. People hesitate to ask their boss “where do I submit my reimbursement?” but will happily ask a buddy. Give one small, real task by Day Three or Four, even if it is modest. Doing something useful early matters more than people assume.
The ninety-day frame
A common structure is 30-60-90, and it works because it forces a manager to write down what progress looks like. A rough shape, which you should adapt to the role:
- First 30 days, learn. Understand the product, the team, the tools, the customers or internal users. Output: the person can explain the work in their own words.
- Days 31 to 60, contribute. Take on a defined piece of work with supervision. Output: something delivered and reviewed.
- Days 61 to 90, own. Run a task or workstream independently and raise improvement ideas. Output: the manager stops checking every step.
Notice that each phase has an observable output, not a vague aim such as “get familiar”. If you cannot describe what the person should be doing differently at day 60, the plan is a wish.
Where the manager fits
HR can build the programme, but the manager decides whether it works. The research and common experience point the same way: the new joiner’s relationship with the direct manager shapes their first impression more than any induction deck. Ask managers to do three things. Hold a weekly one-to-one for the first quarter. Explain what a good result looks like in this team, including unwritten rules such as how quickly messages are answered and whether people speak up in meetings. And give feedback early, while it is still easy to act on.
Check-ins by HR are useful as a second line. A short conversation at day 7, day 30 and day 90 asking “what is clearer than you expected, what is murkier?” will surface problems the manager never hears. Keep the questions open and the tone casual. A survey form with fifteen rating scales gets rushed answers.
What about freshers and lateral hires?
They need different things, and treating them alike wastes both groups’ time. A fresher straight from campus needs structure: classroom learning or a training batch, a mentor, a gradual increase in difficulty, and plain explanations of workplace norms nobody taught them in college. A lateral hire with eight years of experience needs context rather than instruction. They know how to do the job; what they need is the map. Who are the key stakeholders? What did we try before that failed? Where does the real decision get made? Sending an experienced hire through a beginner’s training programme signals that nobody read their CV.
Measuring whether it worked
Some measures are easy to track and genuinely informative. Early attrition, meaning people who leave within the first six months or year, is the blunt one. Time to productivity, which you can estimate by asking managers when the person reached an agreed standard, tells you about speed. Probation confirmation outcomes and new joiner feedback at day 90 fill in the rest. Be careful reading any single number. A low early-attrition figure can simply mean the market is slow, and a long ramp-up may reflect a complicated role rather than poor onboarding.
One last point, since you asked what to do about the very worst case: the person who clearly is not working out by month two. Do not wait for the probation end date to say something. Tell them early, with specifics, and give a chance to improve. Onboarding includes honest feedback, and it is kinder than silence followed by a surprise.
Leave a Reply