Please Help ZNet
That’s precisely the problem facing microworkers around the globe. In his new book Work Without the Worker: Labour in the Age of Platform Capitalism, Phil Jones explains the uphill battle these workers face and how their precarious form of employment may be facilitating its own demise.
Jones joined Alex Press on a recent episode of Jacobin’s Primer, a podcast about all things Amazon. The following transcript has been edited for clarity and length.
Contractors are very often tech giants like Google, Facebook, Uber, Microsoft. These companies need workers to process data and train their artificial intelligence technology.
Tasks on a platform might include annotating images of different areas to direct autonomous drones, annotating images of faces to train facial recognition technology, or training chatbots to recognize different accents or emotions in people’s voices.
I suppose Silicon Valley hype tends to depict artificial intelligence as something entirely unprecedented. But the relationship between new technology and workers really isn’t so different from the relationship between earlier technologies and workers. In both cases, a machine does some of the tasks once done by a worker. But the worker is still required to watch over the machine and correct its functions. That’s similar to what the microworker does.
The majority of those who do this work are in the Global South. They could be refugees, prisoners, or people living in occupied territories. Conditions are pretty miserable on microwork sites, generally speaking. One study found that, on a few of the platforms, a majority of the tasks are paid at less than twenty cents a task. Another study, years back, found that the average wage on one platform was $2 an hour.
Because the tasks are so short and poorly paid, workers often have to work super fast to reach subsistence wages. In fact, what often happens is that workers spend more time hunting for tasks than actually doing paid work.
A woman living in Kenya’s Dadaab, which is among the world’s largest refugee camps, wanders across the vast, dusty site to a central hut lined with computers. Like many others who have been brutally displaced and then warehoused at the margins of our global system, her days are spent toiling away for a new capitalist vanguard thousands of miles away in Silicon Valley. A day’s work might include labelling videos, transcribing audio, or showing algorithms how to identify various photos of cats.
Amid a drought of real employment, “clickwork” represents one of few formal options for Dadaab’s residents, though the work is volatile, arduous, and, when waged, paid by the piece.
So, these are incredibly marginalized people. They’re in a place where this is all they can get for work, it’s all that is on offer.
The majority of those who do this work are in the Global South. They could be refugees, prisoners, or people living in occupied territories.
Clickworker, by comparison, has a user base of over 2 million. Another platform, Appen, has a user base of 1 million. So Mechanical Turk isn’t really that big — partly because it mostly contracts workers in the United States or India, and not many other countries.
Mechanical Turk started as a service only available to programmers at Amazon. This was back in 2001, during the halcyon days of the dot-com boom, when the internet was still ostensibly great and we didn’t have widespread data mining yet. Amazon developed Mechanical Turk to solve an internal problem they had. Basically, its algorithms were failing to recognize product listings. But Amazon soon realized that there was a growing demand for cheap digital labor.
In 2005, Mechanical Turk went public and became a prototype for other platforms like the aforementioned Appen and Clickworker. The name of the platform is actually quite useful in helping us understand the initial logic behind it. The original Mechanical Turk was an outlandish device created in the eighteenth century by a Hungarian inventor. It was designed to resemble a chess-playing automaton. But it was no such thing. Tucked away inside the device was a human chess master. The point was to make it look as though a machine was doing something that humans were doing.
Amazon’s platform is a cheeky nod to this history. Jeff Bezos describes the workers as “artificial artificial intelligence.” The point of the site is that workers appear to contract as machines. This is partly a marketing ploy — another element of Big Tech’s tendency to make everything look high-tech even when it isn’t. But there’s also the theory that it’s set up this way to protect the contractor companies. If you outsource labor and hide it on tech sites, no one will know that your artificial intelligence is actually human intelligence.
Profiting from Crisis
Part of the book’s argument is that we’re moving in this direction, and that’s rooted in a larger argument about employment cycles since the 1970s, profit, and capitalism’s evolution. Can you explain how we got to the point where microwork is a growing sector of employment? Also, please explain your use of the term “subemployment.”
It’s fundamentally a problem of overcapacity. Industries were producing more than could be consumed. So, a lot of companies began looking for cheaper ways to produce their goods. Competition, as is always the case under capitalism, necessitated this.
Companies started to outsource their work to regions where labor was cheaper. That led to fewer manufacturing jobs in countries like the United States and the UK. The workers displaced by this shift were transferred into the service sector, where job growth and productivity gains are notoriously much slower than in manufacturing.
This precipitated a crisis of labor demand. It’s something Aaron Benanav describes in his recent book Automation and the Future of Work. Concurrent with the lack of labor demand, many communist and colonized countries were opening their labor markets. Proletarianization was taking place in those countries, which expanded the global supply of labor.
The upshot of this — counter to other theories — has not been apocalyptic levels of unemployment in the Global North, as is repeatedly predicted in the literature on automation. Instead, we’ve seen consistent downward pressure on wages, worse conditions, insufficient hours, and widespread market volatility.
A lot of the jobs created in recent years have barely differed from the most abject forms of joblessness. In the book, I describe this as “subemployment.” The prefix captures the idea that many people hover in a strange nether region between employment and unemployment.
Simultaneously, due to structural adjustments and deregulation (policies largely coerced by institutions like the World Bank and International Monetary Fund), the informal sectors in Global South countries began to grow. That became a space to absorb workers pushed out of public services and agricultural work. You end up with a global pool of surplus workers, which puts continual downward pressure on wages and conditions. It also stifled the possibility of organizing.
Companies hide the workers almost entirely, both to uphold their reputations and prevent organizing.
This happens partly because workers are given no recourse to action on the platform. If a task is thought to have been done poorly and gets rejected by a contractor, workers can’t really do anything about that. Contractors can review workers, but not the other way around. So, if contractors don’t pay, there’s no way for a worker to flag that and let other workers know.
This allows wage theft to flourish and take many forms. One common way is for lots of workers to be given the same task. The workers who answer in the majority are paid, while the minority are assumed to have done a bad job and are denied payment.
Another way we see workers getting less than promised, which is effectively wage theft, is that requesters could say a task takes much shorter than it actually does. They could say it takes fifteen minutes when it really takes forty.
On Mechanical Turk, for instance, time restrictions are only indicators of how long a task should take. So, the worker will see the task advertised on the platform and think, “Great — a dollar for fifteen minutes of work.” But because these time limits are defined by requesters who are eager to cut costs, a task might be marketed as $1 for fifteen minutes when it actually takes closer to thirty minutes. The worker might not realize this until they’re already fifteen minutes into the task. And if you back out at that stage, then you won’t be paid.
The fact that wages on these sites are called rewards and tokens says it all. I argue in the book that microwork moves us from wage to wager. Paying workers has essentially become discretionary as opposed to contractual. As a worker, you don’t have any guarantee that you’ll be compensated for performing a task.
Paying workers has become discretionary as opposed to contractual. As a worker, you don’t have any guarantee that you’ll be compensated for performing a task.
If those workers are continually not given the wages they were promised, that means a significant amount of stress. It introduces a level of uncertainty about where you’re going to be at the end of the week. There haven’t been any studies about the mental health of microworkers, but those would be really interesting to see.
These sites consistently pay below subsistence wages, according to the standards of pretty much every country across the globe. Crude crowd sites are the type often associated with the highest levels of wage theft. Included within this category are Amazon Mechanical Turk and Clickworker. They’re the two most notorious microwork platforms. They’ve appeared in endless stories in the New York Times, the Guardian, and so on.
Then there’s this other layer of microwork platforms which have received less coverage. That’s partly because the labor conditions are slightly less miserable on these platforms but also because they’ve been good at hiding behind multiple software architectures. Platforms like Appen and Playment cater almost exclusively to the machine-learning needs of large corporations. So, they might have workers processing data for warehouse robotics, chatbots, and so on. They tend to also host tasks that require significant skill. A worker might have to complete an unpaid test to gauge their competence before they can start a task.
Instead of a contractor having to hire a professional translator with labor rights, a minimum wage, and access to a union, they get forty workers completing all those translation tasks — none of whom will have any of those basic protections. It creates a flexibility for capital that neoliberals before now could’ve only dreamt of. You can effectively hire and fire a workforce in the space of an hour. You don’t need any long-term employees, who carry the potential of causing trouble.
Microwork creates a flexibility for capital that neoliberals before now could’ve only dreamt of.
Also, it’s very difficult for unions to see this workforce. They’re essentially invisible. These aren’t easy workers to contact. It’s not like you can send somebody into a microwork platform and organize workers.
Nonetheless, Mechanical Turk workers have set up a forum to pressure the company into providing better conditions — specifically around issues of wage theft and rejected tasks. This is something I heard about from a colleague. I’m excited to hear more in the coming weeks.
Mechanical Turk workers in the past have taken action against dodgy contractors. Earlier, I mentioned the review systems that only allow contractors to rate workers. Workers have pushed back against this one-sidedness by creating a tool called Turkopticon: a browser plug-in that overlays the screens of workers who download it and allows them to write reviews of contractors, which they can then upload in real time. Turkopticon allows other workers to see if there’s a dodgy contractor on the platform.
The problem, though, is that there have been attempts to do stuff like this in the past on Mechanical Turk, and they’ve gotten shut down very quickly by the platform — partly because they’ve relied on the platform itself to authenticate workers for the forum. It’s this difficult situation where microworkers are dependent on software architectures that have been created to prevent them from organizing.
In the book, I don’t offer too many organizational strategies because I feel like it should be left to the workers to figure this out. It feels somewhat condescending for me to come up with those ideas.
But I do work through a couple of potential scenarios that might help inform future strategies. For instance, data sabotage might be one way that microworkers could push for better wages and conditions. If enough workers agree to perform their tasks badly, clogging the flows of data on which these platforms rely, then you could see all kinds of chaos on the internet. Imagine if a bunch of Facebook moderators decided to withhold their labor for a couple of weeks. Facebook would probably have to shut down their platform because it would be swamped with pornographic and traumatic imagery.
Similarly, Google raters find work through platforms like Appen and Lionbridge. If they decided to withdraw their labor, Google searches would no longer be personalized in ways that are particularly useful. It would be pretty catastrophic for these companies.
Microwork platforms don’t offer that. If this is a growing workforce, it’s a growing problem for the labor movement.
The goal of microwork is to show an algorithm how to drive a car or to show a drone how to surveil an urban area. Workers are directly showing machines how to do their jobs, basically. So, the real role of microworkers could be to automate their jobs away.
This isn’t actually that speculative. Companies like Google and Facebook have been pretty explicit about their desire to automate content moderation tasks. If you take the time to read Amazon Mechanical Turk’s terms and conditions, they effectively say that the data from any task completed on the platform can be used by Amazon for its own machine-learning purposes.
Now, it would make sense that the reason why Amazon took the Mechanical Turk platform public — rather than keeping it as an internal service — was not really to take a cut from transactions between workers and contractors which, as I just pointed out, isn’t even that profitable. It’s more likely that they wanted to gain wider access to available data. From Amazon’s perspective, there’s always the possibility that, while hovering over the transactions that take place on Mechanical Turk, they might find something useful for their web-services ecology.
Phil Jones is the author of Work Without the Worker: Labour in the Age of Platform Capitalism and a researcher at the UK think tank Autonomy.
Alex N. Press is a staff writer at Jacobin. Her writing has appeared in the Washington Post, Vox, the Nation, and n+1, among other places.