liveBook · Manning

Change management

As explained in 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.

Change management is the deliberate guidance of organizational or project changes so people, resources, timelines, and deliverables remain aligned. Changes may be incremental, such as moving from on-premises servers to cloud computing, or transformational, such as a single workforce reduction. Engineering managers connect leadership and staff, protect morale, provide support, and reduce the human cost of transition. section 13.0

A practical change-management process includes:

  • Understand why the change is needed and define a shared direction. section 13.5
  • Recruit champions, communicate clearly, identify risks, and provide relevant training. section 13.5
  • Execute iteratively, monitor results, and revise the approach as opportunities or problems emerge. section 13.5
  • For shifting project priorities, estimate the new effort, assess effects on bandwidth and timelines, reallocate resources, and negotiate what to defer. section 10.1.4

A feature requirement changes

After user feedback significantly changes Project Accessible’s feature requirements, the team evaluates effects on timelines, resources, and deliverables. Engineers and the technical project manager estimate the added work; the manager reallocates resources and negotiates which lower-priority work can be postponed. Transparent communication and collaborative decisions preserve momentum while limiting disruption. section 10.1.4

Leadership transitions, reorganizations, layoffs, and mergers require professional handling as well as operational planning. Managers should lead by example, maintain a growth mindset, advocate for team members, and use empathy when career growth or employment is disrupted. section 13.0 section 13.5

How Think Like a Software Engineering Manager covers it

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.
How it connects
Links change management with communication, collaboration, shared vision, leadership transitions, workforce changes, training, and project execution.

Also explained in

Compare how 4 books explain change management →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.