Change Adoption: Why the New Way Feels Harder

Consider what it actually means to be good at a job. Not good in an abstract sense, but good in the moment: the right clause found quickly, the approval secured before the client calls back, the report formatted the way that this particular partner prefers it. That kind of competence is not stored in a person's head alone. It lives in their shortcuts, their templates, their trusted folder of examples, the particular sequence of steps they have learned to rely on under pressure. It is embedded in the rhythms of how they work with the people around them.

Now introduce a new system. On paper, the new route makes sense. Cleaner, more compliant, with a dashboard that finally gives leadership the visibility it needs. The case for change is real and the launch is well-handled. Training happens. The message from the top is clear. And then, three months later, something familiar: the new route is there, people use it to some extent, and yet underneath, the old way is still quietly alive.

---

What the picture actually looks like

The symptoms are recognisable across organisations of every type. Partners approving work by email rather than through the new intake system. Senior people maintaining local folders of trusted precedents because the new repository feels slower when a deadline is pressing. Newer team members completing the minimum required fields in the official form and then keeping a parallel spreadsheet to make sure nothing falls through.

Nobody is arguing openly that the old way is better. In meetings, the new system gets a broadly positive reception. The dashboard suggests reasonable progress. But in the daily contest between the new route and the old one, the old route is still winning, quietly, on speed, confidence and visible competence. What leaders often call resistance is sometimes a visible loss of fluency.

---

What the old way is actually carrying

The temptation is to call this resistance and respond with more communication, more training, or a firmer push from senior leadership. Sometimes that helps. But if the pattern persists after a competent launch with genuine senior support, more of the same rarely changes it.

What is usually happening is that the old way carries things the new way has not yet learned to carry: speed, familiarity, professional judgement, autonomy, and the ability to look credible in front of clients and colleagues. Old routines are not just personal habits. They are distributed across teams and their working environments, wired into templates, handovers, inboxes, billing rhythms and the informal expectations between people. To change a routine is not simply to change a behaviour. It is to change a pattern embedded in how the work itself flows.

In professional services especially, there is an additional layer. The old way often carries professional identity. A senior associate who can retrieve the right clause in thirty seconds, under pressure, for a client who is waiting, is not only being efficient. They are being the kind of lawyer they have spent years becoming. A new workflow that makes that same person feel slow, more dependent than they are used to being, or visibly less fluent in front of juniors, is asking for something significant. It is asking them to be temporarily less good at the job, in public, on the way to eventually becoming better.

That is not a trivial ask.

Implementation researchers such as Carl May and colleagues have shown that new practices become routine only when people can make genuine sense of them, enact them in real work and judge over time that they are worth the effort. Susan Michie and colleagues make a related point: training may increase capability, but people also need the practical opportunity and motivation to behave differently in the conditions they actually face. A strong launch and a clear case for change address neither of those things on their own.

---

A pattern from professional services

A mid-sized UK law firm introduces a new matter-opening and knowledge-management workflow. The business case is genuine: better compliance oversight, cleaner tracking of live work, easier reuse of precedent across the firm. The rollout is handled thoughtfully. Leadership is visibly behind it.

Three months in, the adoption picture is mixed. Partners are still using email to approve new matters. Senior associates have not abandoned the new repository, but they keep local clause folders for anything client-facing and time-pressured. Junior lawyers complete the required fields in the intake form and then maintain their own trackers alongside it, because the form alone does not give them the confidence that nothing important has been missed.

When a practice director looks carefully at why, the answer is not opposition. It is that the new system has not yet proven itself in the moments that matter most: when a client is waiting, when a deadline is close, when being seen to know what you are doing is part of the professional exchange. In those moments, the old route still feels safer, quicker and less exposing. The new one is not yet trusted enough to carry the weight of real work.

---

Four moves that change the contest

1. Map the shadow workflow

Before trying to increase adoption, understand what is actually happening. Ask people to show how work gets done in practice, not how the process map says it should. The parallel spreadsheets, the local folders, the email approvals, the side routes: these are diagnostic information before they are non-compliance. They show where the new route is still losing the usability contest. Treat them accordingly.

2. Ask what the old way is protecting

A genuinely useful question, asked without judgement: what does the old route preserve that the new one currently threatens? In a professional-services context, the answers often come back as speed, discretion, client responsiveness, and the ability to manage risk in the moment without depending on a system that is not yet fully trusted. Those are not unreasonable things to protect. Understanding them is the starting point for designing the new way to carry them.

3. Lower the first-use tax

Look at the first ten minutes of using the new process as if you were doing real work under real pressure. What is duplicated? What requires an extra step the old way did not? What creates uncertainty, dependency, or the feeling of being slower than you should be? Even motivated people revert when the new route is more effortful, poorly integrated, or more exposing than the old one. Another training session will not solve a design problem. Reducing duplicate entry, pre-populating fields, removing unnecessary approval loops, and protecting time to practise without performance consequence will.

4. Make competence visible in the new way

People need to see that the new route is not a step down from craft to compliance. That means senior people using it visibly, not just endorsing it in principle while quietly keeping old routes alive. It means sharing worked examples of professional judgement exercised inside the new workflow, not just examples of correct process-following. And it means recognising people who use it well in terms they care about: quality, responsiveness, confidence, not just adherence metrics.

---

The contest worth understanding

Change adoption is not primarily a communication problem, a training problem, or a resistance problem. It is a contest, played out in real work, between the old route and the new one. As long as the old route still carries more speed, confidence and professional credibility, people will keep it alive, even while agreeing with the change in principle.

The work is to redesign the conditions around the new way: lowering the cost of first use, building visible competence into it, and making sure it can carry the weight of the work that matters most. When the new route starts winning that contest in the moments people care about, adoption follows. Not because people are told to adopt, but because the new way has become, in practice, the better choice.

---

At Common Path Connection, we help leaders look beneath surface adoption problems to the routines, incentives and working norms that decide whether a new way really sticks.

Our Change & Adoption work helps teams make change usable in real work, not just convincing on paper.

If you are working through a specific adoption challenge, our Change Adoption Sprint offers a focused starting point.