Change management
Change management is the structured process of planning, evaluating, coordinating, implementing, and reviewing changes to organizations, systems, processes, or practices.
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
- Frames safe evolution of production digital twins whose updates can affect both virtual behavior and physical operations.
- How deep it goes
- Outlines four change dimensions and practical safeguards, but does not specify a detailed change-control workflow.
- Examples
- Contrasts adding power_kw with renaming temperature to temp_c, and names shadow deployments, canary releases, and A/B testing.
- What you can do after
- Operate/configure it by favoring additive schemas, decoupled components, progressive rollouts, and approval before high-risk physical actions.
Read how Digital Twins in Action explains change management →
Related concepts
- change requesthas part · A change request is a proposal for modifying a system, service, process, or design, submitted for review and discussion.
- policykind of · A policy is a rule, strategy, or mapping that governs or determines decisions, actions, permissions, or behavior under specified conditions.
- driftaddresses · Drift is a change over time in a system’s behavior, state, data, or configuration relative to a reference or expected baseline.
- 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.
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.