Onboarding Plan Builder

Onboarding is the highest-leverage period in the entire employment relationship and most companies treat it as admin. A typical pattern: laptop on Day 1, scattered intros, sink-or-swim by week three, ramp drags into month six, disengagement by month nine, exit by month twelve. The cost isn't a slow start — it's a hire that never fully arrives. The skill builds the structured 90-day ramp that prevents that, broken into three phases with different purposes and different manager investment levels.

Absorb (Days 1–30) is for learning, observing, and building relationships. Manager investment is high — daily check-ins early in the first week, structured 1:1s after that. Outcomes by Day 30: deep understanding of company, team, and role; key stakeholders met; one small visible deliverable shipped; the new hire feels connected. Contribute (Days 31–60) shifts to delivery — owning specific workstreams, identifying improvement opportunities, weekly 1:1s coaching rather than checking in. Own (Days 61–90) is full ownership with standard cadence — proposing and implementing the improvement spotted earlier, contributing to team strategy, mentoring the next new starter.

Pre-boarding gets explicit treatment because the gap between offer acceptance and Day 1 is high-risk for drop-off and high-leverage for momentum. A welcome message within 24 hours of acceptance, equipment shipped pre-Day 1 (nothing kills momentum like "waiting for the laptop"), a curated reading pack capped at five documents — not the whole knowledge base — and all paperwork done digitally before they start. Day 1 should be about people, not forms.

The buddy system is designed deliberately. A peer, not the manager. Someone who's been in the role 6–12 months — long enough to know things, recent enough to remember being new. Lightweight brief on what to cover: culture norms, unwritten rules, who to ask for what. Time-bound to 6–8 weeks. The buddy answers the "stupid questions" the new hire won't ask the manager.

Reviews at 30, 60, and 90 days are structured, not improvised. Each has an agenda. The 30-day review includes a feelings check — "how are you feeling?" is a more important question in the first month than "what are you working on?" The 90-day review reverses the feedback flow: what could we improve about onboarding? Every new hire is a data point for the next one.

The plan customises by role type. Managers get extended Absorb phases and skip-level meetings before they start managing. Technical roles get codebase walkthroughs and a small well-defined first technical task — not critical-path work. Remote hires get double check-in frequency in weeks 1–2, video-on for initial meetings, and structured virtual coffee chats so social integration doesn't depend on accident.