The CM Toolkit

The effect of a change on a group's daily work, responsibilities, skills, or relationships. Always assessed at the group level, not the individual level. Impacts have four dimensions: process, technology, behaviour, and role/structure.

The degree to which an organisation and its people are prepared - in terms of awareness, capability, willingness, and system readiness - to successfully adopt and sustain a change. Readiness is not the same as being on schedule. A programme can be on time and not ready.

The actual use of the change in day-to-day work. Adoption is not completion of training. It is the sustained behavioural change that produces the intended outcome. True adoption is measured 30, 60, and 90 days post go-live - not on go-live day.

The process of ensuring that adopted changes persist over time and do not revert. Sustainment requires embedded accountability, updated performance expectations, retired legacy processes, and a named owner after the project team dissolves.

Observable behaviour (or lack of behaviour) that slows or prevents adoption. Resistance is not a character flaw. It is information - about fear, lack of understanding, legitimate disagreement, or structural barriers. It must be diagnosed before it can be addressed.

Active, visible leadership behaviour that signals the change is real, important, and here to stay. Sponsorship is not approval on a project charter. It is showing up in team meetings, cascading messages personally, and removing obstacles when they arise. The most common failure point in transformation programmes.

A peer-level advocate for the change within an affected team or group. Not the change manager. Not a manager. A trusted peer who can model the new behaviour, answer informal questions, and surface concerns upward. Most effective when self-selected, not appointed.

What's In It For Me. The personal benefit case for the change, stated in the language and context of the specific audience. A change that cannot answer WIIFM for frontline staff will produce passive resistance regardless of how well it is communicated at the organisational level.

A defined post go-live period - typically 2 to 6 weeks - during which elevated technical and operational support is available. Hypercare provides the safety net that makes adoption feel lower-risk for end users. It must have a defined end date with clear exit criteria.

A formal decision point at which a programme determines whether it is ready to proceed to the next phase or milestone. Go/no-go decisions require evidence, not just confidence. A change manager's role is to advise on readiness, not to approve the go decision - that sits with the business sponsor.

Awareness, Desire, Knowledge, Ability, Reinforcement. An individual change model. Useful for diagnosing where a specific person or group is stuck. The Adoption Tracker in this toolkit maps directly to the ADKAR sequence.

Create urgency, form a coalition, develop a vision, communicate the vision, empower action, generate short-term wins, sustain acceleration, anchor the change. An organisational change model. Most useful for culture change and long-horizon transformations.

A model describing the emotional journey through change: Late Status Quo → Resistance → Chaos → Integration → New Status Quo. Useful for understanding why performance often dips immediately post go-live before improving. Helps set realistic expectations with leadership.

Unfreeze (create motivation to change), Change (introduce the new), Refreeze (embed and sustain). The Sustainment Checklist in this toolkit addresses the Refreeze stage - the most commonly under-resourced part of any transformation.

In a government service context: the confidence that residents and staff have in digital systems to be secure, reliable, accurate, and to protect their data. A Digital Trust initiative typically involves modernising identity verification, data governance, or resident-facing service platforms.

The maintenance of resident-facing services without interruption during the transition to new systems or processes. In government transformation, service continuity is a non-negotiable constraint - unlike corporate settings where a temporary dip may be acceptable.

A testing phase in which end users validate that a system works as required before go-live. UAT sign-off from the business is a prerequisite for a Go decision. Change managers should be present during UAT to capture behaviour observations, not just defect logs.

A planned point in the project lifecycle where a defined set of features, processes, or capabilities are made available to users. Each release milestone requires its own readiness gate assessment. Do not apply a single readiness view to a phased release programme.

The stage an organisation has reached in genuinely embedding AI into its operating model, distinct from the stage of technology deployment. An organisation can have AI tools live and still be at an early adoption maturity stage if behaviours, governance, and culture have not shifted. Maturity is measured by how the organisation leads, not just what it has installed.

The deliberate design of decision points where a human takes over from, or passes work to, an AI agent. Poor handoff design is one of the leading causes of AI adoption failure. Change managers should map handoff moments during impact assessment and ensure affected staff understand their role at each point.

A specific form of structural resistance that emerges when automation removes steps that gave a person or team a sense of control, visibility, or status. Unlike fear-based resistance, this type often comes from experienced, high-performing staff who lose informal influence when a process is automated. Address through role redesign conversations, not reassurance messaging.

The degree to which an organisation's people, culture, data practices, and governance structures are prepared to adopt and sustain AI-enabled ways of working. Distinct from digital readiness. An organisation can be digitally mature and still have low AI readiness if its leadership posture, trust environment, or change capacity is insufficient.

The change manager's mandate in an AI deployment is not to explain the technology. It is to design the human adoption architecture: sequencing the rollout by trust and readiness levels, mapping resistance patterns specific to automation anxiety, equipping sponsors to lead through uncertainty, and building the sustainment model before go-live. The agent automates the task. The change manager ensures the organisation actually changes.

The process of embedding AI agent-driven workflows into an organisation's operating rhythm such that staff understand, trust, and consistently use them. Agentic adoption fails most often not at the technology layer but at the trust and habit layer. Measurement should focus on human behaviour change, not agent uptime.