Lean and Six Sigma in Information Technology (IT) Services
Lean Six Sigma is a data-driven improvement methodology that helps businesses to improve their processes and performance (ASQ, 2026). It integrates the principles of Lean and Six Sigma. While Lean focuses on quality enhancements through the reduction or elimination of waste, Six Sigma uses statistical tools and data to identify the causes of process variation and improve process performance and quality. Combining both methodologies, as in Lean Six Sigma, provides a systematic framework through the DMAIC (Define – Measure – Analyze – Improve – Control) cycle. The Lean Six Sigma DMAIC approach serves as a basis for determining the root causes based on collected data. It then recommends improvement measures and a periodic monitoring framework to maintain desired output over time (Pyzdek, 2003). Originally, Lean Six Sigma was intended for industrial and production process control. However, its application has been extended to other business fields, including the service sector (George and George, 2003).
Case Description and Methodology
The study focuses on the IT service department of a service organization that allocates staff at junior, senior, and managerial levels to ongoing projects and customer support activities. The projects managed by the department have varying levels of complexity. As the organisation grows and the number of projects increases, challenges have emerged in the scheduling of tasks and the distribution of the workload. This has contributed to project delays, service-quality concerns, and employee dissatisfaction.
The objective of this study is therefore to apply Lean Six Sigma (LSS) methodology to minimize process variability and eliminate activities that do not create value to optimize resource allocation in the case company. Operational data on project resource allocation and stakeholder feedback on employee workload were used. Relationships between resource allocation, project complexity, employee satisfaction, and customer outcomes during the DMAIC phases were examined.
The first DMAIC phase, known as the Define phase, aimed to identify key stakeholders in the human resource allocation process (Lameijer et al., 2021). A Project Charter was developed to define the scope of the project, while a SIPOC (Suppliers-Inputs-Processes-Outputs-Customers) diagram was used to map the various levels of the resource allocation process. Voice of the Customer (VoC) analysis was employed to capture stakeholder concerns and worries into measurable indicators of satisfaction. Together, these tools helped to uncover areas for improvement based on the customer’s expectations and the organization’s strategy.
The Measure phase is the second step in the DMAIC method. Its focus is to provide quantitative evidence of the existing system and determine the suitable data to be measured and analysed (De Koning et al., 2006). The empirical data analysed in this study consisted of employee interviews, customer feedback, and operational project records.
The Analyze phase draws on data from the Measure phase to find the root causes of the problems at hand. It used statistical tools, including Pareto charts, correlation analysis, and hypothesis testing, to assess inefficiencies found in the process (Aazadnia and Fasanghari, 2008; Pyzdek and Keller, 2024).
The Improve phase focused on system improvement. Failure Mode and Effects Analysis (FMEA) was used for a potential risk assessment. Additionally, Design of Experiments (DOE) served as a tool to evaluate the proposed improvement actions and define measurable outcomes (George, 2005). Finally, the Control phase, the last DMAIC step, was implemented to monitor the process performance, sustain the proposed improvements, and prevent the recurrence of resource allocation issues (Pyzdek, 2003). Statistical Process Control (SPC), and a Control Plan were established to sustain improvements over time.
Result and Discussion
The result of the study revealed an imbalance in resource allocation across the nine active projects evaluated in this study. While Senior employees were involved in an average of 2.25 projects, junior employees handled only 1.3 projects. However, the way resources are allocated does not reflect the complexity of the projects. Another finding relates to Employee satisfaction, where, on average, 5.67/10 reported excessive workload. Feedback from customers helps to identify delivery delays and quality problems. The relationship between resource allocation and performance was highlighted by Correlation analysis, as seen in Table 1 below. The findings show that the number of projects per employee was negatively correlated with employee satisfaction (r = −0.90) and positively associated with workload complaints (r = 0.76). These results suggest that when the number of projects assigned to individual staff members increases, there is a perceived greater workload and lower employee satisfaction. This highlights the importance of balanced project allocation. Additionally, a strong negative correlation (r = −0.73) was found between the resources allocated to projects and delivery delays, suggesting that projects that were allocated fewer resources have more delivery delay issues.
| Variable X | Variable Y | Correlation (r) |
|---|---|---|
| Number of projects per employee | Employee satisfaction | -0.90 |
| Number of projects per employee | Excessive workload complaints | 0.76 |
| Number of projects per employee | Communication complaints | 0.69 |
| Project complexity | Service quality complaints | -0.53 |
| Number of resources allocated | Delivery delay complaints | -0.73 |
| Project complexity | Delivery delay complaints | -0.56 |
Based on these findings, improvement and control measures were developed using a proposed DOE-based experimental framework, Statistical Process Control (SPC) measures, and a Control Plan. The DOE-based proposed experimental framework was formulated to evaluate interventions of controlled variables over 90 days using indicators such as resource utilization, employee satisfaction, and customer complaints (see Table 2 below).
| Improvement objective | Intervention / controlled variable | Response measure |
|---|---|---|
| Reduce senior workload | Limit projects assigned to senior resources | Senior-junior utilization ratio; number of complaints |
| Increase junior utilization | Assign more tasks independently to junior resources with appropriate supervision | Employee satisfaction; number of complaints |
| Improve communication | Introduce monthly resource allocation meetings | Communication-related complaints |
| Improve complexity-based allocation | Define resource requirements according to project complexity | Customer and employee complaints, particularly for low-complexity projects |
| Improve project monitoring | Review workload and project risks before deadlines | Workload and risk feedback |
Finally, SPC measures and a Control Plan were developed to sustain the proposed improvements by monitoring resource utilization, communication, employee satisfaction, delays, and quality issues.
Conclusion and Recommendation
The case presented in this article demonstrates how the Lean Six Sigma method can be applied to address challenges associated with resource-allocation problems in IT service operations. The statistical methods used along with the DMAIC approach, helped to use data to identify workload imbalance challenges among senior resources. Another problem observed was the insufficient utilization of junior employees, communication gaps, and inadequate consideration of project complexity as key issues affecting employee and customer outcomes. Improvement actions were proposed to support a balanced work resource allocation. A Control Plan was also developed to monitor continuous improvement.
It is important for the case company, and similar IT companies, to regularly monitor resource allocation and employees’ workload. Junior employees should be involved more in appropriate projects to reduce the workload of senior staff and improve overall resource utilization.
