Engineering restructuring
The team is 40 people doing the work of 15.
You know a cut is coming. The question is whether it is run as a headcount spreadsheet by finance, or as an engineering decision by someone who can read the delivery data and the people.
How the cut is decided
Six months of pull requests, incidents, and releases, read next to what the roadmap actually needs. The result is not a percentage. It is a target shape: which teams exist afterwards, who leads them, and who ships. Right-sizing an engineering team lays out the method; is your IT team too big covers the signals that you're over-hired.
How the exits run
Under the law of the country, planned before anything is announced. In Belgium that can mean the Renault procedure; in the Netherlands the WMCO and the UWV route. The people who stay watch how the people who leave are treated. That is where the org is kept or lost.
What it looks like done
45 engineers to 22: weekly releases again after 4 months, payroll halved, one regretted departure in the six months after. The diagnosis decides whether your version of this is 20 exits or 4.