This curriculum spans the equivalent of a multi-workshop operational redesign program, addressing the granular decision-making required to align Six Sigma methods with service desk workflows, cross-functional handoffs, and existing IT service management frameworks.
Module 1: Defining Service Desk Value Streams for Six Sigma Alignment
- Select which incident resolution pathways to map based on volume, customer impact, and rework frequency
- Determine whether to include self-service interactions in process maps or treat them as a separate stream
- Decide on the boundary of the value stream—include or exclude backend IT operations dependencies
- Identify primary customer touchpoints that contribute to SLA breaches for inclusion in baseline metrics
- Resolve conflicts between ITIL process boundaries and Six Sigma process scope definitions
- Validate process ownership with stakeholders when cross-functional handoffs exist between service desk and network teams
Module 2: Establishing Baseline Metrics and Data Collection Protocols
- Choose between first-call resolution rate and resolution within SLA as the primary defect metric
- Implement automated data extraction from ticketing systems to reduce manual logging errors
- Define what constitutes a "defect" for incident categorization—include or exclude user error cases
- Address inconsistent tagging practices across shifts by creating standardized logging rules
- Decide whether to normalize metrics by ticket volume, agent count, or business unit
- Integrate customer satisfaction (CSAT) scores with operational data despite delays in survey response timing
Module 3: Root Cause Analysis in High-Volume Incident Environments
- Select Pareto analysis thresholds—determine if top 20% of incident types justify 80% of delays
- Conduct 5-Why analysis on recurring password reset failures while accounting for user behavior variables
- Use fishbone diagrams to separate technology, process, and training factors in access provisioning delays
- Decide whether to escalate root cause investigations for intermittent system outages or treat as noise
- Balance depth of RCA with turnaround time pressure in Level 1 support environments
- Validate root causes identified through agent interviews with system log correlation
Module 4: Designing and Piloting Process Improvements
- Redesign escalation workflows to reduce handoff delays while maintaining audit trail requirements
- Implement standardized troubleshooting checklists and measure impact on mean time to resolve (MTTR)
- Test automated ticket routing rules based on keyword detection against false classification rates
- Introduce knowledge base article prompts during ticket creation and track adoption by agents
- Modify shift scheduling to align with incident volume peaks and assess impact on backlog
- Run A/B testing on two versions of a change approval workflow within different support teams
Module 5: Statistical Process Control and Performance Monitoring
- Set control limits for daily ticket volume using historical data and adjust for seasonal trends
- Determine sampling frequency for monitoring first response time—real-time vs. hourly aggregation
- Respond to out-of-control signals in defect rate charts with structured investigation protocols
- Differentiate between common cause variation and special cause events such as system migrations
- Integrate control charts into team dashboards without overwhelming frontline staff with data
- Adjust performance thresholds when organizational changes affect baseline conditions
Module 6: Change Management and Sustaining Gains
- Update standard operating procedures after process changes and track compliance through audits
- Re-train agents on revised workflows while minimizing disruption to daily operations
- Assign process owners to monitor adherence and address deviations in real time
- Embed revised KPIs into performance review criteria for team leads
- Conduct monthly process health reviews with operations and quality assurance teams
- Decide when to retire temporary countermeasures after sustained performance improvement
Module 7: Scaling Six Sigma Across Multiple Service Desk Units
- Standardize metric definitions across geographically distributed teams with different tools
- Adapt improvement templates for local regulatory or language requirements without losing comparability
- Allocate Black Belt resources across competing initiatives based on ROI and risk exposure
- Harmonize incident classification schemas when consolidating data from multiple ticketing systems
- Coordinate improvement timelines to avoid overloading shared backend support teams
- Establish a central governance board to prioritize projects and resolve cross-team conflicts
Module 8: Integrating Six Sigma with IT Service Management Frameworks
- Map Six Sigma defect categories to ITIL incident and problem management records
- Align DMAIC project timelines with change advisory board (CAB) approval cycles
- Coordinate Six Sigma initiatives with ongoing ISO 20000 compliance efforts
- Integrate voice-of-the-customer data from service reviews into project charters
- Use service level agreement (SLA) breaches as input for selecting improvement projects
- Ensure configuration management database (CMDB) accuracy to support root cause analysis