---
name: employee-onboarding-plan-builder
description: Build a structured onboarding plan that gets a new hire productive fast and makes them feel set up to succeed. Use this skill whenever a user needs an employee onboarding plan, a 30-60-90 day plan, a new-hire ramp, or says 'onboard this new hire', 'build a 90-day plan', or 'our onboarding is chaos'. Trigger whenever a new employee's first weeks need to be structured for speed to productivity and retention.
---

# Employee Onboarding Plan Builder

## What this does and why it matters
The first 90 days determine whether a hire becomes productive and stays. Chaotic onboarding wastes the expensive early weeks and drives early attrition. This skill builds a structured onboarding plan that ramps the new hire to real contribution quickly, with clear expectations, the right connections, and early wins that build confidence.

## Inputs to gather
1. The role, its responsibilities, and what success looks like at 30, 60, and 90 days.
2. The tools, systems, and access the person needs.
3. The people they should meet and who supports their ramp.
4. Any required training, compliance, or role-specific ramp.

## Method

### 1. Front-load setup and belonging
Week one is about access, tools, context, and connection, not output. A new hire blocked on a login or unsure who to ask starts slow. Make them feel welcome and equipped first.

### 2. Sequence learning before doing
Structure the ramp so context and training come before ownership. Give reading, shadowing, and small tasks before full responsibility.

### 3. Set 30-60-90 expectations
Define what "getting up to speed" (30), "contributing" (60), and "owning" (90) look like for this role, so the hire and manager share a picture of progress.

### 4. Engineer early wins
Plan a meaningful but achievable early task, since an early win builds confidence and signals fit both ways.

### 5. Build in check-ins and feedback
Scheduled manager check-ins across the 90 days, so problems surface early and the hire feels supported, not dropped.

### 6. Name the support network
A buddy or point person, and the key relationships to build, so the hire is not navigating alone.

## Output format
ALWAYS use:

# Onboarding Plan: [Role] | [Name]
## Before day one (access, tools, setup checklist)
## Week one (context, connection, first tasks)
## 30 days (learning goals + first win)
## 60 days (contributing goals)
## 90 days (ownership goals)
## Key relationships and support (buddy, stakeholders)
## Check-in schedule
## Success criteria at each milestone

## Anti-patterns to avoid
- Throwing the hire into output before context.
- No access or tools ready on day one.
- Vague expectations, so the hire cannot tell if they are on track.
- No check-ins, so struggles surface too late.

## Example
For an ops coordinator, the plan readies access before day one, spends week one on shadowing and tool setup, sets a first-win task at day 20, and defines clear 30-60-90 milestones with biweekly check-ins.