liveBook · Manning

Organizational change

As explained in Think Like a Software Engineering Manager

Organizational transformation is a substantial change to an organization’s structure, operations, capabilities, or direction.

A software company upgrading legacy systems for performance and security illustrates organizational change: a substantial shift in structure, operations, capabilities, or direction. Change may be incremental, such as moving gradually from on-premises servers to cloud computing, or transformational, such as a single major workforce reduction. section 13.0 section 13.2.1

Manage change by combining business reasoning with practical support:

  • Understand why the change is needed, what employees and the organization must invest, which benefits are expected, and whether the outcome can be reversed. section 13.2.1
  • Build a framework around champions, a strategy, iterative execution, success monitoring, and further improvement. section 13.2 section 13.5
  • Communicate transparently, maintain morale, provide training, encourage collaboration, identify risks, and advocate for affected team members. section 13.0 section 13.5
  • Use Lewin’s model to unfreeze resistance, guide the transition with reassurance, and refreeze the accepted changes as normal practice. section 13.2.1

Netflix’s move to cloud and DevOps

Netflix combined automation, resilient systems, and an iterative rollout. It moved to the cloud before adding tools such as Chaos Monkey and the Netflix Simian Army, using continuous improvement to strengthen delivery and reliability. section 13.2.7

Leadership changes, reductions, mergers, and reorganizations can disrupt careers and morale. Treating people empathetically while connecting upper management and staff helps reduce the human cost and supports collective progress. section 13.0 section 13.5

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains incremental and transformational change, then gives a framework, Lewin’s phases, risks, communication practices, and iterative monitoring.
Examples
Uses cloud migration, legacy-system upgrades, layoffs, Netflix’s DevOps adoption, and questions about leadership and workforce transitions.
What you can do after
Apply a change-management framework to plan, communicate, execute, monitor, and improve organizational transitions.
How it connects
Links organizational change to change management, leadership transitions, workforce change, organizational transformation, and DevOps.

Also explained in

Compare how 2 books explain organizational change →

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.