Work [extra Quality] — Algorithmic Sabotage

Long before data poisoning or phone trees, a landmark case established the legal contours of computer sabotage. In 1996, Timothy Lloyd, a system administrator at Omega Engineering, planted a in the company's central file server before being fired. After his departure, the bomb detonated, permanently deleting approximately 1,200 programs critical to Omega's manufacturing capabilities. The company lost millions of dollars in sales and contracts.

Algorithms should serve as advisors to human managers, not autonomous judges. Final decisions regarding discipline or scheduling must involve human empathy and context.

Gig workers, who lack traditional unions, use forums like Reddit and WhatsApp to organize decentralized disruptions.

: Gig workers often run multiple delivery apps simultaneously to cherry-pick the best-paying jobs, intentionally delaying certain orders to force the algorithm to increase surge pricing. Data Pollution

For last-mile delivery workers paid per hour (not per delivery), speed is the enemy. Savvy workers will park their scooter around the corner from a restaurant, mark "arrived," then walk slowly to the counter. On the delivery side, they will wait at the curb for 90 seconds before walking to the apartment door. algorithmic sabotage work

[Invasive AI Surveillance] ➔ [Loss of Autonomy & Dignity] ➔ [Algorithmic Sabotage] ➔ [Regained Agency] The Illusion of Objectivity

Resistance looks different depending on the industry, but the goal is always the same: reclaiming the human element. The "Slow-Down" via Data:

The New Luddites: A Guide to Algorithmic Sabotage at Work In an era where workplace productivity is increasingly dictated by "black box" algorithms—from AI-driven performance tracking to automated scheduling—a new form of resistance is emerging. isn't about smashing machines; it’s about reclaiming agency in a digital-first workplace. What is Algorithmic Sabotage?

(e.g., gig-economy couriers and warehouse pickers). Long before data poisoning or phone trees, a

Algorithmic sabotage is rarely about destroying hardware; it is about "gaming" the software. Examples are found across various industries: The "Multi-Apping" Maneuver

As long as businesses use algorithms to treat humans like machines, humans will use their ingenuity to break the machine.

They created thousands of "perfect" virtual personas that exclusively shopped at local mom-and-pop stores. The algorithm, seeing this massive (simulated) trend, shifted its predictive modeling to favor small businesses over big-box retailers to keep its "satisfaction scores" high.

In warehouse settings, workers may intentionally take longer on specific tasks to prevent the algorithm from "optimizing" the pace to an impossible speed for the next shift. Coordinate "Log-Offs": The company lost millions of dollars in sales and contracts

If a system tracks "time on task," a worker might find ways to keep a screen active while doing other things.

A key structural reality of this new form of work is that workers are generally classified as independent contractors rather than employees. This shifts the burden of assets, investment, and risk onto the workers themselves, while standard labor and social protections remain largely inaccessible. It is precisely this vulnerability that has driven workers to develop new, creative forms of resistance.

The next time your food delivery arrives 20 minutes late, do not blame the driver. Ask yourself: Was that a failure of the algorithm... or was that a victory of the worker?

Unlike traditional sabotage, which aims to break physical tools, algorithmic sabotage aims to subvert the logic