Onboarding Playbook
Overview
Design comprehensive onboarding playbooks that accelerate time-to-value, ensure customer success, and build strong product adoption. Effective onboarding sets the foundation for long-term customer health, expansion, and retention.
Onboarding Goals
Primary Objectives:
- Get customer live on the product (time-to-value: <30 days)
- Achieve 80% adoption of core features within 60 days
- Build internal champion for product expansion
- Establish positive relationship and trust
- Enable customer to operate independently
Success Metrics:
- Time to first value: 7-14 days
- First 30 days: Core workflows operational
- By day 60: 80% core features adopted; team trained
- By day 90: Expansion conversation; roadmap discussion
- By month 6: Renewal conversation with confidence
Onboarding Playbook Template
Phase 1: Pre-Implementation (Days -7 to 0)
Week Before Go-Live:
Kickoff Meeting (30-60 min):
- Attendees: Customer PM/owner, IT lead, CSM, Implementation lead
- Agenda:
- Customer success plan overview
- Timeline and milestones
- Roles and responsibilities
- Success criteria definition
- Risk identification
Deliverables:
- [ ] Success plan documented (shared document)
- [ ] Timeline and key dates confirmed
- [ ] Customer DRI (Directly Responsible Individual) named
- [ ] Escalation path defined
- [ ] Communication cadence set (weekly check-ins)
Pre-Implementation Prep:
- [ ] Customer provides data (systems to integrate, data formats)
- [ ] Vendor prepares: Sandbox environment, test data, configurations
- [ ] Customer: Network access, credentials, IT approvals
- [ ] Vendor: Training materials, documentation, runbooks
Stakeholder Alignment:
Role | Name | Company | Responsibility | Communication Freq
-----|------|---------|-----------------|------------------
Executive Sponsor | [Name] | Customer | Executive alignment; approval | Monthly
Project Lead | [Name] | Customer | Day-to-day project ownership | Weekly
IT Lead | [Name] | Customer | System access; security; infrastructure | Weekly
Power Users | [Names] | Customer | Feature validation; training peers | 2x/week
CSM | [Name] | Vendor | Overall account; success planning | 2x/week
Implementation Lead | [Name] | Vendor | Technical implementation | 2x/week
Product SME | [Name] | Vendor | Feature training; workflow design | As neededPhase 2: Implementation & Enablement (Days 1-30)
Week 1: Discovery & Design
WEEK 1 ACTIVITIES:
MONDAY - Kickoff:
- Welcome call with full team
- Review success plan and timeline
- Agree on communication cadence
- First weekly check-in scheduled
TUESDAY - Technical Setup:
- Data export from legacy system (if migration needed)
- Credential provisioning and access testing
- System configuration begins (workflows, integrations)
- Environment validation
WEDNESDAY - Process Mapping:
- Current state process walkthrough
- Future state design (how workflows will work in new system)
- Pain points identified
- Change management concerns raised
THURSDAY - Initial Training:
- 2-hour system overview training
- Navigation and UI walkthrough
- Admin and user roles explained
- Q&A session
FRIDAY - Week 1 Review:
- What's complete? (data loaded, core config done)
- Blockers or issues? (address by EOD)
- On track for Week 2? (Yes/No; adjustments if needed)
- Team confidence level? (survey)Week 2-3: Configuration & Pilot
WEEK 2-3 ACTIVITIES:
CONFIGURATION:
- Map legacy data to new system fields
- Build integrations with dependent systems
- Configure workflows and automation rules
- Test configurations with sample data
- Validate data accuracy
PILOT TESTING:
- Select 3-5 power users for pilot
- Conduct live transactions with real use cases
- Gather feedback on workflows
- Identify usability gaps
- Refine configurations based on feedback
TRAINING PLAN:
- Day 1: Admin/Workflow training (2 hours)
- Day 2: Data migration overview (1 hour)
- Day 3: Hands-on practice (2 hours)
- Day 4: Edge cases and exceptions (1 hour)
- Day 5: Train-the-trainer for power users (1 hour)
SUCCESS CRITERIA FOR WEEK 2-3:
- Core workflows configured and tested
- Data migrated and validated
- Pilot team comfortable with workflows
- Integration testing complete and successful
- No critical blockersWeek 4: Go-Live Preparation
WEEK 4 ACTIVITIES:
GO-LIVE PREPARATION:
- Final data migration (production data)
- Cutover plan documented (what's turning off, what's turning on)
- Rollback plan documented (in case of critical issues)
- Support escalation path confirmed
- Go-live schedule finalized (date, time window, teams)
FINAL TRAINING:
- End-user training for all 30 users (4 sessions x 30 min)
- Knowledge base created and shared
- Quick reference guides printed
- FAQ document reviewed
- Recorded training available
GO-LIVE DECISION GATE:
- Vendor: All critical configurations complete (Yes/No)
- Customer: Team trained and confident (Yes/No)
- Data: Migration validated; zero errors (Yes/No)
- Support: Escalation path ready; 24/7 if needed (Yes/No)
- Risk: Identified and mitigated; no blockers (Yes/No)
IF ALL YES: Proceed to go-live
IF ANY NO: Delay and resolve before proceedingPhase 3: Launch & Hypercare (Days 31-45)
Go-Live Week:
GO-LIVE SCHEDULE:
Monday 9:00 AM - Go-Live Meeting:
- All teams on call
- Final system checks
- Load production data
- Activate new system
- De-activate legacy system
Monday 9:30 AM - First Transactions:
- Power users execute first transactions
- Live support from implementation team
- Issues logged and resolved immediately
- Feedback gathered
Monday 2:00 PM - Team Rollout:
- Phased rollout to all users
- Training reinforcement
- Real-time support available
- Managers monitoring adoption
Tuesday-Friday - Hypercare:
- CSM + implementation team monitoring 24/7
- On-call support for any issues
- Daily sync meetings (30 min)
- Issue escalation triggers immediate response
- Performance monitoring (system health, data accuracy)
GO-LIVE METRICS:
- System uptime: 99.9%+
- All critical workflows operational
- User adoption: 100% of power users active
- Issue resolution: <2 hours average
- Data accuracy: 100% validation
- Support: 0 critical issues unresolvedHypercare Support (2-4 weeks post-go-live):
HYPERCARE TEAM:
- CSM (primary contact for business issues)
- Implementation Lead (technical issues)
- Product SME (feature/workflow questions)
- Escalation: Vendor VP if critical issues
AVAILABLE 24/7 FOR:
- Production outages
- Data accuracy issues
- Critical workflow failures
- Security/compliance issues
AVAILABLE BUSINESS HOURS FOR:
- Training questions
- Process optimization
- Non-critical issues
- Enhancement requests
ISSUE SEVERITY:
P1 (CRITICAL):
- System down or unavailable
- Data loss or corruption
- Security breach
- SLA: 30-minute response, 4-hour resolution
P2 (HIGH):
- Core workflow not functioning
- Performance degradation
- Workaround available
- SLA: 2-hour response, same-day resolution
P3 (MEDIUM):
- Non-core functionality issue
- User confusion on feature
- Workflow slower than expected
- SLA: 4-hour response, 24-hour resolution
P4 (LOW):
- Enhancement request
- Documentation question
- UI preference
- SLA: Next business day response
DAILY HYPERCARE MEETING (15 min):
- P1 issues: Are they resolved? (Yes/No; if no, escalate)
- Key metrics: System health, adoption, satisfaction
- Feedback: What's working well? What needs attention?
- Next day focus: What's priority?Phase 4: Transition to Support (Days 46-90)
Week 7-8: From Hypercare to Standard Support
TRANSITION PLAN:
Week 7:
- Hypercare team on 9-5 support (instead of 24/7)
- CSM takes on account health monitoring
- Customer support ticket system activated
- Training on support processes
Week 8:
- Transition complete to standard support
- SLA: Business hours; P1 next morning
- Customer escalation: CSM → Vendor Support
- Final go-live retr