Adapting to New Systems at Work Starts With the People Leading It

Oct 5

7 min read

Experienced professionals rarely leave a job because of a piece of software. They leave when they are expected to lead a change they have not been equipped for, and when their requests for help go nowhere. From the outside, this can look like someone who simply will not adapt. From the inside, adapting to new systems usually feels very different. Last year I worked with a director who reached the point of questioning whether he could continue in his role, and the trigger was the introduction of new software.

His experience deserves close attention because it reveals an assumption that organisations make much more often than they admit. Workplace adjustment to new systems is commonly judged as a matter of attitude. People who find it hard are labelled unwilling, and those who voice concerns are treated as resistant. In my work advising professionals at all levels, that interpretation is often mistaken, and responding to it can cause an organisation to lose people it will struggle to replace.

Frustration and Resistance Are Not the Same

An experienced professional can support a change and still have trouble with it. Those two elements fit together more naturally than implementation plans usually allow, and adjusting to new systems is seldom as straightforward as simply choosing to proceed. The difficulty seldom comes from the technology alone. Instead, it arises from how the technology reshapes someone’s working life, including the judgments they make, the information they depend on, and the time left for the job they were hired to do.

When I listen closely to frustrated professionals, the frustration nearly always points to something concrete. It may signal a training gap, where people have been taught the basics but not how the system applies to the realities of their role. It may point to an unrealistic workload, where learning the system has been layered on top of everything else instead of being built into the working week. Or it may reveal a genuine flaw in the system itself, such as steps that slow critical work or information that has become more difficult to locate.

Each of those causes calls for a different remedy. Better training addresses a training gap, a workload issue requires a decision about priorities, and a system flaw needs someone with authority to hear it. If you treat all three as unwillingness, none of them gets solved. In fact, the frustration usually intensifies, because people who already feel unsupported also feel misunderstood.

There is another, quieter loss that organisations often miss. Experienced professionals frequently derive their standing in a team from knowing how things work. A new system can strip away that familiarity almost overnight, leaving someone with years of service feeling slower than a colleague who started only last month. That is uncomfortable for anyone, and even more so for people who are supposed to be the steady presence others rely on.

The Leader in the Middle

The director I worked with was in precisely that position. While trying to organise training for his staff, he also recognised that he himself needed more detailed instruction. Rather than simplifying his work, the new software added another layer to it. His requests for support went nowhere, and after about three months of frustration, he questioned whether he could carry on.

It is worth stopping to consider what was being demanded of him. He was supposed to guide others through a change he had not been properly supported to understand. He was not rejecting the system or disputing its purpose. He was attempting to make it function for his team without the knowledge required to do that well. Seniority had not eliminated his need for support; if anything, it had amplified it, because other people were depending on him for answers.

PwC's Global Workforce Hopes and Fears Survey 2026, based on responses from 49,364 workers across 48 countries and regions, reported that 31% of senior executives and 24% of managers struggle to manage change. For the workforce overall, the figure was one in five. The same research found that leaders and managers were more likely than those below them to experience strain and lack of clarity around change.

Those numbers strike me as significant. Organisations often assume that the people leading change are also best equipped to handle it, and they shape support around that assumption, focusing on the frontline while leaving managers to absorb the detail on their own. The evidence suggests that the reverse assumption would frequently be safer. The people expected to carry the change are carrying double weight: once for themselves, and once for everyone who looks to them for direction.

When Leaving Feels Like the Only Option

When the director first came to me, we focused on the possibility of moving on. That was a sensible place to begin. After months of asking for help and getting nowhere, leaving can seem like the only choice still under one’s control. I helped him with his CV, and he explored another opportunity.

That opportunity did not lead to a new role, and he returned for another session. I want to be clear that exploring a move was not a mistake. Sometimes leaving is the right answer, and testing the market can give someone useful information about their value and their options. But when an exit is driven mainly by exhaustion, it is worth asking whether the problem has been fully understood before the decision is made. A career consultation is often the point where that question gets examined properly, before the decision is made rather than after.

One thing I have seen repeatedly in my work with professionals is that prolonged frustration narrows perspective. After months of unanswered requests, people can stop noticing the parts of their situation they still have the power to influence. The options have not vanished. They have simply become harder to see, and that is often when an outside view is most helpful.

Adapting to New Systems at Work When You Are Also Leading the Change

In our second discussion, we looked at what remaining in place might mean and which parts he might be able to shape. Rather than treating the matter as a simple decision between enduring it and leaving, we examined his choices one by one. Among them was submitting a formal training request. Instead of making yet another casual appeal for help, he spelt out what he needed and explained why it mattered to both his job and his team.

That difference is more significant than it first seems. When a request is cast as a personal struggle, it is easy to put it at the bottom of the list, especially in a hectic organisation where pressure is already high. By contrast, a request tied to role and team consequences poses a different question. It makes clear what the organisation may lose if the shortfall continues, and it gives the recipient something specific to respond to.

He obtained additional training. He continued to have doubts about the software, and it is important to say that plainly, because adjusting to new systems does not mean you must appreciate every aspect of them. Even so, he started to see some advantages and felt more capable of using it. When we talked again about a month later, he reported that things were getting better. His interactions with IT were smoothing out, and with a stronger grasp of the system, he was able to back his senior team more effectively, which in turn enabled them to provide better support to staff on the floor.

The software stayed in place. What changed was his capacity to work with it and to help others do the same. The system itself had not been altered at all. The change came from narrowing the divide between what he was supposed to lead and what he had actually been given to lead with.

This also offers a lesson about strengths. Seasoned leaders frequently depend on independence and self-reliance, and in many cases those qualities work well for them. Yet under strain, those same strengths can cause someone to delay asking for help too long, or to make an informal request when a formal one would carry more weight. I look at this in more detail in what happens when your strengths work against you. If this sounds familiar, it may be worth considering whether the way you have been seeking support truly fits the scale of the difficulty you are facing.

Making Adaptation Doable

Before deciding someone is resistant, an organisation should ask what makes the system hard to use in their actual work. The question sounds straightforward, yet it is rarely asked. Rollouts are often measured by go-live dates and training attendance, which tells you little about whether people can use the system effectively under the conditions they actually face. A director who attended the launch session can still be unable to answer his team’s questions three months later.

The cost of misreading this is easy to understate. An experienced leader on the verge of leaving is a major risk, and one that seldom appears on a project plan. If that person goes, the organisation loses their knowledge, their relationships, and their influence over how the team responds to change. By contrast, the cost of extra training is a wee fraction of what replacing them would require.

People are often surprised by how many challenges

in adjusting to new systems can be addressed by asking better questions instead of spending more money. It helps to treat frustration as information and to learn whether it points to training, workload, or the system itself. And it helps to distinguish between problems that require more individual practice and problems that require a decision from someone with authority. None of that calls for a new programme; it only requires a willingness to listen to what the frustration is saying. If you lead a team through change, the way you ask for and offer support affects how quickly everyone else settles.

The Question Worth Putting to Yourself

If you are struggling with a new system, especially if you are expected to lead others through it, it may help to separate two questions before deciding anything. First: can you adapt to the system? Second: have you been given what adaptation actually requires? Those questions often feel identical, and that is how experienced people end up blaming themselves for gaps they were never responsible for closing.

The issue is not merely whether people will adapt. It is whether the organisation has made adaptation workable. And if you are the one carrying the change for others, it is worth asking whether you have made your own needs as visible as you have made everyone else’s. If a structured conversation about what staying could look like in your own role would be useful, my internal development work with professionals is designed around exactly that.