Change Implementation Planning
Expert-defined terms from the Professional Certificate in Engineering Change Management course at London School of Business and Administration. Free to read, free to share, paired with a globally recognised certification pathway.
Acceptance Criteria #
The specific conditions that a product or service must satisfy to be accepted by the customer or end-user. In change implementation planning, acceptance criteria are defined for each change to ensure that it meets the desired outcomes and quality standards.
Agile #
A project management and product development approach that emphasizes flexibility, collaboration, and customer satisfaction. Agile methodologies, such as Scrum and Kanban, involve iterative development, continuous improvement, and rapid response to changing requirements.
Change Impact Analysis #
A process of evaluating the potential effects of a proposed change on people, processes, and technology. Change impact analysis helps organizations anticipate and mitigate risks, optimize resources, and ensure smooth transitions.
Change Management #
The systematic approach to managing and controlling changes to an organization's processes, products, or services. Change management involves planning, implementing, and monitoring changes to minimize disruption, ensure compliance, and maximize benefits.
Change Request #
A formal document that outlines a proposed change to a product, process, or service. Change requests typically include a description of the change, its rationale, potential impacts, and required resources.
Change Advisory Board (CAB) #
A group of stakeholders responsible for reviewing, approving, and prioritizing change requests. The CAB ensures that changes align with organizational strategies, policies, and standards, and minimizes risks and disruptions.
Change Implementation Plan #
A detailed roadmap that outlines the steps, resources, and timelines for implementing a change. Change implementation plans typically include risk assessments, communication strategies, training programs, and performance metrics.
Change Log #
A record of all changes made to a product, process, or service. Change logs provide transparency, accountability, and traceability, and help organizations maintain consistency and compliance.
Communication Plan #
A strategy for informing and engaging stakeholders about a change. Communication plans typically include messaging, channels, timing, and feedback mechanisms to ensure effective and timely communication.
Continuous Improvement #
A philosophy of constantly seeking and implementing improvements to products, processes, and services. Continuous improvement involves iterative cycles of planning, execution, evaluation, and learning.
Cost #
Benefit Analysis: A method for evaluating the financial implications of a change. Cost-benefit analysis compares the costs of implementing a change to the expected benefits, such as increased revenue, reduced costs, or improved efficiency.
Critical Success Factors #
The key areas or elements that must be present or achieved for a change to be successful. Critical success factors are often used to define performance metrics and track progress.
Culture Change #
A transformation of an organization's values, beliefs, and behaviors to support a desired outcome or direction. Culture change typically involves shifts in attitudes, practices, and structures, and requires leadership, communication, and engagement.
Deployment Plan #
A detailed plan for installing, configuring, and testing a change in a production environment. Deployment plans typically include rollback strategies, contingency plans, and performance monitoring.
DMAIC #
A problem-solving framework used in change implementation planning. DMAIC stands for Define, Measure, Analyze, Improve, and Control, and provides a structured approach to identifying, quantifying, and resolving issues.
Eight Disciplines (8D) #
A problem-solving methodology used in change implementation planning. 8D involves eight sequential steps for identifying, resolving, and preventing issues: Team Formation, Problem Definition, Root Cause Analysis, Containment Action, Corrective Action, Implement and Validate, Prevent Recurrence, and Congratulate the Team.
Fail #
Safe: A design principle that ensures that a system will fail in a safe and controlled manner, minimizing harm or damage. Fail-safe mechanisms are often used in change implementation planning to mitigate risks and prevent catastrophic failures.
Force Field Analysis #
A tool for analyzing the driving and restraining forces that influence a change. Force field analysis helps organizations identify and address barriers to change, and balance competing interests and priorities.
Gantt Chart #
A visual representation of a project schedule, showing tasks, dependencies, and timelines. Gantt charts are often used in change implementation planning to track progress, allocate resources, and manage deadlines.
Go #
Live: The point in time when a change is deployed and becomes operational. Go-live events typically involve carefully planned and coordinated activities to ensure a smooth and successful transition.
Impact Analysis #
See Change Impact Analysis.
Kaizen #
A Japanese term meaning "continuous improvement." Kaizen involves incremental and continuous improvements to processes, products, and services, often involving cross-functional teams and collaborative problem-solving.
Kanban #
A visual project management method that uses boards and cards to represent tasks, workflows, and progress. Kanban involves limiting work-in-progress and focusing on flow and throughput, promoting flexibility and responsiveness.
Key Performance Indicator (KPI) #
A measurable metric that reflects the critical success factors and desired outcomes of a change. KPIs are often used in change implementation planning to track progress, evaluate effectiveness, and make data-driven decisions.
Lessons Learned #
The insights, experiences, and knowledge gained from a change implementation. Lessons learned are often documented and shared to improve future change initiatives and avoid repeating mistakes.
Levers of Change #
The strategic interventions or actions that can influence or accelerate a change. Levers of change may include structural, cultural, technological, or behavioral interventions, and are often used in change implementation planning to drive desired outcomes.
Metric #
A standard of measurement used to quantify and evaluate a change. Metrics may include financial, operational, or performance metrics, and are often used in change implementation planning to track progress, evaluate effectiveness, and make data-driven decisions.
Mock #
Up: A prototype or simulation of a product, process, or service, used to test and validate a change. Mock-ups are often used in change implementation planning to identify and address issues, refine designs, and build stakeholder confidence.
PDCA #
A problem-solving and continuous improvement framework used in change implementation planning. PDCA stands for Plan, Do, Check, and Act, and provides a structured approach to planning, executing, evaluating, and learning from changes.
Pilot Test #
A small-scale implementation of a change, used to test and validate its feasibility, effectiveness, and impact. Pilot tests are often used in change implementation planning to identify and address issues, refine designs, and build stakeholder confidence.
Plan #
Do-Check-Act (PDCA): See PDCA.
Post #
Implementation Review: A structured evaluation of a change after it has been implemented, to assess its outcomes, impacts, and lessons learned. Post-implementation reviews are often used in change implementation planning to improve future change initiatives and promote continuous improvement.
Process Map #
A visual representation of a process, showing its steps, inputs, outputs, and stakeholders. Process maps are often used in change implementation planning to identify opportunities for improvement, streamline workflows, and clarify roles and responsibilities.
Project Charter #
A document that defines the scope, objectives, and approach of a change implementation project. Project charters are often used in change implementation planning to align stakeholders, allocate resources, and establish governance structures.
Prototype #
See Mock-Up.
Regression Testing #
A testing methodology that validates whether a change has introduced new defects or issues. Regression testing is often used in change implementation planning to ensure that changes do not negatively impact existing functionality or performance.
Risk Assessment #
A process of identifying, evaluating, and prioritizing the risks associated with a change. Risk assessments are often used in change implementation planning to mitigate potential issues, allocate resources, and ensure compliance.
Risk Management #
The systematic approach to identifying, assessing, and controlling risks associated with a change. Risk management involves planning, implementing, and monitoring risk mitigation strategies to minimize disruption, ensure compliance, and maximize benefits.
Rollback Plan #
A plan for reverting to a previous state or version of a product, process, or service, in case of issues or failures. Rollback plans are often used in change implementation planning to minimize downtime, reduce