Managing & Developing People
Onboarding New Team Members
Turning a signed offer letter into someone who can actually do the job, on purpose instead of by accident.
Onboarding is the two-to-eight-week window where a new hire converts from "technically employed" into someone who can do the job without silently guessing where the bathroom is, metaphorically and otherwise. It's the highest-leverage stretch of a manager's relationship with a report: what happens here sets the frame for how much someone trusts you to have their back, how fast they become net-positive for the team, and whether they're still around in six months. Most onboarding failure isn't malicious — it's a manager reusing whatever pattern was done to them, or doing nothing deliberate at all and calling the resulting improvisation "organic."
Scenarios
You manage a small remote team and a new hire starts on Monday. Your calendar for their first week is already full of standing meetings you didn't think to move. By Wednesday, they've been quietly scrolling old Slack threads trying to reverse-engineer how deploys actually work, because interrupting your calendar with what they assume are dumb questions feels worse than staying stuck. What do you do differently before their next start date, and what do you do about this week?
Two weeks in, your new hire opens their first pull request. It comes back with six rounds of revision — wrong branch naming, wrong review etiquette, a missed step in a checklist nobody wrote down because everyone who already worked there just knew it. They start apologizing in every comment thread. None of this was explained to them going in. Whose gap is this, and what do you say to them in your next 1:1?
A month in, a new report tells you in your regular 1:1 that they're "settling in fine." You notice they still haven't had a real conversation with anyone outside your immediate team, and their questions have gotten quieter over the month instead of more confident. Do you take "fine" at face value, and if not, what do you actually ask instead?
Takeaway
- Write the 30/60/90-day plan before day one — not improvised during week one because there wasn't time before.
- Assign a buddy who isn't their manager: someone they can ask an obvious-sounding question without it feeling like it's being scored.
- Give a first task with a known-good outcome and a safety net, not a live-fire test with real customers and no supervision.
- Leave real unstructured time between intro meetings — a calendar full of stakeholders is not the same thing as orientation.
- In week 2 and week 4 1:1s, ask specifically what's still unclear, not "how's it going" — the second question only ever gets "fine."
- Tell them explicitly when the evaluation period is over, so they can stop performing competence and start building it.