Onboarding a New Hire: What to Do in the First 30 Days

Her laptop isn't set up. Nobody told the team she was starting today. By lunch she's eaten alone at her desk and checked her phone twice for other openings. None of this is dramatic. It's just what happens when "we'll figure it out" is the onboarding plan.

Most small companies don't skip onboarding on purpose. There's no HR team to own it, the hiring manager is buried, and the new person is expected to "pick things up." The cost shows up later — in the resignation at month four, or the quiet underperformance nobody can quite name a reason for.

Here's a plan that doesn't need a system, a budget, or a department. Just someone willing to do it deliberately.

Before day one

Do this the week before they start, not the morning of.

• Get their equipment ready — laptop, login, email, any tools they'll need on day one. Test the logins yourself.
• Send a short email the week before: start time, what to wear, where to park or which door to use, who'll greet them.
• Tell the team. A one-line message — "Aisha starts Monday, she'll be on the ops side, say hi" — is enough. The point is that nobody looks surprised.
• Write down the first week's actual tasks. Not a vague "get settled in" — real, small, completable things. A new hire with nothing concrete to do by 11am on day one starts wondering if they made a mistake.

Day one

Keep it human, not ceremonial.

• Someone meets them at the door. Not HR — their manager, or whoever they'll actually work with.
• Fifteen minutes on how the team actually works: who to ask when stuck, how meetings run, what "urgent" means here.
• One completable task before the day ends. Something small enough to finish, so they leave with a sense they did something, not just watched onboarding videos.
• Lunch with at least one person. Doesn't have to be you.

Week one

This week is about orientation, not evaluation.

• A 20-minute check-in on day three: "What's confusing so far? What do you need that you don't have?" Ask it plainly — people won't volunteer this unprompted in week one.
• Introduce them to the two or three people they'll depend on most, not everyone at once.
• Give them something real to contribute to by Friday, even a small piece of a bigger project. Watching from the sidelines for a week erodes confidence faster than a hard task does.

Weeks two to four

This is where most onboarding plans quietly stop — and where the real signal starts showing up.

• Weekly 20-minute check-ins, same time each week, same three questions: What's going well? What's stuck? What do you need from me?
• Give feedback on actual work, even small stuff. Silence in the first month reads as "nobody's watching," which is either reassuring or worrying depending on the person — you want neither.
• Introduce the parts of the job that only show up after week one: the messy client, the tool nobody documented, the process that exists only in someone's head. Better they hear it from you than discover it by breaking something.

If you assessed the person before hiring — a work sample, a structured interview, a test of some kind — you already have a private read on where they'll need support. Use it instead of starting from a blank page. If you ran something like an AssessFit assessment during hiring, that report tells you which areas to check on first, not to catch them out, but so you can send help before they have to ask for it.

The 30-day conversation

Have one real conversation at the 30-day mark, separate from routine check-ins. Structure it around three things:

1. What surprised you — about the role, the team, the company. This tells you what your hiring process failed to communicate.
2. What's still unclear — process, expectations, tools. Fix what you can this week, not "eventually."
3. How they'd rate their own start — and be honest about how you'd rate it too. This is the moment to name a concern gently, before it hardens into a pattern.

Write down what came up. Not for a file nobody reads — so the 60-day and 90-day conversations aren't starting from zero.

When something feels off

Some unease in the first month is normal — new job, new people, new systems. What's worth flagging early:

• They've asked the same clarifying question three times. That's usually not forgetfulness — it's a sign the explanation isn't landing, or the task is genuinely unclear.
• They've stopped asking questions altogether after week one. Curiosity dropping off fast is a bigger warning sign than too many questions.
• Something in the work doesn't match what came across in the interview. Worth a direct, non-accusatory conversation — "I noticed X, walk me through how you approached it" — rather than silently downgrading your opinion of them.

None of these mean you made a bad hire. They mean you caught something in week three instead of month four, which is the entire point of doing this deliberately.

What this isn't

This isn't a 90-page onboarding manual, and it doesn't need to be. Manuals get written once and read never. A person checking in with actual questions, on a schedule, does more than any document — and it's the part small companies are best placed to do well, precisely because there's no HR layer between the manager and the new hire.

The judgement call is how much structure to add as you grow. At ten people, this list is probably enough. At eighty, you'll want a written checklist so onboarding doesn't depend on whichever manager remembers to do it. Add structure when memory stops being reliable — not before.