User Readiness for Salesforce

Overview

This guide covers user readiness patterns for Salesforce, including training plans, support models, and telemetry for feature adoption. These patterns are essential for ensuring successful user adoption, maximizing system value, and driving organizational change.

Related Patterns:

• Org Health Checks - Technical debt and org optimization
• Delivery Framework - Project delivery methodology
• In-App Help and Guidance Patterns - Documentation and contextual guidance design

Prerequisites

Required Knowledge:

• Understanding of change management principles
• Knowledge of training and user adoption strategies
• Understanding of Salesforce platform capabilities
• Familiarity with project delivery methodologies

Recommended Reading:

• Delivery Framework - Project delivery patterns
• Org Health Checks - Technical optimization patterns

Consensus Best Practices

• Plan training early: Include training in project planning from the start
• Tailor training to user roles: Create role-specific training programs
• Provide multiple training formats: Offer various training delivery methods
• Establish support models: Set up help desk and support processes
• Track feature adoption: Monitor how users adopt new features
• Iterate based on feedback: Use user feedback to improve training and support
• Measure training effectiveness: Track training completion and effectiveness
• Support continuous learning: Provide ongoing training and resources

Training Plans

Training Curriculum Design

Curriculum Structure:

• Foundation training: Core Salesforce concepts and navigation
• Role-specific training: Training tailored to user roles
• Feature training: Training on specific features and functionality
• Advanced training: Advanced topics for power users

Curriculum Development:

• Identify training needs by role
• Define learning objectives
• Create training content
• Develop training materials
• Test training content

Curriculum Best Practices:

• Start with basics, build to advanced
• Use real-world scenarios
• Include hands-on exercises
• Provide reference materials
• Update curriculum regularly

Role-Based Training

Role Categories:

• End users: Day-to-day system users
• Power users: Advanced users with additional permissions
• Administrators: System administrators
• Developers: Technical developers
• Managers: Users with reporting and analytics needs

Role-Specific Training Content:

• End users: Navigation, data entry, basic reporting
• Power users: Advanced features, automation, customization
• Administrators: System configuration, user management, security
• Developers: Code development, testing, deployment
• Managers: Reporting, dashboards, analytics

Role-Based Training Delivery:

• Separate training sessions by role
• Customize examples for each role
• Use role-specific scenarios
• Provide role-specific materials

Training Delivery Methods

Training Delivery Options:

• In-person training: Classroom or on-site training
• Virtual training: Online live training sessions
• Self-paced training: Online courses and tutorials
• Hybrid training: Combination of delivery methods

Training Delivery Best Practices:

• Choose delivery method based on audience
• Provide multiple delivery options
• Record training sessions for later access
• Offer training at convenient times
• Support different learning styles

Training Materials:

• User guides: Step-by-step guides
• Video tutorials: Video demonstrations
• Quick reference cards: One-page reference materials
• FAQs: Frequently asked questions
• Knowledge base: Searchable knowledge repository

Support Models

Help Desk Patterns

Help Desk Structure:

• Tier 1: Initial support, basic questions
• Tier 2: Advanced support, complex issues
• Tier 3: Technical support, system issues
• Escalation: Escalate to development or vendor support

Help Desk Best Practices:

• Define support tiers clearly
• Train support staff
• Use ticketing system
• Track support metrics
• Continuously improve support

User Support Workflows

Support Workflow:

1. User submits support request
2. Request triaged and assigned
3. Support staff responds and resolves
4. Request closed and user notified
5. Feedback collected

Support Workflow Best Practices:

• Define clear workflows
• Set response time SLAs
• Track resolution times
• Collect user feedback
• Improve workflows based on feedback

Support Tools:

• Ticketing system: Track support requests
• Knowledge base: Self-service support
• Chat support: Real-time support
• Phone support: Voice support
• Email support: Asynchronous support

Support Escalation Procedures

Escalation Triggers:

• Complexity: Issue too complex for current tier
• Time: Issue not resolved within SLA
• Criticality: Critical issue requiring immediate attention
• Authority: Issue requiring higher authority

Escalation Procedures:

• Define escalation criteria
• Document escalation paths
• Train staff on escalation
• Track escalation metrics
• Review escalation effectiveness

Escalation Best Practices:

• Escalate promptly when needed
• Provide context when escalating
• Follow up on escalated issues
• Learn from escalations
• Improve to reduce escalations

Telemetry for Feature Adoption

Adoption Metrics

Key Adoption Metrics:

• Feature usage: Percentage of users using feature
• Feature frequency: How often feature is used
• Feature depth: How extensively feature is used
• User satisfaction: User satisfaction with feature
• Time to adoption: Time for users to adopt feature

Adoption Metric Tracking:

• Define adoption metrics
• Implement tracking
• Collect adoption data
• Analyze adoption trends
• Report on adoption

Feature Usage Tracking

Usage Tracking Implementation:

• Event tracking: Track user events and actions
• Analytics: Use Salesforce Analytics or external tools
• Custom tracking: Implement custom tracking
• User surveys: Collect user feedback

Usage Tracking Patterns:

• Track feature access
• Track feature interactions
• Track feature completion
• Track feature errors
• Track feature performance

Usage Tracking Best Practices:

• Track meaningful metrics
• Respect user privacy
• Analyze usage patterns
• Identify adoption barriers
• Optimize based on usage data

User Engagement Patterns

Engagement Metrics:

• Login frequency: How often users log in
• Session duration: How long users stay in system
• Feature exploration: How users explore features
• Feature mastery: How users master features

Engagement Analysis:

• Identify engaged users
• Identify disengaged users
• Analyze engagement patterns
• Develop engagement strategies
• Measure engagement improvements

Engagement Strategies:

• Onboarding programs
• Feature announcements
• User success stories
• Gamification
• Recognition programs

Training Effectiveness Measurement

Training Metrics

Training Effectiveness Metrics:

• Completion rate: Percentage completing training
• Time to competency: Time to reach competency
• Knowledge retention: Knowledge retained after training
• Application: Application of training to work
• Satisfaction: User satisfaction with training

Training Measurement:

• Track training completion
• Assess knowledge before and after
• Survey user satisfaction
• Observe user application
• Measure business impact

Continuous Improvement

Improvement Process:

• Collect training feedback
• Analyze training effectiveness
• Identify improvement opportunities
• Implement improvements
• Measure improvement impact

Improvement Best Practices:

• Regular feedback collection
• Data-driven improvements
• Iterative improvement process
• Stakeholder involvement
• Continuous monitoring

Q&A

Q: How do I create an effective training plan for Salesforce?

A: Create effective training by: (1) Identifying training needs by role (what each role needs to know), (2) Defining learning objectives (what users should learn), (3) Creating role-specific training (tailor to user roles), (4) Providing multiple formats (in-person, online, self-paced), (5) Including hands-on practice (sandbox exercises), (6) Measuring effectiveness (completion rates, competency), (7) Iterating based on feedback.

Q: What training formats should I offer?

A: Offer multiple training formats: (1) In-person training (classroom, workshops), (2) Online training (webinars, e-learning), (3) Self-paced training (Trailhead, documentation), (4) Hands-on practice (sandbox exercises), (5) Video tutorials (recorded sessions), (6) Job aids (quick reference guides), (7) Mentoring (one-on-one support). Different users prefer different formats - offer variety.

Q: How do I establish a support model for users?

A: Establish support by: (1) Creating help desk (ticketing system, support team), (2) Defining support tiers (Level 1, 2, 3 support), (3) Setting SLAs (response times, resolution times), (4) Providing self-service (knowledge base, FAQs), (5) Training support staff (ensure they can help), (6) Tracking support metrics (ticket volume, resolution time), (7) Iterating based on feedback.

Q: How do I track feature adoption?

A: Track feature adoption by: (1) Using telemetry (login frequency, feature usage), (2) Monitoring usage metrics (who uses what features, how often), (3) Analyzing user behavior (engagement patterns, feature exploration), (4) Identifying adoption barriers (why users don’t adopt), (5) Measuring adoption rates (percentage of users adopting), (6) Tracking trends over time, (7) Optimizing based on data.

Q: What metrics should I track for user readiness?

A: Track metrics: (1) Training completion rate (percentage completing training), (2) Time to competency (time to reach competency), (3) Knowledge retention (knowledge retained after training), (4) Feature adoption (percentage adopting features), (5) User engagement (login frequency, session duration), (6) Support ticket volume (fewer tickets = better readiness), (7) User satisfaction (satisfaction surveys).

Q: How do I measure training effectiveness?

A: Measure training effectiveness by: (1) Tracking completion rates (percentage completing training), (2) Assessing knowledge (before and after tests), (3) Surveying satisfaction (user satisfaction with training), (4) Observing application (do users apply training to work?), (5) Measuring business impact (improved productivity, reduced errors), (6) Tracking time to competency (how long to become proficient).

Q: How do I improve user engagement?

A: Improve engagement by: (1) Onboarding programs (welcome new users, guide them), (2) Feature announcements (communicate new features), (3) User success stories (share how others use Salesforce), (4) Gamification (badges, leaderboards), (5) Recognition programs (recognize power users), (6) Regular communication (newsletters, updates), (7) Addressing barriers (remove obstacles to adoption).

Q: What is the difference between training and support?

A: Training teaches users how to use Salesforce (initial learning, new features). Support helps users when they have issues (troubleshooting, problem-solving). Training is proactive (before issues), support is reactive (when issues occur). Both are essential - training reduces support needs, support helps users when training isn’t enough.

Q: How do I create role-specific training?

A: Create role-specific training by: (1) Identifying user roles (Sales Rep, Manager, Admin, etc.), (2) Defining role requirements (what each role needs to know), (3) Creating role-specific content (tailor to role needs), (4) Using role-based scenarios (real-world examples for each role), (5) Providing role-specific exercises (practice relevant tasks), (6) Measuring role-specific competency (assess role-specific skills).

Q: What are best practices for user readiness?

A: Best practices include: (1) Plan training early (include in project planning), (2) Tailor training to roles (role-specific programs), (3) Provide multiple formats (various delivery methods), (4) Establish support models (help desk, support processes), (5) Track feature adoption (monitor usage), (6) Iterate based on feedback (improve continuously), (7) Measure effectiveness (track metrics), (8) Support continuous learning (ongoing training).

Related Patterns

• Org Health Checks - Technical debt and org optimization
• Delivery Framework - Project delivery methodology
• Testing Strategy - User acceptance testing patterns