The employee side of transformation
Vermont Information Processing’s notice of 66 job cuts gives its language of transformation a concrete consequence. Based in Colchester in the US state of Vermont, the company sells software to the beverage industry. Its response published on 21 October describes a review of its structure, a product-led transition and resources aligned with new priorities. For employees, the consequence is plain: the employer has decided to stop paying for some positions. Calling that decision a transformation leaves its authorship with management.[1]
The company’s AI narrative has concrete content: software functions for delivery routes, ordering and reporting. These are uses that can make a customer’s work easier. A changed process at the customer and an eliminated position at the software supplier are different jobs, however. Without identifying which task disappeared, treating the product’s use of AI as the explanation for layoffs transfers a management choice into a story of technological inevitability.[1]
The acquisition of Encompass Technologies a little over a month earlier matters here. Combining teams or reorganizing overlapping functions after an acquisition is a plausible explanation. AI could also have reduced tasks. The reporting supplies no task breakdown that would distinguish those possibilities. My objection does not depend on automation being useless. It concerns the company’s responsibility to explain its own decision, rather than letting innovation in a product become a ready-made rationale for reducing employment.[1]
The acquisition timeline also reminds us that ownership has changed. Vermont Information Processing was previously employee-owned before Warburg Pincus acquired it last year. Proceeds received by former employee-owners do not make the current cuts fall equally on everyone. We cannot assume that the person receiving sale proceeds is the person losing a job. Treating the former ownership structure as collective compensation for today’s employees would combine different people’s outcomes into one account.[1]
Where the work goes
Management may have defensible options here. Avoiding duplicate work after a merger or improving customer service are legitimate objectives. Management also chooses how employees share any benefit: reassignment, training, changes in hours or the terms of departure. I am not claiming these measures have been offered at this company. A product-led transition gains meaning for employees when those choices are explained. Convenience promised to a customer and the livelihood of a person whose position is cut cannot be treated as the same outcome.[1]
The answer I want from the company begins with where the work goes, before the size of its AI budget. Which eliminated tasks are no longer performed, and which move to the remaining team or another supplier? This is neither worker testimony nor a claim that workloads have already increased; it is the distinction I propose for accounting for the cuts. When management describes a product doing more, it should also explain who retains the labor of producing and maintaining that product.[1]
An employer able to give notice for 66 positions can explain the distribution of its transformation just as clearly. If automation produces a gain, it should be possible to describe it through tasks, time and working conditions. If merger considerations dominate, management should own that rationale. Presenting a management decision as an inevitable natural event constrains employees’ bargaining space. My demand is straightforward: the company should retain responsibility for its employment decision as readily as it claims credit for the product’s capabilities.[1]