liveBook · Manning

Reduction in force

As explained in Think Like a Software Engineering Manager

A workforce reduction is a decrease in the number of employees retained by an organization.

A reduction in force (RIF) decreases the number of employees retained by eliminating positions without intending to hire replacements. It differs from ordinary hiring pauses because existing roles are removed. section 13.3.2

Organizations may reduce their workforce after unfavorable market conditions, overhiring, declining demand, automation, or internal team mergers. Managing the change requires planning, communication, and empathy. section 13.3 section 13.3.2

An engineering manager may need to:

  • Coordinate with human resources when identifying or communicating affected employees. section 13.3.2
  • Deliver difficult news when the organization entrusts that responsibility to managers. section 13.3.2
  • Recognize that layoffs can be emotional for managers and team members. section 13.3.2

Technology-sector adjustment

After pandemic-era demand declined, some technology companies reduced staff following overhiring. Separately, AI tools automated tasks and changed demand for software, machine-learning, and data-science expertise. section 13.3.2

How Think Like a Software Engineering Manager covers it

How deep it goes
Defines eliminated positions and outlines causes and manager responsibilities, but stops short of a complete layoff procedure.
Examples
Uses pandemic-era technology overhiring, post-pandemic demand decline, AI automation, team mergers, and a major technology-company layoff as examples.
What it assumes
Assumes an engineering-manager perspective and awareness of human resources, organizational teams, and workplace roles.
What you can do after
Practice/perform manager responsibilities by coordinating with human resources and communicating difficult workforce-reduction news empathetically.
How it connects
Connects workforce reduction with organizational change management, mergers and acquisitions, layoffs, remote work, automation, and human resources.

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.