team-onboarding-playbooklisted

A repeatable framework for building an onboarding playbook that ramps new team members predictably without burning out the people training them. ## When to use - A new hire is joining and you do not have a written onboarding plan. - An existing onboarding process is informal and inconsistent. - A team is growing fast and onboarding is the bottleneck. - A contractor or agency partner needs to ramp up quickly. - A team member is leaving and their knowledge needs capturing. - Onboarding currently takes too long and you want to reduce it. ## When NOT to use - For ongoing performance management (different problem). - For training on a specific technology (use targeted docs and tutorials). - For documentation strategy in general (use `documentation-strategy`). - For role definition or hiring (different upstream problem). ## Required inputs - The role: what the person will do, what success looks like at 90 days. - Existing artifacts: docs, runbooks, codebases, design files. - The team: who will mentor, who will pair, who answers what kind of question. - Tools and access: what accounts and systems the new person needs. - Time budget: how much time team members can invest in onboarding. ## The framework A good onboarding plan operates on 4 layers. Build all four. ### Layer 1: Belonging (Day 1 to Week 1) The first week is mostly about belonging, not productivity. Get this right and everything else accelerates. - Welcome message before they start. - Workspace and accounts rea