Overview

A person's first week at your company sets the tone for the next three years. If they're confused, ignored, and thrown into the deep end, they're already thinking about whether they made the right choice. If they're welcomed, oriented, and supported to ramp up, they're excited to be there.

Most onboarding is chaotic. "We'll figure it out as we go" thinking. Someone shows the new hire where the bathroom is. They get a laptop that might not be set up yet. They have an unclear start date and unclear expectations for the first week. By day three they're asking themselves why they left their last job.

Good onboarding has structure. First week: orientation and setup. First month: ramping up on actual work with support. First 90 days: autonomous but still being checked on. First year: evaluating how they're doing and whether the role is right.

AI can help you build this structure. It can help you create checklists so nothing falls through the cracks. It can help you personalize onboarding for different roles. The trap: using AI to generate generic onboarding instead of building something specific to your company.

Why This Matters for HR Professionals

Onboarding affects everything downstream: time-to-productivity, retention, how welcome people feel, their perception of your company culture.

Bad onboarding is expensive. People leave (turnover cost: 50-200% of salary). People stay but are less productive and less engaged. People spend weeks before being useful instead of days.

Good onboarding pays for itself in productivity gains alone. And it costs almost nothing if you structure it well. A person who's productive in week 2 instead of week 6 adds months of value over their tenure.

Most HR leaders know this and try to onboard well, but they don't have a system. So it falls to whoever's available. If your manager is in a meeting, the new hire sits idle. If it's their first time managing a new hire, they don't know what to do.

Structure solves this. AI helps you build and maintain structure. The key is turning AI's generic templates into your specific, detailed, step-by-step onboarding process.

The Onboarding Timeline: What Good Looks Like

Good onboarding is sequenced. Think about it in four phases: before they arrive, day one, week one, and the first 90 days.

Phase 1: Before They Arrive (1-2 weeks before start date)

This is when you prevent chaos. Nothing should be "figured out on day one."

• IT: Laptop ordered, partially set up (OS, required software, accounts created)
  - Office/facilities: Desk assigned, equipment ordered (monitor, keyboard, chair), parking/transit arranged
  - Manager: Creates first week schedule, books key meetings, prepares welcome package
  - Buddy assigned: Introduced to new hire via email, given buddy guide
  - HR: Creates welcome packet, ensures all paperwork is ready, creates onboarding checklist

A week before, your checklist should be at 90% complete.

Phase 2: Day 1 (The Experience)

Day one should not be chaotic. If someone's laptop isn't ready or they don't know where to go, you've already damaged the experience.

• 8:30am: Meet HR or buddy in lobby (warm welcome, go to desk)
  - 9:00am: Get laptop from IT, finish setup (password, email, core apps working)
  - 9:30am: Get to desk, settle in, grab coffee
  - 10:00am: First meeting with manager (what's week 1 look like, how to ask for help, expectations)
  - 11:00am: Meet 3-4 key people (quick 15-min intros, not overwhelming)
  - 12:30pm: Lunch with buddy or team member (not the manager; they shouldn't always be the social contact)
  - 2:00pm: Tool and system walkthrough (Slack, email, project management system, etc.)
  - 3:00pm: Check in with manager (how's day going, anything confusing?)
  - 4:30pm: Wrap up, maybe grab coffee with buddy

Day one should be packed but not overwhelming. The message is: we're organized, we're glad you're here, here's how we work.

Important: Day 1 should be planned to the hour. Nothing should be improvised. If it is, your new hire notices.
Phase 3: Week 1 (Orientation and Setup)

Week one is about orientation: meet the people, understand the company, understand your role, get oriented to systems.

• Daily: 15-minute check-in with manager (quick, not performance; just "how's it going, what's unclear?")
  - Daily: At least one meal or coffee with someone (buddy intro them, they build relationships)
  - Mon-Fri: Attend company standup/meeting (start understanding how we work)
  - Week 1: One-on-ones with 3-4 key collaborators (not all in one day; spread it out)
  - Mid-week: Manager walks through the role in detail (actual work, context, expectations, metrics)
  - End of week: Retrospective with manager (what went well, what's confusing, what's next?)
  - Small assigned task: Something simple they can complete with help (to understand the process)

By end of week 1, they should know: who the key people are, what your company does, what their role is, how to ask for help.

Phase 4: Weeks 2-12 (Ramping Up)

This is where they go from "learning" to "contributing."

• Weeks 2-4: Pair on work with more experienced people, take on increasing responsibility
  - Weeks 4-8: Work more independently, but with regular check-ins and support
  - Weeks 8-12: Autonomous in the role, being evaluated
  - Check-ins: Weekly at weeks 2-4, bi-weekly at weeks 4-12

The key here is structured growth. Week 1 they observe. Week 2 they pair. Week 3 they lead with support. Week 4 they lead with feedback.

The Onboarding Checklist: Role-Specific

Onboarding should have different components for different roles. A software engineer needs to: set up dev environment, understand the codebase, make a code contribution, understand deployment process.

A sales person needs to: understand the product, understand the customer, understand the sales process, do a mock demo.

A finance person needs to: understand the accounting system, understand the financial processes, understand the budget structure.

Generic onboarding doesn't work. You need role-specific paths.

How to use AI:

"Create an onboarding checklist for a [role] at our company. Include: before arrival tasks, day 1 schedule, week 1 activities (setup, meetings, learning), week 2-4 activities (ramping on actual work), and month 2-3 activities (ramping toward autonomy). For each, specify who's responsible, what the new hire does, and how success is measured."

AI produces specific, detailed checklists. Your job is to customize and ensure every item has an owner.

Example: Software Engineer Onboarding

Before arrival:
- IT: Laptop ordered, GitHub access created, required development tools ordered
- Engineering manager: Dev environment setup guide prepared, first codebase task identified
- Buddy (senior engineer): Introduced, given buddy guide
- Team: Notified, someone assigned to help with dev environment setup

Day 1:
- 9am: Meet manager, get laptop setup
- 10am: IT walkthrough (VPN, email, tools)
- 11am: Codebase overview (manager/buddy walks through repo structure)
- 2pm: Dev environment setup (engineer sets up with pair programming support)
- 3pm: Check in with manager

Week 1:
- Mon: Codebase overview, understand architecture
- Tues: Set up local dev environment with help
- Wed: Make your first code change (trivial, just to understand the process)
- Thurs: Submit first pull request (with support)
- Fri: Code review feedback, retrospective with manager

Weeks 2-4:
- Week 2: Make a meaningful code contribution (small feature, clear scope)
- Week 3: Work on a feature from start to finish with support
- Week 4: Deploy to production, understand the process

Month 2-3:
- Fully contributing to team tasks
- Confidence in codebase growing
- Being trusted to review others' code

This is specific. Every item has context. The engineer knows what's expected.

The First Day Checklist: Avoiding Chaos

Day one should not be chaotic. Create a detailed first-day checklist that everyone knows.

How to use AI:

"Create a first-day checklist for our company. Include: before they arrive (what needs to be done the week before), who does what (IT, office manager, HR, manager, buddy), when (specific times), and how to measure success (was it smooth?). Make it detailed enough that someone covering can't mess it up."

Example First-Day Checklist:

Week Before:
- [ ] IT: Laptop ordered (deadline: 2 weeks before start)
- [ ] IT: Accounts created (GitHub, email, systems; deadline: 1 week before start)
- [ ] IT: Laptop set up OS + base software (deadline: 2 days before start)
- [ ] Office: Desk assigned, equipment ready (deadline: 1 week before)
- [ ] Manager: First week schedule created and communicated to new hire (deadline: 1 week before)
- [ ] Manager: Key meetings booked (deadline: 1 week before)
- [ ] Buddy: Given buddy guide, introduced to new hire via email (deadline: 1 week before)
- [ ] HR: Welcome packet ready, paperwork prepared (deadline: 3 days before)

Day Of:
- [ ] 8:00am: HR/Buddy arrives 30 min early, greets new hire at lobby/door
- [ ] 8:15am: Walk to desk, settle in
- [ ] 8:30am: IT arrives with laptop, walks through setup, confirms everything works
- [ ] 9:00am: HR does 15-min orientation (bathroom, emergency exits, lunch procedures, how to ask for help)
- [ ] 9:15am: Buddy introduces them to 2-3 nearby people (quick, casual, 5 min each)
- [ ] 10:00am: First manager meeting (30 min: role overview, week 1 schedule, how to ask questions)
- [ ] 10:45am: Back at desk, explore systems with buddy
- [ ] 12:00pm: Lunch (buddy brings them somewhere; not with manager)
- [ ] 1:00pm: System/tool walkthrough (Slack, email, project management, knowledge base)
- [ ] 2:00pm: Small task with buddy (something to do to understand workflow)
- [ ] 3:30pm: Check in with manager (quick: how's it going, what's unclear?)
- [ ] 4:00pm: Wrap up, buddy asks if they have questions

By end of day one, they've:
- Met the people they work with
- Know how to get help
- Understand where things are
- Have a schedule for week one
- Know how to use the tools

That's success.

Tip: Create this checklist as a shared document your whole team can see. When someone asks "what do we do on day one," you have the answer.

The 30-60-90 Plan: Clear Expectations

A 30-60-90 plan is a partnership between the new hire and their manager. It sets clear expectations for each month. Without it, both the manager and new hire are guessing about what success looks like.

What a good plan includes:
- 30 days: What they should understand (product, team, processes, their role)
- 60 days: What they should be contributing (real work, small projects, demonstrating capability)
- 90 days: What success looks like (autonomous in key aspects, making real impact, clear growth path)

How to use AI:

"Create a detailed 30-60-90 plan template for a [role]. Include: what should they learn at each stage, what should they be able to do, what projects will they own, how will success be measured, what support they'll get. Make it specific to our company and role, not generic. Include checkpoints (30, 60, 90 days) where manager and new hire review progress together."

AI produces a template. On day 1, the manager personalizes it for the individual.

Example: Sales Representative 30-60-90 Plan

30 Days: Understand
- Goal: Understand the product, the customer, the sales process
- Learning:
- Attend product training (what we sell, why it matters)
- Meet 5 customers (listen, learn, understand pain points)
- Shadow 3 sales calls (observe how experienced reps sell)
- Learn the sales process (qualification, proposal, close)
- Work:
- Prepare one customer research report (company, industry, challenges)
- Sit in on your own sales calls (observe, take notes)
- Measurement:
- Can explain our top 3 product features in customer language?
- Can describe the typical customer problem we solve?
- Understand the sales process stages?
- Check-in: Manager reviews understanding, adjusts next phase if needed

60 Days: Contribute
- Goal: Start owning parts of the sales process
- Learning:
- Own one early-stage prospect (you lead the call with support)
- Present one proposal (manager gives feedback)
- Handle one common objection in a real call
- Work:
- Own 2-3 prospecting conversations (you lead, manager observes)
- Present a proposal (manager reviews, gives feedback)
- Close a small deal or move one to next stage
- Measurement:
- How many conversations did you own?
- Can you handle common objections?
- Do you understand what makes a good prospect?
- Check-in: Did you contribute? Are you ready for more responsibility?

90 Days: Autonomous (with support)
- Goal: Working independently in the sales process
- Work:
- Own 5-10 prospects from qualification to close (or close attempt)
- Present proposals and handle objections independently
- Start hitting some part of quota (not full quota; ramping)
- Contribute to sales team discussion (ideas, insights)
- Measurement:
- Number of deals closed or moved forward
- Prospects owned and managed
- Sales conversations led
- Team contribution
- 360 feedback from manager and peers
- Check-in: Are they ready for full autonomy? What support do they still need? Clear growth path for next 12 months?

This is specific. Measurable. Gives both the manager and new hire a clear roadmap.

The Onboarding Materials: What to Create

Minimum onboarding materials:
- Welcome email (before their first day)
- First-day schedule
- Company guide (mission, culture, how we work)
- Role guide (what they'll do, who they work with, expectations)
- Tools guide (how to use Slack, email, project management, whatever you use)
- 30-60-90 plan (customized)
- FAQ (common questions new people ask)
- Buddy guide (what buddies should do)
- Onboarding checklist (shared with everyone involved)

How to use AI:

For each material, ask AI to create a first draft. You customize for your company.

Example prompt:
"Create a welcome email for a new [role] joining our company. Include: excitement about them joining, what happens on day 1, what to prepare before they start, who to contact with questions, what to expect in week 1. Make it warm, welcoming, not corporate. Keep it to one page."

AI will produce something generic. You'll customize it: add real names of the people they'll meet, details about your company, specific role information.

Creating a Company Guide

"Create a company guide for new employees. Include: our mission, culture, how we make decisions, communication norms, what we value, what success looks like here. Make it personal (written as if from the founder/CEO), not corporate. Keep it to 3-4 pages."

This should feel like your company, not a generic template. AI drafts it; you make it yours.

The Buddy System: Peer Support

A buddy (peer mentor) makes onboarding so much better. The buddy answers questions the manager might not know. They invite the new hire to lunch. They check in informally. They make the new person feel part of the team.

How to use AI:

"Create a buddy guide for someone supporting a new [role]. What should they do? How should they help? What's out of scope? When should they loop in the manager? How much time should they spend on this per week? What if there's a conflict or problem?"

AI produces something like:

Your role as buddy:
- Days 1-2: Welcome them, answer immediate questions, help with logistics ("where do I get lunch?")
- Week 1: Invite them to social activities, help them understand the team dynamics, answer process questions
- Weeks 2-4: Pair on work, help them understand unwritten norms, answer "how do we do this?" questions
- Month 2+: Check in regularly (weekly coffee?), but less frequently as they ramp up

In Scope:
- Answering "how do I do this?" questions
- Introducing them to colleagues
- Showing them the ropes (informal stuff)
- Being a friendly face
- Inviting them to team events

Out of Scope:
- Making hiring/performance decisions
- Handling conflicts (escalate to manager)
- Technical coaching (that's the manager's role)
- Managing their work
- Being their only support (manager is primary)

Time commitment:
- Week 1: 5-10 hours (it's intense)
- Weeks 2-4: 3-5 hours/week
- Month 2+: 1-2 hours/week (coffee, check-ins)

A buddy guide ensures buddies know their role and don't overcommit.

Tip: Rotate buddies. Use onboarding as a chance to develop leadership in your team. Being a buddy teaches communication and mentorship skills.

The Onboarding Evaluation: Did It Work?

You can run the best onboarding, but if nobody measures it, you don't know if it's working.

Measurement points:
- Day 1: Did they have a good first day? (quick survey or conversation)
- Week 1: Are they settled in? Do they feel welcomed?
- 30 days: Are they understanding the basics? Are they engaging?
- 90 days: Are they autonomous in key areas? Are they happy?
- 6 months: Are they still engaged? Are they productive? Do they understand growth path?
- 1 year: Would we hire them again? Are they a cultural fit? Are they growing?

How to use AI:

"Create a 30-day onboarding survey for a new [role]. Ask about: setup (was everything ready?), support (did they have help when needed?), clarity (do they understand their role and expectations?), culture (do they feel like part of the team?), confusion (what's still unclear?). Keep it to 5-6 questions. Make it easy to answer."

Use this data to improve your onboarding. If 3 new hires say "I didn't understand the approval process," that goes into your company guide.

Sample survey:
- How would you rate your first 30 days? (1-5)
- Was everything set up and ready when you arrived? (yes/no + comment)
- Did you have support when you needed it? (yes/no + comment)
- Do you understand your role and what success looks like? (yes/no + comment)
- Do you feel part of the team? (yes/no + comment)
- What was most confusing in your first month?
- What went well in your onboarding?
- What could we improve?

Aggregate the feedback. Use it to improve your process.

Try This Now: Three Exercises

Exercise 1: Map Current Onboarding

Write down what actually happens when someone new joins your company. Day 1? Week 1? Month 1? Who does what?

Ask yourself: Where are the gaps? What falls through the cracks?

Ask AI: "Here's what our onboarding looks like now: [describe]. What's missing? What should we add to make it better?"

Exercise 2: Create a First-Day Checklist

Ask AI: "Create a detailed first-day checklist for a [role] at our company. Include: who's responsible for what, when it happens, how to measure success. Make it detailed enough that someone covering can execute it without confusion."

Customize the checklist. Add real names and times. Share it with your team.

Exercise 3: Create a 30-60-90 Plan

Ask AI: "Create a detailed 30-60-90 plan for a [role]. Include: what they learn at each stage, what they contribute, how success is measured, what support they get. Make it specific to our role and company."

Customize it. Use it on day 1 with your next new hire.

Practical Application - "What to Do Monday Morning"

• 
  Map your current onboarding: What happens now? What's missing? Where does it break down?
• 
  Create a first-day checklist: Make sure day 1 is planned to the hour. Nothing should be improvised.
• 
  Create role-specific 30-60-90 plans: Different roles ramp up differently. Customize the plan for each role.
• 
  Create a buddy guide: Train buddies on their role so they don't accidentally overcommit or undershoot.
• 
  Implement 30-day feedback: After 30 days, ask new hires how onboarding went. Use the feedback to improve.
• 
  Measure outcomes: Track: time-to-productivity (when are they contributing?), retention (are they still here after a year?), engagement (are they engaged?).

Key Takeaways

• Onboarding is a system, not ad-hoc: Structure and checklists prevent missed steps and chaotic experiences.
  - Different roles need different paths: A sales person and an engineer ramp up very differently.
  - First day is critical: Get it right and you've set a good tone. Get it wrong and you've created doubt.
  - 30-60-90 plan is the roadmap: Clear expectations for both new hire and manager.
  - Buddy system adds significant value: Peer support complements manager support and builds community.
  - Measure and improve: Use feedback to make onboarding better each time.
  - Pre-arrival prep prevents chaos: Most day-one problems can be prevented by good planning the week before.

FAQ

Q: How much should onboarding be structured vs. flexible?
A: Core structure (first day, first week) should be tight and predictable. Weeks 2-4 can flex based on the person's pace and needs. After month 1, it's fully personalized.

Q: Should everyone go through the same onboarding?
A: Core elements (welcome, setup, introductions) yes, absolutely. Role-specific ramping (actual work, technical learning) no, it should be different for engineers vs. sales vs. finance.

Q: Can I use the same 30-60-90 plan for everyone in a role?
A: As a template, yes. But customize it on day 1 based on the person's background, experience, and the specific situation. A senior hire might move faster; a junior hire might need more support.

Q: How do I know if my onboarding is good?
A: Ask: Do people feel welcomed? Do they ramp faster than in the past? Are they still here after a year? Are they productive? Do they feel part of the culture? If the answer to all of these is yes, you're doing it right.

Q: What if I can't assign a dedicated buddy?
A: Assign someone a responsibility (even if it's a few hours/week). If nobody is accountable, it won't happen. Make it someone's job.

Q: How do I know if the new hire is on track during the first 90 days?
A: Use the 30-60-90 plan. At each checkpoint (30, 60, 90 days), sit down and review progress. Are they hitting the milestones? If not, adjust support or expectations.

What's Next

You've covered recruiting, communications, and learning. Chapter 5 is about performance management: how to use AI to structure reviews, set goals, synthesize feedback, and handle difficult conversations about performance.