Handbook
/
Hiring & Team
Onboarding New Hires for Success
The first 90 days determine whether a hire succeeds. Here's how to onboard well.
Hiring is expensive. Losing new hires is more expensive. Good onboarding is the difference between someone ramping quickly and contributing, versus struggling and leaving. The first 90 days matter enormously.
Why Onboarding Matters
The Stakes
New hires decide quickly:
First 30 days form lasting impressions
90 days determines if they’ll stay
Early experiences shape engagement
Poor onboarding costs you:
Slow ramp to productivity
Lower engagement
Higher turnover
Wasted hiring investment
What Good Onboarding Does
For the new hire:
Clarity on what success looks like
Connection to team and culture
Confidence to contribute
Path to impact
For the company:
Faster productivity
Cultural integration
Reduced turnover
Return on hiring investment
Before Day One
Preparation
Don’t wait until they show up:
Equipment ready
Accounts created
Workspace prepared (physical or virtual)
Onboarding plan documented
Checklist:
[ ] Laptop configured
[ ] Email and tools set up
[ ] Calendar invites for first week
[ ] Documentation access
[ ] Team introductions scheduled
Communication
Stay in touch between offer and start:
Send welcome message
Share what to expect day one
Introduce them to team (Slack/email)
Answer questions proactively
They should feel welcomed before they arrive.
Buddy Assignment
Assign an onboarding buddy:
Someone who can answer daily questions
Not their manager (psychological safety)
Available and engaged
Good at explaining things
Day One
Make It Special
First impressions matter:
Personal welcome from manager
Team introduction
Maybe a small gift (swag, welcome card)
Lunch with the team
Don’t make day one all paperwork.
The Basics
Get them set up:
Complete HR paperwork
Equipment and access working
Communication channels joined
Basic tools configured
Goal: Functional by end of day one.
Context Setting
Help them understand:
Company story and mission
Current priorities and goals
Team structure
How their role fits
Clear First Week Plan
Give them a roadmap:
What they’ll do each day
Who they’ll meet with
What they should read/learn
First small task
Structure reduces anxiety.
Week One
Meeting Overload (Intentional)
Schedule key meetings:
1:1 with manager (expectations)
Team members (individual intros)
Key stakeholders (context)
Buddy check-ins (daily)
Front-load relationship building.
Learning Time
Provide materials:
Product documentation
Company wiki/handbook
Past work examples
Relevant Slack channels
But don’t just dump docs. Curate what’s most important.
First Task
Give them something to do:
Small, completable
Real work (not busywork)
Low risk
Provides early win
Examples:
Fix a small bug
Write documentation
Handle a simple customer request
Improve a small process
Daily Check-Ins
Manager should check in daily:
How’s it going?
Any blockers?
What questions came up?
What do you need?
This decreases as they ramp.
First 30 Days
Clear 30-Day Goals
Define what success looks like:
Specific deliverables
Skills to develop
People to connect with
Knowledge to gain
Write these down together.
Expanding Scope
Gradually increase responsibility:
Week 1: Observe and learn
Week 2-3: Contribute with support
Week 4+: Own small things independently
Don’t throw them in the deep end, but don’t keep them on the sidelines either.
Regular 1:1s
Weekly meetings should cover:
Progress on goals
Questions and blockers
Feedback (both directions)
Adjustment needs
Feedback Early
Don’t wait for problems:
Give positive reinforcement
Address concerns immediately
Adjust expectations if needed
Create psychological safety
Early feedback prevents later crises.
First 90 Days
90-Day Plan
Build on 30-day goals:
What they should own by 90 days
Key relationships to build
Skills to develop
Impact to demonstrate
Increasing Independence
By 90 days they should:
Own meaningful work
Need less daily guidance
Understand how things work
Contribute to team decisions
If they still need hand-holding, something’s wrong.
90-Day Review
Formal checkpoint:
Review against goals
Discuss what’s working/not working
Set expectations for going forward
Confirm mutual fit
This is when both sides decide if it’s working.
Onboarding Different Roles
Engineers
Focus on:
Development environment setup
Codebase walkthrough
Architecture understanding
First PR shipped quickly
First task: Fix a small, well-scoped bug.
Designers
Focus on:
Design system and patterns
User research access
Cross-functional relationships
Design tools and files
First task: Improve one small user flow.
Salespeople
Focus on:
Product knowledge deep
Customer personas
Sales process and tools
Shadowing existing reps
First task: Run discovery calls with support.
Managers
Focus on:
Team introductions (individual and group)
Current team dynamics
Existing processes and commitments
Stakeholder relationships
First task: 1:1s with every team member.
Remote Onboarding
Extra Challenges
Remote adds difficulty:
No casual interaction
Harder to read culture
Easy to feel isolated
Technology friction
Adaptations
More structure:
Detailed written plans
More scheduled check-ins
Virtual coffee chats
Documented processes
More connection:
Video calls over messages
Team bonding activities
Buddy more important
Manager more available
Better tools:
Equipment shipped in advance
Clear tool instructions
IT support accessible
Communication norms documented
Signs of Good Onboarding
They Know What Success Looks Like
Can articulate their goals
Understand how they’ll be evaluated
Know what good work looks like
They’re Building Relationships
Know their teammates
Have go-to people for questions
Feel comfortable reaching out
They’re Contributing
Doing real work
Getting positive feedback
Feeling valued
They’re Engaged
Asking good questions
Offering ideas
Enthusiastic about the work
Signs of Poor Onboarding
They’re Confused
Unclear on expectations
Don’t know what to work on
Ask the same questions repeatedly
They’re Isolated
Haven’t connected with team
Don’t know who to ask
Feel like an outsider
They’re Frustrated
Blocked on basics (access, tools)
Not getting feedback
Feel ignored
They’re Disengaged
Low energy
Not participating
Already looking for exits
Common Mistakes
No Plan
“Figure it out” approach.
Fix: Document onboarding plan before they start.
Sink or Swim
Throwing them into complex work immediately.
Fix: Gradual ramp with support.
Information Dump
Overwhelming them with everything at once.
Fix: Curated, sequenced learning.
No Early Wins
Only giving them busywork or nothing.
Fix: Real work, small scope, achievable.
Manager Unavailable
Too busy to invest time.
Fix: Block time for daily check-ins early.
No Feedback
Waiting until problems are severe.
Fix: Continuous feedback from day one.
One-Size-Fits-All
Same onboarding for every role.
Fix: Customize for role and individual.
Key Takeaways
First 90 days determine success—invest heavily in onboarding
Prepare before day one: equipment, accounts, plan, buddy assigned
Make day one special, not just paperwork
Give clear 30/60/90 day goals—write them down together
First task should be real work, small scope, achievable quickly
Check in daily early, then weekly as they ramp
Give feedback early and often—don’t wait for problems
Remote needs more structure, more documentation, more connection
Watch for confusion, isolation, frustration—address immediately
Good onboarding pays dividends; bad onboarding wastes your hiring investment
AIMake has access to all of this
Our AI has access to the entire Startup Handbook. Ask it anything about building your startup.
Get started
Previous
Making Offers That Get Accepted
Next
Performance Management for Startups