onboarding-guide
Design comprehensive onboarding programs with milestone-based progression, resource organization, and success measurement
What this skill does
# Onboarding Guide > Create structured onboarding programs that accelerate new hire productivity through clear milestones, organized resources, and measurable outcomes. ## When to Use This Skill - Designing company onboarding - Creating role-specific plans - Building onboarding checklists - Measuring onboarding effectiveness - Improving time-to-productivity ## Methodology Foundation Based on **Gallup Q12 engagement research** and **BambooHR onboarding studies**, combining: - 30-60-90 day frameworks - Milestone-based progression - Social integration focus - Measurable competency gates ## What Claude Does vs What You Decide | Claude Does | You Decide | |-------------|------------| | Structures onboarding phases | Timeline flexibility | | Creates milestone checklists | Resource availability | | Suggests activities | Buddy assignments | | Identifies success metrics | Performance standards | | Drafts welcome materials | Cultural elements | ## Instructions ### Step 1: Define Onboarding Goals **Core Objectives:** | Objective | Measure | Target | |-----------|---------|--------| | Productivity | Time to first contribution | 30 days | | Engagement | Pulse survey score | 4+/5 | | Retention | 90-day retention | 95%+ | | Culture | Manager satisfaction | 4+/5 | | Compliance | Training completion | 100% | ### Step 2: Design Phase Structure **30-60-90 Framework:** | Phase | Days | Focus | Outcome | |-------|------|-------|---------| | **Absorb** | 1-30 | Learn, observe, connect | Understands role | | **Adapt** | 31-60 | Apply, contribute, ask | Making contributions | | **Accelerate** | 61-90 | Own, improve, lead | Fully productive | ### Step 3: Create Milestone Checklists **Checklist Categories:** 1. Administrative setup 2. Tools and systems 3. People and relationships 4. Role-specific training 5. Cultural integration ### Step 4: Build Resource Library **Resource Organization:** | Category | Contents | |----------|----------| | Company | Vision, values, org chart | | Role | JD, expectations, success criteria | | Tools | System access, tutorials | | People | Team bios, stakeholder map | | Culture | Norms, rituals, communication | ### Step 5: Measure Success **Checkpoint Assessments:** | Day | Assessment | Owner | |-----|------------|-------| | 7 | First week check-in | Manager | | 14 | Buddy feedback | Buddy | | 30 | 30-day review | Manager | | 60 | Progress assessment | Manager | | 90 | Performance review | Manager + HR | ## Examples ### Example 1: Complete 30-60-90 Onboarding Plan **Input:** ``` Create onboarding plan for: - Role: Marketing Manager - Team: 3 marketers, reports to VP Marketing - Key tools: HubSpot, Google Analytics, Figma - First project: Q2 campaign planning ``` **Output:** ``` ## 30-60-90 Onboarding Plan: Marketing Manager ### Role Overview | Element | Detail | |---------|--------| | Title | Marketing Manager | | Reports To | VP Marketing | | Team | 3 direct reports | | Start Date | [Date] | | Buddy | [Senior Marketing Manager] | --- ## Pre-Start Checklist (Before Day 1) **IT/Admin:** - [ ] Email account created - [ ] Laptop ordered and configured - [ ] Building access/badge - [ ] HubSpot seat provisioned - [ ] Google Analytics access - [ ] Figma seat added - [ ] Slack workspace invite **Manager Prep:** - [ ] First week calendar blocked - [ ] Buddy assigned and briefed - [ ] Welcome message drafted - [ ] Desk/workspace ready - [ ] Team notified of start date --- ## Phase 1: ABSORB (Days 1-30) ### Goal Understand the company, team, and role fundamentals ### Week 1: Orientation **Day 1 - Welcome** | Time | Activity | Owner | |------|----------|-------| | 9:00 | Welcome from manager | VP Marketing | | 9:30 | IT setup and security training | IT | | 10:30 | Office tour | Buddy | | 11:00 | HR paperwork and benefits | HR | | 12:00 | Team lunch | Team | | 1:30 | Company overview presentation | VP Marketing | | 3:00 | Tool access verification | Self | | 4:00 | First 1:1 with manager | VP Marketing | **Day 2-3 - Company Deep Dive** - [ ] Complete company history module - [ ] Review brand guidelines - [ ] Read last 2 quarterly reports - [ ] Watch CEO all-hands recording - [ ] Review competitor landscape doc **Day 4-5 - Marketing Team Orientation** - [ ] 1:1 with each team member (3 × 30 min) - [ ] Review team OKRs and metrics - [ ] Understand current campaigns - [ ] Access marketing dashboards - [ ] Review content calendar ### Week 2: Systems and Stakeholders **Tools Training:** - [ ] HubSpot certification (8 hours) - [ ] Google Analytics walkthrough - [ ] Figma basics tutorial - [ ] Internal wiki navigation **Stakeholder Meetings:** | Person | Role | Purpose | |--------|------|---------| | Head of Sales | Revenue partner | Understand MQL handoff | | Product Manager | Product launches | Align on roadmap | | Customer Success | Customer voice | Understand retention | | Finance | Budget partner | Understand process | ### Week 3-4: Role Immersion **Activities:** - [ ] Shadow team members on key tasks - [ ] Review past 6 months of campaigns - [ ] Analyze top-performing content - [ ] Understand lead scoring model - [ ] Map customer journey documentation **Deliverable:** Present "30-Day Observations" to VP Marketing - What I've learned - Questions I have - Initial opportunities I see --- ### Phase 1 Milestones | Milestone | Due | Status | |-----------|-----|--------| | All system access working | Day 3 | [ ] | | Completed company training | Day 5 | [ ] | | Met all key stakeholders | Day 14 | [ ] | | HubSpot certification | Day 21 | [ ] | | 30-day presentation | Day 30 | [ ] | ### Phase 1 Success Criteria | Criterion | Measure | Target | |-----------|---------|--------| | System proficiency | Can navigate independently | Yes/No | | Team relationships | Buddy rating | 4+/5 | | Company knowledge | Quiz score | 80%+ | | Engagement | Pulse check | Positive | --- ## Phase 2: ADAPT (Days 31-60) ### Goal Start contributing and take ownership of initial responsibilities ### Responsibilities Ramp **Week 5-6: Supporting Role** - [ ] Co-lead weekly marketing meeting - [ ] Review and approve team content - [ ] Begin 1:1s with direct reports - [ ] Contribute to campaign ideation **Week 7-8: Primary Ownership** - [ ] Lead weekly marketing meeting - [ ] Own content calendar decisions - [ ] First budget planning input - [ ] Draft Q2 campaign strategy ### Key Activities **Campaign Planning:** - [ ] Analyze Q1 campaign performance - [ ] Interview Sales on lead quality - [ ] Research competitor Q2 activities - [ ] Draft Q2 campaign brief **Team Management:** - [ ] Establish 1:1 cadence with reports - [ ] Complete first performance check-ins - [ ] Identify team training needs **Deliverable:** Q2 Campaign Proposal Presentation --- ### Phase 2 Milestones | Milestone | Due | Status | |-----------|-----|--------| | First campaign contribution | Day 35 | [ ] | | Leading weekly meeting | Day 42 | [ ] | | Team 1:1 rhythm established | Day 45 | [ ] | | Q2 campaign proposal | Day 60 | [ ] | ### Phase 2 Success Criteria | Criterion | Measure | Target | |-----------|---------|--------| | Campaign contribution | VP approval | Yes | | Team feedback | Skip-level pulse | 4+/5 | | Independence | Manager assessment | 4+/5 | --- ## Phase 3: ACCELERATE (Days 61-90) ### Goal Operate independently and drive impact ### Full Ownership **Responsibilities:** - [ ] Full ownership of Q2 campaign execution - [ ] Team performance management - [ ] Budget management ($X/quarter) - [ ] Cross-functional project leadership - [ ] Process improvement initiatives ### Key Activities **Campaign Execution:** - [ ] Launch Q2 campaign - [ ] Establish reporting cadence - [ ] First optimization cycle **Strategic Contribution:** - [ ] Participate in H2 planning - [ ] Identify one process improvement - [ ] Present results to leadership **Deliverable:** 90-Day Impact Report - Campaigns launched/contributed - Metrics influenced - Team development actions - Re
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.