If management finds a way to automate jobs during a strike, is that scabbing?
Peripherally.
The automation itself is more part of the general category of management strategies to restructure workflow and production methods in order to reduce the need for, and thus the power of, labor. This dates back to the origins of Taylorism itself in the 1890s as an effort to “steal the brains from underneath the cap of labor” and through to the emergence of Human Relations and Industrial Psychology in the early 20th century as a means to better control workers. So I think you could see in as essentially equivalent to classic speed-up and stretch-out efforts to maintain production at as low a cost as possible during a strike, and thus break the union.
However, the dirty truth of automation is that there is no clean way to fully substitute machinery for labor. Due to the inherent limitations of technology at any stage of development, you need labor to repair and maintain and monitor automated systems, you need labor to install and operate the machines, you need labor to design and program and manufacture the machines. (This is one reason why the job-killing predictions around automation often fall flat, because the supposedly superior new technology often requires a significant increase in human labor to service the new technology when it breaks. For example, this is why automation in fast food has proven to be so difficult and partial than expected: it turns out that self-checkout machines are actually very expensive to operate in terms of skilled manpower.) And to the extent that a given automation contract or project is being undertaken during a strike in order to break that strike, that’s absolutely scabbing.












