Change Mgmt key terms

An alteration to a product, service, process, system, or organisation, made deliberately to achieve an outcome. It may be small and routine or large and strategic, and it can be planned in advance or emerge gradually.

The coordinated set of practices used to prepare for, approve, implement, and review changes so that benefits are realised while disruption and risk are controlled. It spans individual change control and the human side of organisational transition.

The administrative process of recording, assessing, approving, scheduling, and reviewing proposed changes. Its purpose is to ensure that only authorised changes proceed and that the impact on services and stakeholders is understood before work begins.

A modern name for the practice that maximises the number of successful changes by managing risk and authorising change. It emphasises appropriate authorisation for each change type rather than a single heavyweight approval route.

A formal proposal to alter a configuration item, service, or process. It captures what is to change, why, the expected benefit, the proposed timing, and an initial view of risk so that assessors can decide whether to authorise it.

The stored details of a change throughout its lifecycle, including the original request, assessments, approvals, implementation notes, test evidence, and closure outcome. It provides the audit trail and the history needed for later review.

A group that reviews proposed changes and advises on their risk, priority, and scheduling. It typically includes technical, service, and business representatives, and it recommends rather than owns the change, depending on governance arrangements.

The person or role empowered to approve or reject a particular change, within limits set by governance. Authority should match the risk and cost of the change, so low-risk changes can be approved close to where the work happens.

A low-risk, repeatable change that follows a pre-approved procedure, so it needs no individual authorisation each time it is used. The procedure itself is reviewed periodically to confirm it remains safe and appropriate.

A change that must be assessed and authorised through the usual change process before implementation, because its risk or impact is not covered by a pre-approved procedure. It is scheduled to balance risk, urgency, and business constraints.

A change that must be implemented urgently, often to restore or protect a service, and so uses an expedited assessment and approval route. Retrospective review after implementation keeps control without delaying the fix.

A defined period during which non-essential changes are not permitted, often around peak trading, financial close, or major events. Exceptions are limited to urgent corrective work and require explicit authorisation from the change authority.

A schedule showing planned changes, freezes, and known busy periods so that changes can be sequenced and clashes avoided. It helps teams see dependencies and agree timing across services and suppliers.

The agreed timetable for implementing one or more changes, including dates, dependencies, resources, and communication points. It translates approved change records into a practical sequence of work.

Any component that needs to be managed to deliver a service, such as hardware, software, documentation, or a person's role. Recording these items and their relationships lets teams assess which changes will affect what.

The set of tools and data used to hold details of configuration items and the relationships between them. It supports impact assessment by showing what depends on what before a change is approved.

The analysis of what a proposed change will affect, including services, users, systems, processes, costs, and risks. Its findings inform the decision to approve, defer, or reject the change and shape the implementation plan.

The structured evaluation of the likelihood and consequences of a change failing or causing harm, weighed against the benefit expected. It produces a risk rating that determines the level of scrutiny and approval required.

A documented method for reversing a change if it fails or causes unacceptable harm, including the steps, data, and decisions needed. Testing the rollback before implementation makes recovery faster and more reliable.

The practical instructions for restoring the previous state after an unsuccessful change, such as reinstating files, configurations, or hardware. It differs from a rollback plan mainly in naming convention and should be verified in advance.

The technical act of putting a changed component into a live or target environment. It is distinct from release, which concerns making functionality available to users, though the two are often coordinated closely.

One or more changes, often grouped, made available to users together. Grouping changes into a release can reduce disruption and simplify testing, but it also increases the scope of any failure.

A check after a change has gone live to confirm it achieved the intended outcome, caused no unexpected harm, and was delivered as planned. Lessons are recorded and fed back to improve future changes.

Permission given to a role or team to approve changes within stated limits, such as cost, risk, or scope. It speeds up decisions while keeping accountability clear through documented thresholds and reporting.

The structures, roles, and rules that determine who decides what, how decisions are made, and how performance is monitored. In change work it sets approval thresholds, reporting lines, and accountability for outcomes.

The discipline of helping people and groups move from a current state to a desired future state, addressing behaviour, capability, and culture as well as process and technology. It focuses on adoption and sustained benefit rather than on technical delivery alone.

A model describing typical emotional responses to change, such as shock, resistance, exploration, and acceptance. It helps change leaders anticipate dips in performance and time support to where people are in the transition.

Behaviour that slows or blocks a change, ranging from open objection to quiet non-compliance. It often signals legitimate concerns about loss, competence, or fairness, and is best addressed by listening rather than by force.

The planned process of identifying people affected by or able to influence a change and communicating with them in ways that build understanding and support. It is continuous, two-way, and tailored to each group's interests and influence.

A method of mapping individuals and groups by their interest in and influence over a change, so that engagement effort is proportionate. It usually records concerns, preferred channels, and the level of involvement needed.

The senior person who authorises a change, provides resources, and publicly supports it. An effective sponsor has enough authority to remove barriers and is visibly involved, because their behaviour signals how seriously others should take the change.

A person who actively promotes and facilitates a change within their sphere of influence, often without formal authority over it. They translate the case for change into local action and feed concerns back to the programme.

A group of informed volunteers or appointed staff who support a change in their teams, answering questions and modelling new behaviour. The network extends reach beyond the core team and surfaces local issues early.

The extent to which an organisation and its people are prepared to adopt a change, covering awareness, capability, resources, and willingness. Readiness is assessed before go-live so that gaps can be closed rather than discovered afterwards.

A structured check of whether the people, processes, and systems needed for a change are in place before it goes live. It typically examines awareness, training completion, support arrangements, and contingency planning.

The point at which people consistently use a new process, tool, or behaviour in their normal work. Adoption is measured by actual usage and outcomes, not by attendance at briefings or completion of launch activities.

The process of confirming that the intended gains from a change are actually achieved and sustained. It requires defined measures, agreed baselines, and review after implementation, rather than assuming benefits follow automatically from delivery.

A schedule of what will be communicated to whom, by which channel, and when, across the life of a change. Good plans include two-way feedback routes and are adjusted as stakeholder concerns emerge.

The process of identifying which people need which knowledge and skills to work effectively after a change. Its output shapes the design, timing, and delivery of learning so that capability arrives before go-live.

The period during which people move from old ways of working to new ones, often experiencing mixed practice and reduced confidence. Managing transition means providing support, clarity, and quick fixes while the new state settles.

The work of embedding a change so that new behaviour persists after the project team disbands. It relies on aligned incentives, updated processes and documentation, and continued reinforcement by line managers.

The degree to which people feel involved in and committed to a change, rather than merely informed or compliant. High engagement is associated with discretionary effort and lower turnover during transitions.