Why do digital transformation projects meet resistance on the shop floor? A practical guide for employers on habit, competence anxiety and change fatigue.
The new ERP system went live after months of preparation, training was delivered and user accounts were opened. But a few weeks later you look and see: the warehouse supervisor is still writing orders in a notebook, production planning does not trust the data in the system and keeps its own Excel sheet, and the field teams fill in the digital forms all at once at the end of the shift. Management often sums up this picture as "the employees are closed to change". Yet most of the resistance seen in digital transformation projects is related not to stubbornness but to understandable psychological causes. In this article, for employers, HR leaders, factory managers and project leaders, I look at the psychology behind resistance to digital transformation and the concrete steps that can be taken to reduce it.
Why Is Digital Transformation So Hard?
Digital transformation is usually planned as a technology project: which software will be bought, which modules installed, how data will be migrated. But what happens on the ground is a change in people, more than in technology. Work that has been done a certain way for years is suddenly done with a different logic. The employee's expertise, habits, the order they have built up with colleagues and even their place in the organisation are affected by this change.
Even a system that is technically set up flawlessly does not deliver the expected benefit if users do not adopt it. What is more, running old and new methods in parallel leads to data inconsistency, double workload and a strengthening belief that the system is "unreliable anyway". For this reason, the question that determines the success of a transformation is not only "Does the system work?" but "Do people want to use this system, and can they?"
In Turkey, employees already enter these processes with a high stress load. According to Gallup's 2026 report, 66% of employees in Turkey say they experienced stress during a large part of the previous day, while the proportion of employees truly engaged in their work is only 8% (Gallup, 2026; 2025 data). In a team that is stressed and has low engagement, every innovation that brings an extra learning load is easily perceived as "one more burden".
Psychological Causes of Resistance to Change
Resistance to change does not stem from a single cause. On the ground, we generally see the following psychological processes operating together:
- Loss aversion: People tend to focus on what they will lose more than on what they will gain. The convenience the new system will bring is abstract and in the future, while the loss of the old order is concrete and today.
- Threat to competence: The person who "knew everything" in the old system becomes a novice in the new one. This can create a serious blow to confidence, especially for experienced employees and foremen.
- The power of habit: Ways of working that have been repeated for a long time become almost automatic. A new method demands much more mental effort and slows the work down in the early period.
- Loss of control: An employee who feels that the change was decided without consulting them views the process from the outside and does not take ownership of it.
- Distrust and past experiences: Projects that were left unfinished or failed in the past feed the thought "this too will pass".
- Fear of job loss and surveillance: Concern that digitalisation will turn into headcount reduction or tight performance monitoring.
- Change fatigue: Restructurings, new processes and systems arriving one after another in a short time can use up employees' capacity to adapt.
What these causes have in common is this: resistance is often directed not at the technology but at what the change means for the employee. I deal separately with the particular worries that arise in AI applications in my article on AI transformation and employee anxiety.
Resistance is often the way an employee says they are afraid of losing something; listening to it rather than suppressing it lets you understand what they want to protect.
How Does Resistance Show Itself?
Resistance to change does not always appear as open objection. It often shows itself in quiet and indirect ways:
- Old methods being kept going as a "backup" alongside the new system
- Data being entered incompletely, late or in batches
- Silence in meetings, but intense criticism in the corridor
- Generalisations such as "The system crashed again" or "This programme doesn't suit our work"
- Low attendance at training, or disinterest during training
- Errors being blamed on the system and responsibility being diffused
- An increase in short-term leave and complaints
Treating these signs as a disciplinary problem drives resistance underground. A more productive approach is to read these behaviours as feedback showing where the process is stuck. For example, data being entered in a batch at the end of the shift can show that the system is not usable in the field, that the terminals are far away or that the forms are too long.
Change Fatigue: The Invisible Load of Projects Arriving One After Another
In many organisations the real source of resistance is not a single project but accumulated changes. In the last few years a new payroll system, then quality software, then a new shift planning application have come into use, each requiring different training, a different password and a different habit. In this intensity, some employees respond to a new announcement with "not again" without looking at its content.
Change fatigue arises when a person's capacity to adapt is stretched to its limit for a long time. Its symptoms resemble burnout: exhaustion, cynicism, indifference and a feeling that "whatever I do, nothing will change". For this reason management needs to see the total load of all changes in the organisation, not just of one project.
In practice this means: not loading the same department with more than one major change in the same quarter, not moving on to the next system without being sure that one has bedded in, and sharing the results of completed projects with employees. Every project that is left unfinished or quietly abandoned reduces trust in the next one. The more employees see that the organisation carries changes through and that their efforts are rewarded, the more open they are to new initiatives. You can find the organisational side of burnout in detail in my article on preventing employee burnout.
Digital Transformation and Occupational Health: What Does the Legislation Say?
Digital transformation projects are usually on the agenda of IT and operations units; yet these projects also have consequences for occupational health and safety (OHS). Article 5(f) of the Occupational Health and Safety Law No. 6331 (İş Sağlığı ve Güvenliği Kanunu) requires the employer to develop a coherent prevention policy covering the effects of factors related to technology, work organisation, working conditions and social relationships. Article 17 of the law provides that training be given when the job or equipment changes and when new technology is applied, and be renewed in line with the changing risks.
Article 8 of the Regulation on Occupational Health and Safety Risk Assessment requires sources of psychosocial hazard to be identified and recorded as well. The Ministry of Labour and Social Security's 2024 Psychosocial Factors Information Guide lists workload and work pace, control, environment and equipment, and organisational culture among the categories of psychosocial hazard (ÇSGB, 2024). A major digital transformation touches almost all of these categories at once.
In a survey covering European workplaces, 64% of workplaces that carry out risk assessments say they have enough information on how to include psychosocial risks in them (EU-OSHA, 2025). This also means that a significant share of the rest need support on this subject. Reviewing the risk assessment in times of change supports both legal compliance and the success of the project.
Concrete Steps to Reduce Resistance to Digital Transformation
1. Explain the "why", not only the "what". Employees should be able to see which problem the new system will solve through examples from their own working day. Concrete benefits such as "we will no longer have to stay for Saturday overtime for stock counts" are more meaningful than "efficiency will rise".
2. Choose "change ambassadors" from the shop floor. Involve a few respected, experienced and curious employees from each department early in the pilot. These people both contribute to adapting the system to the shop floor and act as a trusted guide for their colleagues.
3. Reflect users' voices in the design. Simplify forms, screens and workflows using the feedback gathered during the pilot period. An employee who sees their suggestion put into practice takes ownership of the system.
4. Break learning into pieces and repeat it. Instead of long one-off training, organise short, hands-on, repeated sessions. A meta-analysis of resilience programmes showed that the effect of one-off interventions fades markedly over time, and that one-to-one and face-to-face group formats are more effective (Vanhove et al., 2016). Reinforcement is essential for learning to last.
5. Plan for the load of the transition period. Targets staying the same while the new system is being learned is one of the most common reasons employees go back to old methods. In Europe, 46% of employees already say they experience serious time pressure or work overload (EU-OSHA, 2022). Adjust targets temporarily during the transition and increase support resources.
6. Normalise making mistakes. Say openly that mistakes made during learning will not be punished, and encourage managers to share the points where they themselves struggle. Teams in which mistakes can be talked about learn faster.
7. Prioritise foremen and middle managers. They are the ones who will carry the change to the shop floor; but they too have to absorb both the pressure from above and the team's resistance. According to Gallup, managers' engagement with their work is 22% and has fallen by 9 points since 2022 (Gallup, 2026). The World Health Organization, in its guidelines on mental health at work, also presents training managers in mental health as the recommendation with the strongest evidence (WHO, 2022).
8. Make small wins visible. Share the first concrete gains the system delivers, for example a fall in the number of errors or a shorter reporting time, with the teams, and recognise those who contributed.
Say that in a medium-sized furniture factory, production tracking is moving from paper work orders to a tablet-based system. The craftsman with twenty years of experience in the cutting shop finds the tablet hard to use and is wary of making mistakes in front of younger colleagues; so he still follows the work orders on paper. Instead of forcing him through discipline, management brings him into the pilot team, asks his opinion on making the screens suitable for the shop floor and arranges a few short one-to-one training sessions for him during working hours. Within a few weeks the craftsman becomes one of the system's most effective advocates; because the change is no longer something done to him but a process he has contributed to.
How Do You Get Started in Your Organisation?
Needs analysis: The departments, roles and workflows affected by the transformation are identified. Through confidential surveys and focus group discussions, employees' concerns, learning needs, change fatigue and experiences with past projects are understood. At this stage, the system's usage data is also a valuable source: it shows in which department and at which step things are held up.
Programme: Based on the analysis results, a communication plan, a network of change ambassadors, change leadership and mental health training for managers, hands-on training for employees and, where needed, cognitive-behavioural stress management workshops are planned. A meta-analysis examining workplace stress management programmes found that cognitive-behavioural programmes consistently showed a larger effect than other types (Richardson and Rothstein, 2008). You can look at how such programmes can be structured on the corporate services page.
Measurement: System usage rates, data entry quality, error and near-miss reports, absenteeism and employee pulse surveys are monitored at set intervals. Monitoring technical indicators and human indicators together allows problems to be noticed early. You can find the general psychology of change processes in my article on the psychology of organisational change management.
Frequently Asked Questions
Are employees who show resistance to digital transformation closed to change?
Most of the time, no. Resistance is generally related to the fear of losing competence, losing control, an increased workload or losing one's job. When these concerns are listened to and addressed, even the employees who object most at the start can become important supporters of the process.
Is providing training enough to remove resistance?
On its own, no. Training is an important step, but the employee also needs to understand why they must change, be able to contribute to the process, have their workload adjusted during the transition and not fear making mistakes. Training too should be repeated and hands-on, not a one-off.
Why do experienced employees struggle more?
Experienced employees are respected for their expertise in the old system. A new system can temporarily turn them into novices, which shakes their confidence. Involving them in the design of the process and letting them learn at their own pace reduces this difficulty.
How can we support employees who are under intense stress during the change process?
Managers should talk calmly and without judgement about the points where the employee is struggling, adjust their workload temporarily and offer extra support for learning. Employees who show marked disruption in sleep, concentration or daily functioning, or who talk about hopelessness or thoughts of harming themselves, should be referred to a mental health professional; in an emergency, 112 (Turkey's emergency services) should be called. It is also helpful to remind them that seeking professional support is always an option.
Bu yazı genel bilgilendirme amaçlıdır; tanı veya tedavi yerine geçmez. Yaşadığınız güçlükler için bir ruh sağlığı uzmanına başvurmanız önerilir. Acil bir durumda lütfen 112'yi arayın.
Eda Erkan Alapala
Klinik Psikolog. İstanbul Kent Üniversitesi Klinik Psikoloji Tezli Yüksek Lisans mezunu; bilişsel davranışçı terapi, çocuk merkezli oyun terapisi ve çocuk-ergen psikoterapisi alanlarında eğitimlerini tamamlamıştır.
Eğitimler