When a new customer signs, /onboarding-specialist builds the kickoff and implementation plan, so you can hit first value fast. — Claude Skill

---

title: Section Organization

1. Program Design (program)

Impact: CRITICAL Description: Onboarding program architecture, kickoff frameworks, success criteria definition, and journey mapping for different customer segments.

2. Time-to-Value (ttv)

Impact: CRITICAL Description: Accelerating time-to-first-value, quick wins strategy, "aha moment" identification, and value milestone optimization.

3. Implementation (implementation)

Impact: CRITICAL Description: Project management, milestone tracking, technical configuration, data migration, and integration setup.

4. Training & Enablement (training)

Impact: HIGH Description: Training delivery methods, learning paths, enablement content, adoption strategies, and competency validation.

5. Go-Live Readiness (golive)

Impact: HIGH Description: Launch criteria, readiness checklists, pilot programs, rollout strategies, and go-live support.

6. Sales-to-CS Handoff (handoff)

Impact: HIGH Description: Transition process from sales to customer success, context transfer, expectation management, and relationship continuity.

7. Early Warning Signals (signals)

Impact: HIGH Description: Risk identification, health scoring during onboarding, intervention triggers, and escalation protocols.

8. Automation & Tech-Touch (automation)

Impact: MEDIUM-HIGH Description: Scaled onboarding programs, automated journeys, self-service resources, and digital-led enablement.

9. Stakeholder Management (stakeholders)

Impact: MEDIUM-HIGH Description: Champion development, executive alignment, multi-threaded relationships, and organizational change management.

10. Measurement & Optimization (measurement)

Impact: MEDIUM Description: Onboarding metrics, success measurement, continuous improvement, and benchmarking.

---

title: Onboarding Automation & Tech-Touch impact: MEDIUM-HIGH tags: automation, tech-touch, scaled, self-service, digital

Onboarding Automation & Tech-Touch

Impact: MEDIUM-HIGH

Not every customer needs high-touch onboarding. Automation and tech-touch programs can deliver excellent onboarding at scale, often achieving equal or better outcomes than manual programs for appropriate segments. The key is matching touch model to customer needs.

The Touch Model Spectrum

HIGH-TOUCH ←──────────────────────────────────→ TECH-TOUCH

Dedicated CSM    │    Pooled CSM    │    Digital-led
Custom program   │    Templated     │    Automated
Sync meetings    │    Async + sync  │    Self-service
1:1 training     │    Group/1:few   │    On-demand
                 │                  │
Enterprise       │    Mid-Market    │    SMB/Self-Serve
$100K+ ARR       │    $25-100K      │    <$25K

When to Use Tech-Touch Onboarding

Automated Onboarding Journey

Day 0:   Welcome email → Account activation
         ↓
Day 1:   Quick start guide → First login prompt
         ↓
Day 2:   Feature 1 tutorial → In-app guidance
         ↓
Day 3:   Progress check → Engagement email
         ↓
Day 5:   Feature 2 tutorial → Usage tips
         ↓
Day 7:   Value checkpoint → Survey/offer help
         ↓
Day 10:  Advanced features → Power user content
         ↓
Day 14:  Success check-in → Human touch option
         ↓
Day 21:  Optimization tips → Community invite
         ↓
Day 30:  Graduation → Ongoing engagement

Email Sequence Framework

Good Tech-Touch Practices

✓ Behavior-based triggers
  → Actions drive communications
  → Not just time-based
  → Relevant, not spam

✓ In-app + email coordination
  → In-app for contextual help
  → Email for re-engagement
  → Consistent messaging

✓ Easy human escalation
  → "Need help?" always visible
  → Chat, email, call options
  → Warm handoff when needed

✓ Progressive disclosure
  → Start simple
  → Unlock complexity over time
  → Don't overwhelm day 1

✓ Self-service resources
  → Comprehensive help center
  → Video tutorials
  → Community forums

Bad Tech-Touch Practices

✗ Email blast approach
  → Same emails to everyone
  → Ignore behavior signals
  → High unsubscribe rate

✗ No human fallback
  → "Figure it out yourself"
  → Frustrated users churn
  → No escalation path

✗ Overwhelming automation
  → 5 emails per day
  → Constant in-app pop-ups
  → User dismisses everything

✗ Set and forget
  → Build once, never optimize
  → Stale content
  → Poor conversion over time

✗ Generic content
  → "Dear User"
  → No personalization
  → Feels impersonal

In-App Guidance Framework

Onboarding Checklist Design

┌────────────────────────────────────────────────┐
│  Getting Started                    2 of 5 ✓  │
├────────────────────────────────────────────────┤
│  ✅ Create your account                        │
│  ✅ Complete your profile                      │
│  ⬜ Connect your first integration            │
│  ⬜ Invite a team member                      │
│  ⬜ Complete your first workflow              │
│                                                │
│  [40% complete ████░░░░░░]                    │
│                                                │
│  Need help? Chat with us →                    │
└────────────────────────────────────────────────┘

Behavioral Triggers

Email Template: Tech-Touch Welcome

Subject: Welcome to [Product] - Let's get you started

Hi [Name],

Welcome! You're now part of the [Product] community.

**Your first step (takes 2 minutes):**
[Big, clear CTA button: "Start your setup"]

Here's what you'll accomplish this week:
✓ Day 1: Set up your account
✓ Day 3: Complete your first [workflow]
✓ Day 7: See your first results

**Need help?**
→ Quick start guide: [Link]
→ Video walkthrough: [Link]
→ Live chat: [Link]

Let's make this a success,
[Signature]

P.S. Reply to this email anytime - a real human will respond.

Email Template: Re-Engagement

Subject: We noticed you haven't logged in - can we help?

Hi [Name],

We noticed you haven't logged back into [Product] since signing up.

**Common reasons people pause:**
→ Too busy right now
→ Got stuck somewhere
→ Not sure where to start

**If you're stuck, here's a 2-minute video:**
[Video thumbnail with play button]

**If you need more time, no problem.**
We'll be here when you're ready.

**If you have questions:**
→ Reply to this email
→ Chat with us: [Link]
→ Book a quick call: [Link]

Cheers,
[Signature]

Self-Service Resource Hub

Tech-Touch Metrics

Automation Tool Stack

Hybrid Touch Model

Personalization Framework

Tech-Touch Audit Checklist

□ Journey Mapping
  □ All touchpoints documented
  □ Triggers defined for each
  □ Fallbacks for non-engagement

□ Content
  □ All emails written and tested
  □ In-app guidance created
  □ Help resources complete
  □ Videos produced

□ Technical Setup
  □ Automation tool configured
  □ Triggers tested
  □ Analytics tracking live
  □ Escalation paths working

□ Human Backup
  □ Escalation criteria defined
  □ Response SLAs set
  □ Team trained on handoff

□ Measurement
  □ KPIs defined
  □ Reporting dashboard live
  □ Review cadence set

Anti-Patterns

• Automation as abandonment — Tech-touch = no touch
• One size fits all — Same journey for everyone
• Channel spam — Too many messages, too often
• Static journeys — Never updated or optimized
• No human option — Can't reach a person
• Metric vanity — Optimizing opens, not outcomes
• Tool overload — Too many systems, poor integration
• Set and forget — Built once, never reviewed

---

title: Go-Live Readiness & Launch Success impact: HIGH tags: go-live, launch, readiness, pilot, rollout

Go-Live Readiness & Launch Success

Impact: HIGH

Go-live is the moment of truth in onboarding. A successful launch builds confidence and momentum; a failed launch can permanently damage adoption. Only 30% of software implementations achieve their original go-live date. Planning and readiness assessment make the difference.

Go-Live Readiness Stages

PILOT → READINESS → GO-LIVE → STABILIZATION → OPTIMIZATION
  ↓         ↓          ↓           ↓              ↓
 Test    Validate   Launch     Support        Improve
 Small    All       Full       Issues         Expand
 Group   Criteria   Rollout    Resolution     Adoption

Pilot Program Framework

Pilot User Selection Criteria

✓ Good pilot candidates:
  → Engaged and available during pilot period
  → Represent different user types/roles
  → Willing to provide feedback
  → Tech-comfortable but not just power users
  → Include some skeptics (valuable feedback)

✗ Avoid for pilot:
  → VIPs who can't tolerate issues
  → Users on vacation or busy with other projects
  → Only enthusiasts (biased feedback)
  → Critical path users if failure = business impact

Go-Live Readiness Checklist

## Go-Live Readiness Checklist: [Customer Name]
**Target Go-Live Date:** [Date]
**Assessment Date:** [Date]
**Status:** Ready / Not Ready / Conditionally Ready

### Technical Readiness
□ Core configuration complete and tested
□ Integrations working in production
□ Data migration complete and validated
□ User accounts provisioned
□ SSO/authentication functioning
□ Performance tested under expected load
□ Backup and recovery validated
□ Security review passed

### Operational Readiness
□ Admin team trained and certified
□ End user training completed (>80% completion)
□ Support procedures documented
□ Escalation paths defined
□ Internal help resources available
□ Change management communications sent
□ User guides and documentation accessible

### Business Readiness
□ Success criteria defined and measurable
□ Baseline metrics captured
□ Executive sponsor briefed
□ Stakeholders aligned on go-live date
□ Rollback plan documented (if needed)
□ Go-live communication drafted

### Support Readiness
□ Hypercare support plan in place
□ Known issues documented with workarounds
□ War room/rapid response team identified
□ Vendor support escalation configured
□ Monitoring and alerting active

### Final Approvals
□ Customer project manager: _______________
□ Vendor project manager: _______________
□ Customer executive sponsor: _______________
□ Technical lead: _______________

Good Go-Live Practices

✓ Phased rollout
  → Start with pilot group
  → Expand in waves
  → Learn and adjust between phases

✓ Hypercare period
  → Increased support coverage
  → Rapid response to issues
  → Dedicated resources

✓ Clear communication
  → What's changing, when, why
  → Where to get help
  → Set expectations

✓ War room readiness
  → Cross-functional team available
  → Decision authority present
  → Communication channels open

✓ Success celebration
  → Acknowledge the milestone
  → Recognize contributors
  → Build momentum

Bad Go-Live Practices

✗ Big bang without pilot
  → All users at once, no testing
  → Problems hit everyone simultaneously

✗ No hypercare
  → Normal support levels
  → Issues queue up, frustration builds

✗ Silent launch
  → Users discover changes unexpectedly
  → No preparation, resistance increases

✗ Go-live on Friday
  → Weekend for issues to compound
  → No support available

✗ Premature declaration
  → "We're live!" with critical issues
  → Users lose trust immediately

Rollout Strategy Options

Launch Communication Template

## [Product] Launch Communication

### Pre-Launch (1 week before)
Subject: [Product] Going Live on [Date] - What You Need to Know

Hi Team,

On [Date], we're launching [Product] to [improve X/replace Y/enable Z].

**What's Changing:**
- [Change 1]
- [Change 2]

**What You Need to Do:**
- [ ] Complete training by [Date] - [Link]
- [ ] Review quick start guide - [Link]
- [ ] Test your login - [Link]

**Getting Help:**
- Help desk: [Contact]
- Resources: [Link]
- FAQ: [Link]

Questions? Reply to this email.

---

### Launch Day
Subject: [Product] is Now Live!

Hi Team,

[Product] is now live and ready for you to use!

**Quick Start:**
1. Log in at [URL]
2. [First step to take]
3. [Second step to take]

**Need Help?**
- Quick start guide: [Link]
- Live support: [Contact] (extra coverage this week)
- Help center: [Link]

**Report Issues:**
- Email: [support@...]
- Slack: #[channel]

Let's make this a success!

---

### Post-Launch (3 days after)
Subject: [Product] Launch Update - Tips & Support

Hi Team,

We're 3 days into [Product] - here's what you need to know:

**Quick Tips Based on Your Feedback:**
- Tip 1: [Common question answer]
- Tip 2: [Helpful shortcut]

**Known Issues:**
- [Issue 1]: [Workaround]
- [Issue 2]: Being fixed, expected [date]

**Your Feedback Matters:**
We're collecting feedback to improve your experience.
[Feedback survey link]

Keep the questions coming - we're here to help.

Hypercare Plan Template

## Hypercare Plan: [Customer Name]

**Duration:** [2 weeks recommended]
**Start Date:** [Go-live date]
**End Date:** [Date]

### Support Coverage
| Time | Coverage | Channel |
|------|----------|---------|
| Business hours | Extended team | All channels |
| After hours | On-call rotation | Email, urgent phone |
| Weekend | On-call | Emergency only |

### Response Times (During Hypercare)
| Severity | Definition | Response | Resolution |
|----------|------------|----------|------------|
| Critical | System down | 15 min | 2 hours |
| High | Major feature broken | 1 hour | 4 hours |
| Medium | Workaround available | 4 hours | 24 hours |
| Low | Minor issue | 24 hours | 72 hours |

### Daily Sync
- **Time:** [Time] daily
- **Participants:** [Customer + Vendor leads]
- **Agenda:** Issues, trends, decisions
- **Duration:** 15-30 min

### Issue Tracking
- Log all issues in [system]
- Categorize by severity and type
- Daily summary report
- Trend analysis weekly

### Exit Criteria
Hypercare ends when:
□ No critical/high issues open for 48+ hours
□ Issue volume trending down
□ Customer confirms stability
□ Handoff to standard support complete

Go-Live Success Metrics

Rollback Criteria & Plan

## Rollback Decision Framework

### Automatic Rollback Triggers
- System availability <95% for >2 hours
- Critical data loss or corruption
- Security breach

### Evaluation Triggers (Consider Rollback)
- >50% of users unable to complete core workflow
- Critical business process blocked
- Executive sponsor requests review

### Rollback Plan
1. **Decision authority:** [Name] with [backup name]
2. **Communication:** Draft ready, send within 30 min
3. **Technical steps:** [Documented procedure]
4. **User impact:** [What changes for users]
5. **Recovery timeline:** [How long to restore]
6. **Post-mortem:** Within 48 hours of rollback

Post-Go-Live Review Template

## Go-Live Review: [Customer Name]

**Go-Live Date:** [Date]
**Review Date:** [Date, ~2 weeks post]

### Metrics Summary
| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| On-time | [Date] | [Date] | ✅/❌ |
| User adoption | 80% | X% | ✅/❌ |
| Critical issues | 0 | X | ✅/❌ |
| User satisfaction | 4/5 | X/5 | ✅/❌ |

### What Went Well
- [Success 1]
- [Success 2]
- [Success 3]

### What Could Improve
- [Improvement 1] - [Action]
- [Improvement 2] - [Action]

### Lessons Learned
- [Lesson 1]
- [Lesson 2]

### Next Steps
- [ ] Transition to ongoing success
- [ ] Schedule 30-day review
- [ ] Identify optimization opportunities
- [ ] Gather success story content

Anti-Patterns

• Go-live by date, not readiness — Calendar over quality
• Skipping pilot — No validation before full rollout
• Normal support levels at launch — Users feel abandoned
• No rollback plan — Committed with no exit
• Weekend launches — No support when issues arise
• Declaring success prematurely — Before stabilization
• No post-launch review — Same mistakes next time
• Disappearing after go-live — Onboarding is not adoption

---

title: Sales-to-CS Handoff Excellence impact: HIGH tags: handoff, transition, sales, customer-success, continuity

Sales-to-CS Handoff Excellence

Impact: HIGH

The handoff from Sales to Customer Success is one of the most critical moments in the customer lifecycle. A poor handoff creates confusion, repetition, and erodes trust. 35% of customers report having to re-explain their needs after purchase — a preventable failure.

The Handoff Continuum

SALES OWNS                      JOINT                    CS OWNS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Discovery → Evaluation → Close → Handoff → Kickoff → Onboarding
                                   ↑
                         Critical Transition
                         Point of Maximum
                         Risk for Customer

Handoff Timing Models

Handoff Document Template

## Customer Handoff Document

### Company Overview
- **Company Name:** [Name]
- **Industry:** [Industry]
- **Size:** [Employees, revenue if relevant]
- **Website:** [URL]
- **Contract Value:** [ARR]
- **Contract Term:** [Length]
- **Start Date:** [Date]

### Stakeholders
| Name | Title | Role | Contact | Notes |
|------|-------|------|---------|-------|
| [Name] | [Title] | Executive Sponsor | [Email] | [Notes] |
| [Name] | [Title] | Project Lead | [Email] | [Notes] |
| [Name] | [Title] | Technical Lead | [Email] | [Notes] |
| [Name] | [Title] | End User Champion | [Email] | [Notes] |

### Why They Bought
**Primary Business Drivers:**
- [Driver 1 - the problem they're solving]
- [Driver 2]
- [Driver 3]

**What Influenced the Decision:**
- [Specific feature/capability]
- [Competitive advantage]
- [Reference/case study that resonated]

**Alternative Solutions Considered:**
- [Competitor 1]: Why not chosen
- [Competitor 2]: Why not chosen
- [Build vs Buy]: Consideration

### Success Criteria (From Sales)
**What the customer said success looks like:**
1. [Outcome 1 with specific metric if available]
2. [Outcome 2]
3. [Outcome 3]

**Timeline expectations:**
- Quick wins by: [Date]
- Full rollout by: [Date]
- ROI expected by: [Date]

### Technical Context
**Current Environment:**
- Systems to integrate: [List]
- Data sources: [List]
- Technical constraints: [List]

**Technical Concerns Raised:**
- [Concern 1]: How addressed in sales
- [Concern 2]: How addressed in sales

### Relationship History
**Sales Cycle:**
- First contact: [Date]
- Cycle length: [Weeks/months]
- Key meetings: [List notable]

**Relationship Dynamics:**
- Champion: [Name] - [Notes on relationship]
- Detractor (if any): [Name] - [Concerns]
- Political considerations: [Notes]

### Promises & Commitments
**CRITICAL: What was promised during sales:**
- [ ] [Specific commitment 1]
- [ ] [Specific commitment 2]
- [ ] [Specific commitment 3]

**What was explicitly out of scope:**
- [Item 1]
- [Item 2]

### Risks & Red Flags
| Risk | Severity | Mitigation |
|------|----------|------------|
| [Risk 1] | High/Med/Low | [Suggested approach] |
| [Risk 2] | High/Med/Low | [Suggested approach] |

### Implementation Notes
**Preferred approach:**
- [Implementation preference]

**Timeline constraints:**
- [Hard deadline if any]
- [Blackout periods]

**Resource availability:**
- [Customer resource constraints]

### Additional Context
[Any other relevant information for CS success]

---
**Handed off by:** [AE Name]
**Handed off to:** [CSM Name]
**Handoff date:** [Date]
**Handoff call completed:** Yes / No

Good Handoff Practices

✓ Documented handoff
  → Written document, not just verbal
  → Accessible to full CS team
  → Updated as information changes

✓ Warm introduction
  → Sales introduces CS personally
  → "You're in great hands with [CSM]"
  → Shows continuity of care

✓ Internal sync before customer call
  → CS reads handoff doc first
  → Clarifying questions asked
  → Prepared, not cold

✓ Sales available post-handoff
  → For questions from CS
  → For customer escalations
  → Gradual fade, not cliff

✓ Customer validation
  → "Did I capture this correctly?"
  → Surface misalignments early
  → Customer feels heard

Bad Handoff Practices

✗ Over-the-wall handoff
  → "Here's the customer, good luck"
  → No context, no introduction
  → Customer feels abandoned

✗ No documentation
  → "Just ask the customer"
  → Customer repeats everything
  → Trust erodes immediately

✗ Overpromise exposure
  → Sales committed to impossible
  → CS discovers during onboarding
  → Customer frustrated, CS blamed

✗ Champion blindness
  → Don't know who the buyer is
  → Engage wrong stakeholders
  → Lack of alignment

✗ Delayed handoff
  → Weeks pass after signing
  → Customer momentum lost
  → "Did they forget about us?"

Internal Handoff Meeting Agenda

## Internal Handoff: [Customer Name]
**Attendees:** AE, CSM, SE (if applicable), CS Leader
**Duration:** 30-45 minutes

### Agenda

1. **Document Review** (5 min)
   - CSM confirms handoff doc received and reviewed
   - Initial questions prepared

2. **Customer Context** (15 min)
   - AE walks through key points
   - Why they bought (in depth)
   - Relationship dynamics
   - Political landscape

3. **Commitments & Risks** (10 min)
   - Explicit promises made
   - Known risks and concerns
   - Red flags to watch

4. **Success Definition** (5 min)
   - What does the customer say success is?
   - What metrics matter to them?
   - Timeline expectations

5. **Transition Plan** (5 min)
   - When/how will introduction happen?
   - AE involvement post-handoff
   - Escalation during onboarding

6. **Q&A** (5 min)
   - Remaining questions from CS

Customer Introduction Meeting

## Customer Introduction Meeting
**Attendees:** Customer team, AE, CSM
**Duration:** 30 minutes

### Agenda

1. **Welcome & Introductions** (5 min)
   - AE introduces CSM
   - CSM background and role
   - Team availability

2. **Transition Overview** (5 min)
   - What changes (AE → CSM)
   - What stays the same (commitment)
   - How support works

3. **Context Validation** (10 min)
   - "Here's what I understand about your goals..."
   - Customer confirms/corrects
   - Surface any gaps

4. **Next Steps Preview** (5 min)
   - Kickoff scheduling
   - Pre-kickoff preparation
   - Immediate questions

5. **Open Discussion** (5 min)
   - Customer questions
   - Concerns to address

Handoff Quality Checklist

## Handoff Quality Assessment

### Documentation
□ Handoff document complete
□ All stakeholders identified
□ Success criteria documented
□ Technical context captured
□ Relationship notes included
□ Promises explicitly listed

### Process
□ Internal handoff meeting held
□ AE/CSM questions resolved
□ Customer introduction scheduled
□ Warm introduction completed
□ Customer validated understanding

### Relationship Continuity
□ Customer feels cared for (not handed off)
□ No information repeated by customer
□ AE available for questions
□ Escalation path clear

### Risk Mitigation
□ Red flags surfaced and documented
□ Overpromises identified
□ Mitigation plan in place

Handoff Timing Framework

Handoff Metrics

Sales-CS Alignment

Anti-Patterns

• Documentation optional — "I'll just tell you verbally"
• CS as afterthought — No CSM assigned until after close
• Cold customer contact — CSM reaches out without intro
• Assumed context — "They know why they bought"
• Champion assumption — "Talk to whoever signed"
• Promise amnesia — Commitments not transferred
• AE disappearance — Gone immediately after close
• Template neglect — Same handoff doc for all customers

---

title: Implementation Project Management impact: CRITICAL tags: implementation, project-management, milestones, configuration, data-migration

Implementation Project Management

Impact: CRITICAL

Implementation is where onboarding plans become reality. Poor project management is the #1 cause of delayed go-lives and customer frustration. Structured, transparent, and adaptive management separates successful implementations from failures.

Implementation Project Phases

DISCOVERY → DESIGN → BUILD → VALIDATE → DEPLOY → OPTIMIZE
    ↓          ↓        ↓        ↓         ↓          ↓
  Gather    Define   Execute   Test     Launch    Refine
  Reqs      Config   Setup    QA       Go-Live   Iterate

Phase Breakdown

Project Plan Template

## [Customer Name] Implementation Plan

### Overview
- **Go-Live Target:** [Date]
- **Project Manager:** [Name]
- **Executive Sponsor:** [Name]
- **Working Team:** [Names and roles]

### Phase 1: Discovery (Week 1-2)
| Task | Owner | Due | Status |
|------|-------|-----|--------|
| Current state documentation | Customer | W1D3 | |
| Requirements gathering | Joint | W1D5 | |
| Data audit | Customer | W2D2 | |
| Integration requirements | Technical | W2D4 | |

### Phase 2: Design (Week 2-3)
| Task | Owner | Due | Status |
|------|-------|-----|--------|
| Configuration design | Vendor | W2D5 | |
| Data mapping | Joint | W3D2 | |
| Integration architecture | Technical | W3D3 | |
| Design sign-off | Customer | W3D5 | |

### Phase 3: Build (Week 3-5)
| Task | Owner | Due | Status |
|------|-------|-----|--------|
| Core configuration | Vendor | W4D3 | |
| Data migration | Joint | W4D5 | |
| Integration setup | Technical | W5D2 | |
| User provisioning | Customer | W5D3 | |

### Phase 4: Validate (Week 5-6)
| Task | Owner | Due | Status |
|------|-------|-----|--------|
| QA testing | Vendor | W5D5 | |
| UAT testing | Customer | W6D3 | |
| Admin training | Vendor | W6D2 | |
| User training | Joint | W6D4 | |

### Phase 5: Deploy (Week 6-7)
| Task | Owner | Due | Status |
|------|-------|-----|--------|
| Pilot launch | Joint | W6D5 | |
| Pilot feedback | Customer | W7D2 | |
| Go-live readiness | Joint | W7D3 | |
| Go-live | Joint | W7D5 | |

RACI Matrix Template

R=Responsible, A=Accountable, C=Consulted, I=Informed

Good Implementation Practices

✓ Clear requirements upfront
  → Document before building
  → Sign-off on scope
  → Parking lot for Phase 2

✓ Regular status communication
  → Weekly written updates
  → Real-time issue visibility
  → No surprises

✓ Risk management
  → Identify risks early
  → Mitigation plans ready
  → Escalation triggers defined

✓ Change control
  → Formal change requests
  → Impact assessment
  → Scope protection

✓ Parallel workstreams
  → Don't serialize unnecessarily
  → Multiple tracks when possible
  → Faster overall timeline

Bad Implementation Practices

✗ Scope creep acceptance
  → "Yes" to every request
  → Timeline blown
  → Never reaches go-live

✗ Silent status
  → No news shared
  → Customer assumes worst
  → Trust erodes

✗ Hero dependency
  → One person knows everything
  → Vacation = crisis
  → No documentation

✗ Testing shortcuts
  → "We'll fix it in production"
  → Go-live becomes chaos
  → User confidence destroyed

✗ Big bang go-live
  → Everything at once
  → No rollback plan
  → Risk concentrated

Status Report Template

## [Customer Name] Weekly Status Report
**Week of:** [Date]
**Overall Status:** 🟢 On Track / 🟡 At Risk / 🔴 Blocked

### Progress Summary
- Completed: [What was done]
- In Progress: [What's happening]
- Coming Up: [Next week focus]

### Milestone Status
| Milestone | Target | Status | Notes |
|-----------|--------|--------|-------|
| Requirements complete | [Date] | ✅ Done | |
| Configuration complete | [Date] | 🔄 In Progress | 70% |
| Data migration | [Date] | ⏳ Pending | |
| Training complete | [Date] | ⏳ Pending | |
| Go-Live | [Date] | ⏳ Pending | |

### Risks & Issues
| Item | Impact | Status | Owner | Mitigation |
|------|--------|--------|-------|------------|
| [Risk 1] | High | Open | [Name] | [Action] |
| [Issue 1] | Medium | Resolved | [Name] | [Resolution] |

### Decisions Needed
- [ ] [Decision 1] - Owner: [Name], Due: [Date]
- [ ] [Decision 2] - Owner: [Name], Due: [Date]

### Action Items
| Action | Owner | Due | Status |
|--------|-------|-----|--------|
| [Action 1] | [Name] | [Date] | Open |
| [Action 2] | [Name] | [Date] | Complete |

### Next Steps
1. [Immediate next step]
2. [Following step]

Data Migration Framework

Integration Implementation

Risk Management Framework

Escalation Matrix

Change Request Template

## Change Request: [CR-XXX]

**Requested By:** [Name]
**Date:** [Date]
**Priority:** High / Medium / Low

### Change Description
[Detailed description of the change]

### Business Justification
[Why is this change needed?]

### Impact Assessment
- **Timeline Impact:** [X days added/removed]
- **Resource Impact:** [Additional effort required]
- **Cost Impact:** [If applicable]
- **Risk Impact:** [New risks introduced]

### Recommendation
[ ] Approve for current phase
[ ] Defer to Phase 2
[ ] Reject with rationale

### Approval
- [ ] Customer PM: [Name] - [Date]
- [ ] Vendor PM: [Name] - [Date]
- [ ] Sponsor (if major): [Name] - [Date]

Implementation Metrics

Anti-Patterns

• Waterfall rigidity — No adaptation to reality
• Scope avoidance — Every request is "out of scope"
• Over-documentation — Process over progress
• Silent suffering — Problems not escalated
• Hero culture — One person carries project
• Testing theater — Checkbox testing, not real validation
• Big bang deployment — Everything at once with no fallback
• Handoff void — Implementation ends, no one continues

---

title: Measurement & Continuous Optimization impact: MEDIUM tags: measurement, metrics, optimization, improvement, benchmarking

Measurement & Continuous Optimization

Impact: MEDIUM

What gets measured gets improved. Systematic measurement of onboarding performance enables data-driven optimization. The best onboarding programs improve 10-20% year-over-year through continuous refinement.

Onboarding Metrics Framework

┌─────────────────────────────────────────────────────────────┐
│                   METRICS HIERARCHY                          │
├─────────────────────────────────────────────────────────────┤
│  BUSINESS OUTCOMES                                          │
│  └── Retention, Expansion, NRR                              │
├─────────────────────────────────────────────────────────────┤
│  LEADING INDICATORS                                         │
│  └── Adoption, Engagement, TTV                              │
├─────────────────────────────────────────────────────────────┤
│  OPERATIONAL METRICS                                        │
│  └── Completion Rate, On-Time %, Satisfaction               │
├─────────────────────────────────────────────────────────────┤
│  ACTIVITY METRICS                                           │
│  └── Meetings, Trainings, Support Tickets                   │
└─────────────────────────────────────────────────────────────┘

Core Onboarding KPIs

Metric Definitions

## Time to First Value (TTV)
Definition: Days from account creation to first value milestone
Calculation: Value_Event_Date - Account_Created_Date
Good: <7 days (self-serve), <14 days (SMB), <30 days (Enterprise)
Bad: >30 days (any segment)

## Onboarding Completion Rate
Definition: % of customers completing all onboarding milestones
Calculation: Completed_Onboarding / Started_Onboarding * 100
Good: >85%
Bad: <70%

## On-Time Completion Rate
Definition: % completing by original target date
Calculation: On_Time_Completions / Total_Completions * 100
Good: >80%
Bad: <60%

## Onboarding NPS
Definition: Net Promoter Score at end of onboarding
Calculation: % Promoters (9-10) - % Detractors (0-6)
Good: >50
Bad: <20

## 90-Day Retention
Definition: % of customers still active 90 days after signup
Calculation: Active_Day_90 / Signed_Up * 100
Good: >95%
Bad: <85%

Measurement Dashboard

Good Measurement Practices

✓ Leading + lagging metrics
  → Leading: Engagement, adoption (predictive)
  → Lagging: Retention, NRR (outcomes)
  → Both tell the story

✓ Segment-appropriate benchmarks
  → Enterprise vs SMB vs self-serve
  → Different targets for different segments
  → Apples to apples comparison

✓ Regular review cadence
  → Weekly: Operational metrics
  → Monthly: KPIs and trends
  → Quarterly: Strategic review

✓ Actionable insights
  → Not just reporting, analysis
  → Why, not just what
  → Recommendations attached

✓ Continuous improvement
  → Track changes over time
  → A/B test improvements
  → Celebrate progress

Bad Measurement Practices

✗ Vanity metrics only
  → "100 customers onboarded!"
  → No quality measurement
  → Success theater

✗ Lagging-only measurement
  → Only see churn after it happens
  → No early warning
  → Reactive, not proactive

✗ One benchmark for all
  → Enterprise held to self-serve TTV
  → Unfair comparisons
  → Wrong incentives

✗ Measurement without action
  → Reports generated, filed
  → No decisions made
  → Data waste

✗ Infrequent reviews
  → Quarterly only
  → Trends missed
  → Slow to improve

Onboarding Funnel Analysis

Cohort Analysis Framework

Survey Framework

Onboarding NPS Survey Template

## Post-Onboarding Survey

Q1. Overall, how satisfied are you with your onboarding experience?
[1-10 scale]

Q2. How likely are you to recommend [Company] to a colleague?
[0-10 scale - NPS question]

Q3. How would you rate each aspect of onboarding?
- Communication: [1-5]
- Training quality: [1-5]
- Technical support: [1-5]
- Timeline/pace: [1-5]
- Resource availability: [1-5]

Q4. What was the best part of your onboarding experience?
[Open text]

Q5. What could we improve?
[Open text]

Q6. Do you feel prepared for ongoing success?
[Yes / Somewhat / No]

Q7. Would you be willing to be a reference?
[Yes / Maybe later / No]

Optimization Framework

A/B Testing for Onboarding

Continuous Improvement Process

1. MEASURE
   → Collect data on current performance
   → Identify metrics outside target

2. ANALYZE
   → Root cause analysis
   → Compare cohorts, segments
   → Identify patterns

3. HYPOTHESIZE
   → Develop improvement theories
   → Prioritize by impact/effort

4. TEST
   → Small-scale pilot
   → A/B test when possible
   → Measure results

5. IMPLEMENT
   → Roll out successful changes
   → Update playbooks
   → Train team

6. REPEAT
   → Return to step 1
   → Continuous cycle

Quarterly Business Review (QBR) Template

## Onboarding QBR: Q[X] [Year]

### Executive Summary
[2-3 sentences on quarter performance]

### KPI Performance
| Metric | Target | Actual | vs Prior Q | Trend |
|--------|--------|--------|------------|-------|
| TTV | X days | Y days | +/-% | ↑↓→ |
| Completion Rate | X% | Y% | +/-% | ↑↓→ |
| On-Time Rate | X% | Y% | +/-% | ↑↓→ |
| NPS | X | Y | +/-pts | ↑↓→ |
| 90-Day Retention | X% | Y% | +/-% | ↑↓→ |

### Wins
- [Win 1]
- [Win 2]
- [Win 3]

### Challenges
- [Challenge 1]: [Root cause], [Action]
- [Challenge 2]: [Root cause], [Action]

### Improvements Made This Quarter
- [Improvement 1]: [Impact]
- [Improvement 2]: [Impact]

### Next Quarter Focus
- [Initiative 1]: [Expected impact]
- [Initiative 2]: [Expected impact]

### Resource Needs
- [Need 1]
- [Need 2]

Benchmarking Framework

Metric Review Checklist

□ Weekly Review
  □ TTV trend
  □ Active onboardings status
  □ At-risk customers
  □ Blockers and escalations

□ Monthly Review
  □ All core KPIs
  □ Funnel conversion rates
  □ Survey scores and feedback
  □ Team performance

□ Quarterly Review
  □ QBR preparation
  □ Trend analysis
  □ Improvement initiatives review
  □ Resource planning

Anti-Patterns

• Measurement overload — Too many metrics, no focus
• Vanity metric focus — Looks good, means nothing
• Blame game — Metrics for punishment, not improvement
• Analysis paralysis — Measure everything, act on nothing
• Cherry-picking — Only highlight good metrics
• Benchmark misuse — Wrong comparisons
• Set and forget — Dashboards built, never checked
• Improvement theater — Announce changes, don't measure impact

---

title: Onboarding Program Design impact: CRITICAL tags: program, kickoff, journey, framework, design

Onboarding Program Design

Impact: CRITICAL

A well-designed onboarding program is the foundation of customer success. The first 90 days determine whether a customer becomes a long-term advocate or an early churn statistic. 70% of customers who churn do so within the first 90 days.

Onboarding Program Architecture

┌──────────────────────────────────────────────────────────────────┐
│                   ONBOARDING PROGRAM LAYERS                      │
├──────────────────────────────────────────────────────────────────┤
│  STRATEGIC    Goals → Success Criteria → Value Milestones       │
├──────────────────────────────────────────────────────────────────┤
│  OPERATIONAL  Project Plan → Milestones → Deliverables          │
├──────────────────────────────────────────────────────────────────┤
│  TACTICAL     Tasks → Resources → Enablement                    │
├──────────────────────────────────────────────────────────────────┤
│  TECHNICAL    Config → Integration → Data → Testing             │
└──────────────────────────────────────────────────────────────────┘

Program Design by Segment

The IMPACT Kickoff Framework

Good Program Design

✓ Segmented programs
  → Different tracks for different customer types
  → Enterprise gets dedicated resources
  → SMB gets efficient, automated support

✓ Defined success criteria upfront
  → "What does success look like in 90 days?"
  → Measurable, specific outcomes
  → Customer-defined, not vendor-defined

✓ Milestone-based progression
  → Clear checkpoints and gates
  → Celebration at each milestone
  → Adjustment points built in

✓ Flexible frameworks
  → Core structure with customization points
  → Adapts to customer pace and needs
  → Not rigid waterfall

✓ Quick wins built in
  → Value demonstration early
  → Momentum building
  → Stakeholder confidence

Bad Program Design

✗ One-size-fits-all approach
  → Enterprise customer on SMB timeline
  → Mismatched resources and expectations

✗ Feature-focused, not outcome-focused
  → "We'll train you on all features"
  → vs "We'll help you achieve X outcome"

✗ No defined end state
  → "Onboarding is complete when..."
  → Undefined success = endless onboarding

✗ Vendor-centric timeline
  → "Our standard is 30 days"
  → Ignores customer reality and constraints

✗ All setup, no value
  → 4 weeks of configuration
  → Customer sees no benefit until end

✗ Inflexible scope
  → "That's Phase 2" when customer needs it now
  → Customer frustration builds

Kickoff Meeting Agenda Template

## [Customer Name] Kickoff Meeting
**Date:** [Date]
**Duration:** 90 minutes
**Attendees:** [List with roles]

### Agenda

1. Introductions (10 min)
   - Team member roles
   - Working styles and preferences

2. Project Overview (15 min)
   - Why [Customer] chose [Product]
   - Key business drivers
   - Expected outcomes

3. Success Criteria (20 min)
   - What does success look like?
   - Measurable goals for 30/60/90 days
   - How will we measure progress?

4. Project Plan Review (20 min)
   - Phase overview
   - Key milestones
   - Dependencies and risks

5. Roles & Responsibilities (10 min)
   - RACI for key activities
   - Decision makers
   - Day-to-day contacts

6. Communication & Cadence (10 min)
   - Meeting frequency
   - Communication channels
   - Escalation paths

7. Q&A and Next Steps (5 min)
   - Immediate action items
   - Pre-work for next session

Success Criteria Definition

Success Criteria Workshop Questions

1. Business Outcomes
   - What business problem are you solving?
   - How do you measure success today?
   - What would "great" look like in 90 days?

2. User Outcomes
   - Who are the primary users?
   - What will change in their daily work?
   - How will they know it's working?

3. Technical Outcomes
   - What systems need to integrate?
   - What data needs to flow?
   - What are the technical success criteria?

4. Timeline Outcomes
   - What's driving your go-live date?
   - Are there business events we need to align to?
   - What's the cost of delay?

Onboarding Journey Map

Program Governance

Onboarding Program Checklist

□ Pre-Kickoff
  □ Handoff document received
  □ Account research completed
  □ Success criteria drafted
  □ Kickoff agenda sent
  □ Attendees confirmed

□ Kickoff
  □ Introductions completed
  □ Goals aligned and documented
  □ Project plan reviewed
  □ RACI established
  □ Communication cadence set
  □ Next steps assigned

□ Configuration
  □ Technical requirements gathered
  □ Data migration planned
  □ Integrations scoped
  □ Environment provisioned
  □ Initial setup complete

□ Training
  □ Training plan created
  □ Admin training delivered
  □ End user training delivered
  □ Documentation provided
  □ Competency validated

□ Go-Live
  □ Readiness checklist passed
  □ Pilot completed successfully
  □ Go-live plan approved
  □ Communication sent
  □ Support plan in place

□ Transition
  □ Success criteria validated
  □ Ongoing cadence established
  □ CSM relationship transferred
  □ Optimization roadmap created
  □ Onboarding closed

Anti-Patterns

• Kickoff without preparation — Shows up without knowing the customer
• Goal setting without customer input — Vendor defines success alone
• Rigid program templates — No flex for customer needs
• Milestone inflation — Too many, too detailed, overwhelming
• No executive involvement — Lack of strategic alignment
• Feature tour as kickoff — Product demo instead of outcome alignment
• Unclear roles — "Who's doing what?" questions throughout
• No baseline metrics — Can't prove value without starting point

---

title: Early Warning Signal Detection impact: HIGH tags: signals, risk, warning, intervention, health

Early Warning Signal Detection

Impact: HIGH

The best time to save a struggling onboarding is before it becomes a crisis. Most onboarding failures show warning signs 2-4 weeks before they become critical. Systematic detection and intervention can save 60-70% of at-risk implementations.

The Risk Detection Timeline

HEALTHY → EARLY SIGNALS → AT-RISK → CRITICAL → FAILED
   ↓           ↓             ↓          ↓          ↓
 Monitor    Intervene    Escalate   Rescue    Post-mortem
 Weekly     Proactive    Leadership  All-hands  Learn

         ← Best time to act →

Early Warning Signal Categories

Engagement Warning Signals

Progress Warning Signals

Technical Warning Signals

Adoption Warning Signals

Sentiment Warning Signals

Organizational Warning Signals

Good Detection Practices

✓ Systematic monitoring
  → Weekly signal review
  → Defined thresholds
  → Automated alerts where possible

✓ Multiple data sources
  → Product analytics
  → Communication patterns
  → Project tracking
  → Relationship intelligence

✓ Pattern recognition
  → One miss = note
  → Two misses = concern
  → Three misses = action

✓ Proactive inquiry
  → "How are things going?"
  → Don't wait for problems
  → Create safe space for honesty

✓ Fast response
  → Same-day acknowledgment
  → 48-hour action plan
  → Follow through visible

Bad Detection Practices

✗ Reactive-only approach
  → Wait for customer complaint
  → Miss early signals
  → Crisis management mode

✗ Single signal reliance
  → "They attend meetings, they're fine"
  → Miss sentiment, adoption issues
  → Surprise churn

✗ Hope-based assessment
  → "I'm sure it will work out"
  → Ignoring warning signs
  → Delays intervention

✗ Delayed response
  → "I'll check on that next week"
  → Issues compound
  → Customer loses confidence

✗ No escalation
  → Trying to fix alone
  → Missing resources/authority
  → Problem grows

Health Score During Onboarding

Health Score Thresholds

Intervention Playbook

Signal Detection Checklist (Weekly)

## Weekly Signal Review: [Customer Name]
**Week of:** [Date]
**Reviewer:** [CSM Name]

### Engagement Signals
□ All scheduled meetings attended? Y/N - Notes: ___
□ Email response time acceptable? Y/N - Notes: ___
□ Key stakeholders engaged? Y/N - Notes: ___

### Progress Signals
□ Milestones on track? Y/N - Notes: ___
□ Any blocked tasks? Y/N - Notes: ___
□ Scope remaining stable? Y/N - Notes: ___

### Technical Signals
□ Integrations functioning? Y/N - Notes: ___
□ Data quality acceptable? Y/N - Notes: ___
□ Any technical issues? Y/N - Notes: ___

### Adoption Signals
□ Users logging in as expected? Y/N - Notes: ___
□ Core features being used? Y/N - Notes: ___
□ Support tickets normal? Y/N - Notes: ___

### Sentiment Signals
□ Overall tone positive? Y/N - Notes: ___
□ Any concerns expressed? Y/N - Notes: ___
□ Champion engaged? Y/N - Notes: ___

### Overall Assessment
Health Score: ___/100
Status: Healthy / Monitor / At Risk / Critical
Action Needed: ___

### Next Steps
- [ ] [Action 1]
- [ ] [Action 2]

Escalation Template

## Onboarding Risk Escalation

**Customer:** [Name]
**ARR:** [Value]
**Current Phase:** [Onboarding phase]
**Escalation Date:** [Date]
**Escalated By:** [CSM Name]
**Escalated To:** [Manager/Leadership]

### Risk Summary
[2-3 sentence description of the situation]

### Warning Signals Observed
| Signal | First Noticed | Severity | Action Taken |
|--------|---------------|----------|--------------|
| [Signal 1] | [Date] | High | [Action] |
| [Signal 2] | [Date] | Medium | [Action] |

### Impact Assessment
- **Timeline Impact:** [Days/weeks at risk]
- **Relationship Impact:** [Champion, stakeholder status]
- **Revenue Impact:** [Churn risk, expansion risk]

### Root Cause Analysis
[What is causing the issue?]

### Actions Taken
1. [Action 1] - [Result]
2. [Action 2] - [Result]

### Support Requested
[ ] Executive involvement
[ ] Additional resources
[ ] Technical escalation
[ ] Commercial discussion
[ ] Other: ___

### Recommended Next Steps
1. [Recommended action 1]
2. [Recommended action 2]

### Decision Needed By
[Date]

Anti-Patterns

• Signal blindness — Ignoring obvious warning signs
• Single-thread dependency — Only talking to champion
• Optimism bias — "It'll work out"
• Delayed escalation — Waiting too long to raise issues
• Hero syndrome — Trying to fix everything alone
• Metric fixation — Missing sentiment behind numbers
• Post-mortem only — Analysis after failure, not during
• Alert fatigue — Too many signals, none prioritized

---

title: Stakeholder Management impact: MEDIUM-HIGH tags: stakeholders, champion, executive, relationships, change-management

Stakeholder Management

Impact: MEDIUM-HIGH

Successful onboarding requires more than technical execution — it requires people. Managing stakeholders across the customer organization is often the difference between successful adoption and failed implementation. 70% of digital transformation failures cite people issues, not technology.

Stakeholder Categories

┌─────────────────────────────────────────────────────────────┐
│                    STAKEHOLDER MAP                          │
├───────────────┬───────────────┬───────────────┬────────────┤
│   SPONSOR     │   CHAMPION    │   INFLUENCER  │   USER     │
│   (Power)     │   (Advocate)  │   (Affect)    │   (Use)    │
├───────────────┼───────────────┼───────────────┼────────────┤
│ • Budget      │ • Day-to-day  │ • Opinions    │ • Daily    │
│ • Authority   │ • Driver      │ • Peer impact │ • Workflow │
│ • Strategy    │ • Problem     │ • Culture     │ • Adoption │
│               │   Owner       │               │            │
└───────────────┴───────────────┴───────────────┴────────────┘

Stakeholder Roles & Responsibilities

Stakeholder Mapping Template

## Stakeholder Map: [Customer Name]

### Power/Interest Grid

              HIGH INTEREST
                   ↑
    ┌──────────────┼──────────────┐
    │   KEEP       │    MANAGE    │
    │   SATISFIED  │    CLOSELY   │
    │              │              │
LOW ←──────────────┼──────────────→ HIGH
POWER              │              POWER
    │   MONITOR    │    KEEP      │
    │   (MINIMUM   │    INFORMED  │
    │    EFFORT)   │              │
    └──────────────┼──────────────┘
                   ↓
              LOW INTEREST

### Stakeholder Details

| Name | Role | Power | Interest | Strategy | Notes |
|------|------|-------|----------|----------|-------|
| [Name] | Exec Sponsor | High | Medium | Keep satisfied | [Notes] |
| [Name] | Champion | Medium | High | Manage closely | [Notes] |
| [Name] | Tech Lead | Medium | High | Keep informed | [Notes] |
| [Name] | End User | Low | High | Keep informed | [Notes] |

### Relationship Map

Champion: [Name]
├── Reports to: [Sponsor]
├── Works with: [Peers]
├── Influenced by: [Names]
└── Influences: [Names]

Champion Development

Good Stakeholder Practices

✓ Multi-threaded relationships
  → Know 3+ people, not just one
  → Champion leaves ≠ project fails
  → Different perspectives

✓ Executive engagement
  → Regular (monthly) updates
  → Strategic alignment
  → Air cover for project

✓ Champion nurturing
  → Make them look good
  → Provide ammunition
  → Celebrate their wins

✓ Resistance management
  → Understand concerns early
  → Address, don't ignore
  → Convert skeptics to advocates

✓ Change management
  → Communication plan
  → Training for all affected
  → Support through transition

Bad Stakeholder Practices

✗ Single-threaded relationship
  → Only know champion
  → No executive connection
  → No backup relationships

✗ Champion neglect
  → Take them for granted
  → Don't celebrate wins
  → Burden without support

✗ Ignoring resistance
  → "They'll come around"
  → Resistance grows underground
  → Sabotage at go-live

✗ Surprising executives
  → Bad news arrives unfiltered
  → No air cover for issues
  → Sponsor pulls support

✗ Assuming alignment
  → "Everyone knows the goal"
  → Hidden agendas emerge
  → Political surprises

Executive Engagement Framework

Executive Update Template

## [Customer Name] - Executive Update
**Period:** [Date range]
**For:** [Executive Name]

### Status Summary
Overall: 🟢 On Track / 🟡 At Risk / 🔴 Needs Attention

### Progress Highlights
✓ [Accomplishment 1]
✓ [Accomplishment 2]
✓ [Accomplishment 3]

### Value Delivered
- [Metric/outcome achieved]
- [Business impact]

### Upcoming Milestones
- [Date]: [Milestone]
- [Date]: [Milestone]

### Decisions/Support Needed
- [Any executive action required]

### Next Update
[Date]

Handling Resistance

Resistance Intervention Playbook

Change Management Framework

Communication Plan Template

## Onboarding Communication Plan

### Objectives
- Build awareness of [Project]
- Create desire for adoption
- Enable successful transition

### Audiences
| Audience | Key Message | Channel | Frequency |
|----------|-------------|---------|-----------|
| Executives | Strategic value | Email, meeting | Monthly |
| Managers | Team impact | Team meeting | Bi-weekly |
| End users | Daily benefits | Email, training | Weekly |
| IT | Technical details | Technical meeting | As needed |

### Communication Calendar
| Date | Audience | Message | Owner |
|------|----------|---------|-------|
| [Date] | All | Project announcement | Sponsor |
| [Date] | Users | Training schedule | Champion |
| [Date] | All | Go-live reminder | Champion |
| [Date] | All | Success celebration | Sponsor |

### Key Messages by Phase
| Phase | Message |
|-------|---------|
| Kickoff | "Here's why we're doing this" |
| Build | "Here's our progress" |
| Training | "Here's how to succeed" |
| Go-live | "We're live - here's support" |
| Post-launch | "Here's what we've achieved" |

Stakeholder Health Tracking

Champion Loss Response

## Champion Loss Protocol

### Immediate Actions (Day 1)
□ Acknowledge departure with champion
□ Understand transition timeline
□ Request introduction to successor/backup
□ Document current project state

### Short-term Actions (Week 1)
□ Meet with successor (if identified)
□ Engage backup stakeholders
□ Brief executive sponsor
□ Assess project risk

### Continuity Actions (Week 2-4)
□ Rebuild relationship with new contact
□ Re-confirm success criteria
□ Validate project timeline
□ Adjust engagement approach

### Escalation Criteria
Escalate to leadership if:
□ No successor identified after 1 week
□ New contact disengaged or hostile
□ Project at risk of pause/cancellation
□ Executive sponsor also departing

Anti-Patterns

• Champion dependency — Everything through one person
• Executive avoidance — Fear of senior engagement
• Resistance ignorance — Hope skeptics disappear
• Political naivety — Ignoring organizational dynamics
• Communication absence — Not keeping people informed
• Change management skip — "Just roll it out"
• Hero worship — Over-relying on one champion
• Stakeholder surprise — Major news without preparation

---

title: Training & Enablement Delivery impact: HIGH tags: training, enablement, learning, adoption, competency

Training & Enablement Delivery

Impact: HIGH

Training is not the same as enablement. Training transfers knowledge; enablement ensures people can actually do the work. Effective training programs increase feature adoption by 40-60% and reduce support tickets by 30%.

Training vs. Enablement

Learning Modality Framework

┌─────────────────────────────────────────────────────────┐
│                   LEARNING PYRAMID                       │
│                                                          │
│              ┌──────────────────┐                       │
│              │   Teach Others   │  90% retention        │
│              │   (Help desk)    │                       │
│           ┌──┴──────────────────┴──┐                    │
│           │   Practice by Doing     │  75% retention    │
│           │   (Hands-on labs)       │                   │
│        ┌──┴─────────────────────────┴──┐                │
│        │   Discussion & Exercises       │  50% retention │
│        │   (Workshops)                  │               │
│     ┌──┴────────────────────────────────┴──┐            │
│     │   Audio-Visual (Videos, Demos)        │  20% ret.  │
│  ┌──┴───────────────────────────────────────┴──┐        │
│  │   Reading (Documentation)                    │  10%   │
│──┴──────────────────────────────────────────────┴───────│
└─────────────────────────────────────────────────────────┘

Training Audience Segmentation

Training Delivery Methods

Good Training Practices

✓ Outcome-focused curriculum
  → "After this, you'll be able to..."
  → Job-relevant scenarios
  → Clear competency targets

✓ Blended learning approach
  → Multiple modalities
  → Live + self-paced combination
  → Reinforcement over time

✓ Hands-on practice
  → Training environment access
  → Real-world exercises
  → Safe space to experiment

✓ Role-based paths
  → Admin vs. user vs. executive
  → Relevant content for each
  → Appropriate depth

✓ Just-in-time support
  → Resources when needed
  → In-app help
  → Quick reference guides

Bad Training Practices

✗ Feature tour as training
  → "Here's button X, here's button Y"
  → No workflow context
  → Forgotten immediately

✗ One-size-fits-all sessions
  → Executives bored, users lost
  → Wastes everyone's time

✗ Information dump
  → 4-hour lecture
  → No practice time
  → Cognitive overload

✗ Training once
  → No reinforcement
  → Knowledge decays
  → New hires left out

✗ No practice environment
  → "Don't click that in production"
  → Fear prevents learning

Training Curriculum Template

## [Product] Training Curriculum

### Track 1: Administrator Training
**Duration:** 4 hours
**Format:** Live workshop + hands-on

#### Module 1: Platform Overview (30 min)
- Architecture and concepts
- Navigation and interface
- Learning objectives: Understand system structure

#### Module 2: User & Access Management (45 min)
- User provisioning
- Roles and permissions
- Hands-on: Create users, assign roles

#### Module 3: Configuration (60 min)
- Settings and preferences
- Customization options
- Hands-on: Configure for your use case

#### Module 4: Integrations (45 min)
- Available integrations
- Setup and management
- Hands-on: Connect sample integration

#### Module 5: Reporting & Analytics (30 min)
- Standard reports
- Custom report building
- Hands-on: Build a report

#### Module 6: Troubleshooting (30 min)
- Common issues
- Support resources
- Escalation paths

### Track 2: End User Training
**Duration:** 90 minutes
**Format:** Virtual instructor-led

#### Module 1: Getting Started (20 min)
- Login and navigation
- Personal settings
- Learning objectives: Access and basic orientation

#### Module 2: Core Workflow (40 min)
- [Primary use case steps]
- Best practices
- Hands-on: Complete core task

#### Module 3: Tips & Productivity (20 min)
- Shortcuts and efficiency
- Mobile access
- Advanced features preview

#### Module 4: Resources & Help (10 min)
- Where to find help
- Support channels
- Q&A

Competency Validation Framework

Training Assessment Template

## Training Assessment: [Module Name]

### Knowledge Check
1. [Multiple choice question]
   a) Option A
   b) Option B (correct)
   c) Option C

2. [True/False question]
   True / False (correct)

3. [Short answer]
   Expected answer: [Key points]

### Practical Exercise
**Task:** [Describe task to complete]
**Criteria:**
- [ ] Step 1 completed correctly
- [ ] Step 2 completed correctly
- [ ] Result matches expected outcome

### Competency Assessment
| Skill | Not Yet | Developing | Proficient |
|-------|---------|------------|------------|
| [Skill 1] | [ ] | [ ] | [ ] |
| [Skill 2] | [ ] | [ ] | [ ] |
| [Skill 3] | [ ] | [ ] | [ ] |

Training Effectiveness Metrics

Train-the-Trainer Program

Enablement Resource Library

Training Schedule Template

## [Customer Name] Training Schedule

### Week 1: Administrator Training
| Date | Time | Session | Audience | Format |
|------|------|---------|----------|--------|
| Mon | 10am-2pm | Admin Training Pt 1 | IT Team | Live |
| Wed | 10am-2pm | Admin Training Pt 2 | IT Team | Live |
| Fri | 2pm-3pm | Admin Q&A | IT Team | Office hours |

### Week 2: Power User Training
| Date | Time | Session | Audience | Format |
|------|------|---------|----------|--------|
| Tue | 10am-12pm | Power User Workshop | Team leads | Live |
| Thu | 3pm-4pm | Power User Practice | Team leads | Lab |

### Week 3: End User Training
| Date | Time | Session | Audience | Format |
|------|------|---------|----------|--------|
| Mon-Fri | Self-paced | Basic Training Course | All users | E-learning |
| Wed | 11am-12pm | Live Q&A Session | All users | Virtual |
| Fri | 2pm-3pm | Office Hours | All users | Drop-in |

### Ongoing Support
- Monthly office hours: 2nd Tuesday, 2pm
- Quarterly refresher: New feature training
- Self-paced: Always available in learning portal

Anti-Patterns

• Training as checkbox — Did it once, done forever
• PowerPoint marathon — Slides without practice
• Premature training — Before system is configured
• No reinforcement — One-time event, no follow-up
• Skipping administrators — Expect them to figure it out
• Ignoring learning styles — One modality for everyone
• No success criteria — Training ends, adoption unknown
• Generic content — Not customized for customer use case

---

title: Time-to-Value Optimization impact: CRITICAL tags: time-to-value, ttv, quick-wins, aha-moment, activation

Time-to-Value Optimization

Impact: CRITICAL

Time-to-Value (TTV) is the most important metric in customer onboarding. Every additional day before a customer realizes value increases churn risk by 2-5%. The goal is to compress the time between purchase and the "aha moment" as much as possible.

The Value Timeline

CONTRACT → FIRST LOGIN → SETUP → FIRST VALUE → HABIT → FULL VALUE
    ↓           ↓          ↓         ↓           ↓          ↓
  Day 0      Day 1      Day 3      Day 7     Day 30    Day 60+

           ←── DANGER ZONE ──→  ←── MOMENTUM ──→  ←── RETENTION ──→

TTV Benchmarks by Product Type

The "Aha Moment" Framework

Identify the specific moment when customers realize value:

Quick Wins Strategy

Good TTV Practices

✓ Value before setup
  → Show what's possible before asking for configuration
  → Demo data or sample reports immediately
  → "See your potential" experience first

✓ Minimum viable onboarding
  → What's the LEAST needed to get first value?
  → Remove unnecessary steps
  → "You can customize later"

✓ Progressive complexity
  → Start simple, add complexity over time
  → Don't expose all features day 1
  → Guided feature discovery

✓ Pre-populated starting points
  → Templates, examples, sample data
  → Don't start from blank slate
  → "Start from here, customize from there"

✓ Success celebration
  → Acknowledge milestones
  → Share with stakeholders
  → Build momentum

Bad TTV Practices

✗ Setup before value
  → "First, let's configure everything"
  → 2 weeks of setup before any value
  → Customer loses enthusiasm

✗ Perfect before progress
  → "Let's get everything right"
  → Delays first value for completeness
  → Momentum killer

✗ Feature overload
  → "Let me show you everything"
  → Overwhelming, confusing
  → Paralysis, not progress

✗ Linear requirements
  → "You can't do X until Y is done"
  → Unnecessary blockers
  → Frustrated customers

✗ No early evidence
  → First month with no tangible wins
  → Buyer's remorse sets in
  → Stakeholders question purchase

TTV Acceleration Tactics

The Value Ladder

Level 5: Strategic Value
         └── Business transformation achieved
Level 4: Full Adoption
         └── All use cases implemented, optimized
Level 3: Workflow Value
         └── Key workflows automated/improved
Level 2: Feature Value
         └── Core features in regular use
Level 1: First Value
         └── Initial "aha moment" achieved
Level 0: Setup Complete
         └── Basic configuration done
Ground:  Account Activated
         └── Can log in and explore

Quick Win Identification Matrix

Value Milestone Template

## Value Milestone: [Name]

**Timeline:** Day [X]
**Owner:** [Customer/Vendor]
**Stakeholder Impact:** [Who benefits]

### Definition of Done
- [ ] [Specific measurable outcome 1]
- [ ] [Specific measurable outcome 2]
- [ ] [Validation method]

### Prerequisites
- [ ] [What must be true before]
- [ ] [Dependencies]

### Quick Win Evidence
- Screenshot/export of [specific output]
- Metric showing [specific improvement]
- Stakeholder quote/acknowledgment

### Celebration Plan
- Share with: [stakeholders]
- Format: [email/call/demo]
- Message: [value statement]

Value Demonstration Framework

TTV Blockers and Solutions

TTV Metrics Dashboard

Value Acceleration Checklist

□ Pre-Onboarding
  □ Environment pre-provisioned
  □ Sample data available
  □ Templates prepared for use case
  □ Quick-start guide ready

□ First Week
  □ "Aha moment" identified
  □ Day 1 quick win planned
  □ First value milestone defined
  □ Blockers pre-identified

□ First Value Achievement
  □ Value milestone reached
  □ Evidence captured
  □ Stakeholder informed
  □ Next milestone set

□ Momentum Building
  □ Weekly value checkpoints
  □ Wins shared broadly
  □ Expansion seeds planted
  □ Success story draft started

Anti-Patterns

• Configuration marathon — Weeks of setup before any value
• Waterfall thinking — "Phase 1 must complete before value"
• Perfectionism tax — Delays value for edge cases
• Value hiding — Don't show ROI until renewal
• One value fits all — Same "aha" for all personas
• Silent success — Value achieved but not celebrated
• Boiling the ocean — Trying to do everything at once
• Checkbox onboarding — Focus on tasks, not outcomes