You will be able to plan a new hire's first month so they know the work, the people and what good looks like.
Aziz started on a Monday. His laptop arrived on Wednesday. His access to the ticketing system came through the following week, and the client database took another week after that. For his first three days, he read old reports in a meeting room and waited for someone to have time for him. At the end of the first week, his main memory of the job was being apologised to.
Nobody meant it to go that way. Everyone was busy, and onboarding was nobody's job in particular. But the first month shapes how quickly someone starts contributing, and how they feel about the decision to join. A rough start is expensive for everyone, and it's almost entirely avoidable.
Most of what goes wrong in the first week is set up, or not, before the person arrives. Equipment, accounts and access take time, often days, and they depend on other teams. Start them as soon as the offer is accepted.
Make a list of everything the new hire needs to do their job: a laptop, email, the team chat, the shared drive, the ticketing system, the CRM, the client database, building access, any software licences. Next to each, write who arranges it and how long it usually takes. Send the requests in the week the offer is signed, because waiting until the start date is how a laptop arrives on Wednesday.
Name a buddy: someone on the team, not the manager, who will be the new hire's first stop for small questions. "Where's the printer?" "How do I book a meeting room?" "Is it normal for this client to email at midnight?" New hires often hesitate to ask their manager small questions, and a buddy removes that barrier. Choose someone patient and tell them clearly what you are asking of them for the first month.
Finally, send the new hire a short note a few days before they start: where to go, what time, who will meet them, what the first day will look like. It takes ten minutes and removes much of the first-day anxiety.
The first week has two jobs. The first is to meet the people the new hire will depend on. Not the whole company in a blur of introductions, but the specific people whose work connects with theirs. For Aziz, that means his teammates, the warehouse lead who sends the client data, the finance contact who handles billing queries, and Daniel. Short one-to-one meetings work better than a group lunch for this, because he'll remember the people he actually spoke to.
The second job is to finish one small, real piece of work. Not a training exercise, but a genuine task that matters, sized so that it can be done in the first week with help. Answering three routine client queries with his buddy reviewing them, or checking one week's report figures against the source data. Finishing something real in week one gives the person a reason to feel useful, and it shows you early where they will need support.
Hold a short one-on-one on day one and another at the end of the week. The questions are simple. What's going well? What's confusing? What do you need?
From week two, give the new hire a piece of real work they will own, with clear expectations about what good looks like. Use the five-part brief from lesson 3.1, Delegate outcomes, not instructions, and set the authority level and checkpoints from lesson 3.2, Match your involvement to their experience. For a new hire, almost every task starts at low experience, so expect more structure and more check-ins than you'd give the rest of the team.
Share the team's working expectations from lesson 4.2, Write down the expectations you assumed were obvious, in the first week or two. New joiners usually learn the team's unwritten rules by breaking them. Written expectations let them skip that.
Hold one-on-ones more often than usual for the first month, weekly at least. Start the shared one-on-one document from lesson 2.3 on day one, so the habit is set from the beginning.
At the end of the first month, ask the new hire one more question: what was confusing, unclear or harder than it needed to be?
New hires see gaps that everyone else has stopped noticing. The team's knowledge has become invisible to the people who have it. The newcomer is the only person who can still see which document is out of date, which process makes no sense to an outsider, and which piece of jargon nobody ever explained.
When Wei Ling asked Aziz this, he gave her a list of six things. The client handbook referred to a system the company stopped using a year ago. Two people had given him opposite instructions about how to log escalations. Nobody had mentioned that the warehouse data came on Fridays. Every one of these would trip up the next hire, and several were tripping up the current team too.
Write the answers down and fix the ones you can before the next person starts. Your onboarding gets better with every hire.
Start with the first part, the list of everything a new hire on your team needs before they can do any work, and who on your team or elsewhere arranges each item.
List every account, tool and introduction a new hire on your team needs and who arranges each one.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).