> I wouldn’t be so dismissive: “force multiplier” means job loss unless there’s a large amount of work which isn’t currently being done.

I think there is a massive amount of work that's currently not being done, industry-wide. Everywhere I've worked has had something like 4-10X more work to do than staff to do it. The feature and bug backlogs just endlessly grow because there is no capacity to keep up. Companies should be able to adopt a force multiplier without losing staff: It could bring that factor down to 2-5X. The fact that layoffs are happening industry-wide shows that leadership might not even know what their workers could be doing.

In software, there is a lot of postponed work. I was thinking of other things like how companies want to replace customer service, claims processing, etc. where efficiency improvements pretty directly translate into job losses unless their business suddenly grows significantly.