Change Management

The leadership decision: improve adoption, change the design or reconsider the commitment?

Consider an illustrative new intake system. Employees attend training and agree with the purpose, yet continue using spreadsheets. One explanation is habit or reluctance. Another is that the new system does not handle a necessary exception, requires duplicate entry or cannot be accessed at the point of work. The first calls for different support from the second. A third possibility is that the proposed standard is inconsistent with a service requirement that has not been resolved.

Leaders should therefore ask what the current workaround enables before demanding that it stop. Workarounds can conceal risk and inconsistency, but they can also reveal a missing feature or unresolved operating decision. The task is to test the explanation, not romanticize the workaround or assume that compliance proves the new design is sound.

If the change is used consistently but outcomes do not improve, a stronger adoption campaign may increase the cost of the wrong solution. Implementation support needs a route for challenging assumptions, changing the design or stopping an element of the initiative. That requires a sponsor with authority to decide, not only a team responsible for communicating.

What organizational-readiness research contributes

Weiner’s 2009 theory distinguishes shared commitment to implementing a specific change from confidence in the collective ability to do so. It also explains that readiness can differ between changes within the same organization. This is a conceptual theory: it provides a disciplined distinction to investigate, not a validated guarantee of success or a universal readiness score. Read A theory of organizational readiness for change.

The updated Consolidated Framework for Implementation Research, published in 2022, organizes potential implementation influences across the innovation, outer and inner settings, individuals and implementation process. It gives greater attention to the people receiving and delivering an innovation. Developed from literature and user feedback, it helps structure inquiry; it does not establish which factor caused a particular stalled project. Read the updated CFIR publication.

Arcus’s practical synthesis is to examine the specific change, the work environment and the evidence of use together. A generic staff-engagement score may miss whether a particular team has the authority, resources and coordination needed for a particular operating change.

Four explanations that imply different management action

Several explanations may be true at once. Triangulate interviews with work observations, usage records, issue logs and operational information. Disagreement between these sources is useful evidence to explore, rather than a reason to discard the inconvenient source.

Choose the intervention that matches the barrier

An enterprise program can coordinate dependencies, but line leaders must own the continuing work. Conversely, leaving every department to solve a shared systems constraint separately can multiply effort. The governance design should put each decision where the authority and evidence needed to resolve it exist.

A practical adoption chain

This Arcus discussion framework makes the logic of an implementation explicit. It is a management tool rather than a proprietary empirical model.

Measure effective use before claiming benefits

A communications calendar, training-completion rate and number of champions show activity. They do not establish whether the new practice is used correctly, consistently and in the situations that matter. Define the eligible users or transactions, the expected behaviour and what constitutes an exception before interpreting an adoption percentage.

For the illustrative intake system, leadership might review use for eligible requests, missing information, duplicate work and time to resolution, alongside effects on staff workload and service access. A rising usage count can reflect rising demand rather than improving adoption. A shorter local processing time can coincide with a longer downstream queue.

Use measures to decide whether to continue, adapt or stop part of the rollout. Record other changes in demand, staffing or policy that could explain the result. Even strong adoption does not establish that the original solution is beneficial; the operational case must remain open to evidence.

An engagement that connects diagnosis with delivery

What your organization can receive

The proposal identifies the expertise, project roles and client responsibilities required. Explore the central Arcus consultant directory.

The final scope may focus on diagnosis, planning or implementation support. Arcus’s existing published change case accounts describe historical work on culture, transition, learning and knowledge transfer; they do not establish a universal success rate.

Build on strengths without overlooking constraints

Appreciative inquiry can give teams a constructive way to identify successful practices worth retaining. It should sit alongside scrutiny of workload, incentives, authority and the design itself. A strengths discussion does not replace the need to investigate a serious operational problem.

Appreciative Inquiry and Change Management · Change Management Framework · Organizational Review & Design

When an independent review is worth considering

Independent support can be valuable when leaders receive conflicting explanations, departments cannot resolve a shared barrier, or the organization needs to reassess an important commitment before expanding it. A small, clearly understood issue may be better handled by the internal team with the authority to fix it.

Tell Arcus what has been approved, what people are expected to do differently and where the work is getting stuck. We can discuss an appropriate assessment or implementation-support scope, the evidence required and the decisions it should help you make.