Change management
Change management is the structured process of planning, guiding, coordinating, and controlling changes to organizations, systems, or processes.
Fundamentals of Cybersecurity
A change management policy is an organizational directive that governs how modifications to systems, applications, processes, and infrastructure are requested, evaluated, approved, tested, implemented, and reviewed.
- How it is used
- Governs modifications so evolving systems remain secure and stable rather than drifting from approved configurations.
- How deep it goes
- Lays out six lifecycle steps, their checks and rollback planning, plus an emergency path; stops short of tool-specific implementation instructions.
- Examples
- Uses a Sunday maintenance window, rollback after a failed change, and an urgent patch for an actively exploited vulnerability.
- What you can do after
- Practice/perform it: request, assess, approve, test, implement, and review a change while preparing to restore the previous state.
Read how Fundamentals of Cybersecurity explains change management →
Think Like a Software Engineering Manager
Organizational change management is the deliberate planning and guidance of changes to an organization's structure, workforce, practices, or operations.
- How it is used
- Guides engineering managers through reorganizations, workforce transitions, leadership changes, and shifting project priorities.
- How deep it goes
- Explains change types, manager responsibilities, and an iterative framework, then applies it to effort, resource, timeline, and deliverable decisions.
- Examples
- Uses cloud migration, layoffs, reorganizations, mergers, and a user-driven feature change to illustrate organizational and project transitions.
- What you can do after
- Apply an iterative change process that evaluates impact, reallocates resources, communicates transparently, and supports affected people.
Read how Think Like a Software Engineering Manager explains change management →
First-Party Data Activation
The structured practice of preparing, supporting, and guiding people and organizations through changes in processes, technology, or ways of working.
- How it is used
- Guides organizational adoption of first-party data strategies and generative marketing.
- How deep it goes
- Outlines three adoption phases and organizational shifts, without detailing a complete change-management procedure.
- Examples
- Uses self-serve audience access, standardized cross-channel testing, predictive churn models, and changing marketer roles as examples.
- What you can do after
- Apply it by sequencing adoption from self-serve data access through measurement to predictive and multichannel methods.
Read how First-Party Data Activation explains change management →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
A governance process of steps and reviews for implementing production changes while controlling their risk.
- How it is used
- Governs production infrastructure changes through requests, reviews, quality gates, scheduling, and verification.
- How deep it goes
- Defines the workflow and risk controls, but stops short of automating every review or preventing every failure.
- Examples
- Uses server changes, ticketed requests, conflicting updates, change windows, and an incompatible binary rollout.
- What you can do after
- Operate/configure production changes with documented rollout and rollback plans, coordinated approvals, and explicit risk mitigation.
Digital Twins in Action
Change control is the governed process for evaluating, approving, implementing, and tracking changes to a system or its operating configuration.
- How it is used
- Supports safe evolution of production digital twins whose changes can affect physical operations.
- How deep it goes
- Identifies change dimensions and safeguards, but does not detail a complete approval or tracking workflow.
- Examples
- Uses adding power_kw and renaming temperature to temp_c to illustrate schema compatibility.
- What you can do after
- Apply it by identifying change dimensions, favoring additive schemas, and selecting rollout and approval safeguards.
Read how Digital Twins in Action explains change management →
Also covered in
What to know first
- authorizationAuthorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.
- complianceCompliance is conformity with applicable legal, regulatory, contractual, policy, or other governing requirements.
- resilienceResilience is the ability of a system to continue providing acceptable functionality or recover when failures or other disruptions occur.
- language modelA language model is a computational model that represents patterns in linguistic sequences to assign probabilities, predict, generate, or evaluate language.
Related concepts
- change requesthas part · A change request is a proposal to modify an existing system, requirement, service, process, or design, typically submitted for review or approval.
- driftaddresses · Drift is a change or divergence over time in a system’s data, state, behavior, or performance relative to a reference or intended condition.
- peer reviewuses · Peer review is the assessment of work by knowledgeable colleagues or independent experts to evaluate its quality, correctness, validity, or reasoning and provide feedback.
- policykind of · A policy is a rule, principle, or decision function that governs behavior or determines actions or permissions under specified conditions.
Questions about change management
What is change management?
Change management is the structured process of planning, guiding, coordinating, and controlling changes to organizations, systems, or processes.
Which Manning books explain change management?
Fundamentals of Cybersecurity, Think Like a Software Engineering Manager, First-Party Data Activation, Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform and Digital Twins in Action.
What should I know before learning change management?
Manning books that teach change management usually introduce authorization, compliance, resilience and language model first.
What is change management a kind of?
Change management is a kind of policy. A policy is a rule, principle, or decision function that governs behavior or determines actions or permissions under specified conditions.
What are the parts of change management?
Change management includes change request and impact analysis.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.




