Going forward

With Lisa at the helm, My Boss Is A Robot is going to take a slightly different path toward our goal of doing crowdsourced journalism. Partly that’s because our first attempt didn’t exactly produce stellar results. But it’s also because Lisa thinks about the problem in a different way. Here’s what she says about her plans going forward:

The initial attempts to create news articles hit two obstacles: low speed and low quality. Unlike simple tasks such as labeling images, fewer workers are willing to write news articles, which require more cognitive effort. Since workers are less willing, it takes longer to assemble a crowd and complete the task. Moreover, either for lack of ability, or because workers are not putting sufficient effort into the task, the quality of the crowd’s work is low.

In order to find talented and motivated workers, we need to build a stable workforce. Our approach is called invitation-based participation. Instead of posting tasks to the public crowdsourcing market, we will invite workers to join a writing team. Workers who accept enjoy special benefits. We’ll also focus on building a team with a shared goal, establishing a bond between the requestors and workers, as well as between workers themselves. The team environment also allows for feedback and integrated learning.

The idea of building a stable workforce in the crowdsourcing market was inspired by theories from several disciplines. Ronald Coase, an economist, explained the emergence of the firms in terms of transaction costs. There are many costs that occur in the processing of market-based transactions: for example, search and information costs and bargaining costs. Firms with long-term employees are able to save such transaction costs. Posting the writing tasks to the crowd in the crowdsourcing market leads to very high transaction costs: long waiting times, lower quality from the unfitted workers, and higher payments. By building a long-term relationship with the right workers, we can reduce such costs.

We have conducted some studies and the preliminary results show that invited-participation leads to better performance. Now we’re gong to experiment with various ways of building up a stable and high-quality workforce. We’re also trying to combine machine learning techniques with the crowd. We will first shorten the source articles using text summarization techniques, then let the crowd work on the shortened articles. This machine-assisted summarization process is expected to be an integrated part of crowdsourced journalism.

Are we stepping back from our original goal? In some ways, yes. We’d hoped to be able to create articles using any workers from Mechanical Turk. We’re admitting that, at least at this stage, we need more control over our workforce. Having said that, our workforce will still consist of untrained journalists. If the system works, we’ll still be creating articles rapidly and at low cost. And if it fails? Maybe we’ll have shown that journalism isn’t something that can easily be done by an algorithm and the crowd.

We’ll be back here with more results as soon as Lisa has them.

Back on track

We’ve been stalled for a while looking for a new technical collaborator, but we’re happy to announce that the project is now back on track. Lisa (Lixiu) Yu is a new postdoc at the Human Computer Interaction Institute at Carnegie Mellon. She has done extensive research in the areas of crowdsourcing, creativity, and open innovation, with a focus on crowdsourcing complex and creative work. She’s a perfect fit for our project to crowdsource journalism, and we’re happy she’s signed on.

We’ll have a more extensive post coming up, detailing where we are, what we’ve learned, and what the plan is from here.

it’s still very quiet

It turned out that we were a little over-confident when we said that a new researcher would soon be heading up our project. It didn’t work out with the person we had in mind, so My Boss Is A Robot remains temporarily leaderless. Our friends at Carnegie Mellon are on the hunt for a suitable candidate and we hope to have someone in place come January. If you think that person might be you, drop me an email at jg@jimgiles.net. You’ll need expertise in computer science, an interest in crowdsourcing and a desire to experiment with the journalistic process.

an update

It’s been very quiet recently at My Boss Is A Robot. That’s not because we’ve given up. It’s because two team members have become fathers and Susheel Khamkar, who has been posting the jobs on Mechanical Turk and analysing the results, has finished his MS at CMU and taken a position at CrowdFlower. (Congrats, Susheel!) This has set us back a bit, but Susheel’s work is being handed over to another CMU researcher and the new fathers will soon find time to start working again. So don’t give up on us. We’ll have more results soon.

lots of people can write well

Our first experiments at crowdsourcing journalism hinted that writing would not be our big problem. The quality of the material we’ve been getting back is variable, but basically okay. Certainly good enough that an editor could knock it into publishable shape.

These results seem to be in line with other findings. Marti Motoyama and colleagues at the University of California, San Diego commissioned a bunch of articles from workers at Freelancer, a Mechanical Turk rival. (Freelancer jobs tend to be better paid and to involve more work than the “microtasks” posted on Turk). The results don’t make for thrilling reading, but most are reasonably well written.

Motoyama commissioned the articles as part of a study of the outsourcing of “web service abuse”, meaning offers of payment for shady tasks such as the creation of Gmail accounts for spamming purposes, or the posting of fake positive reviews. It turns out there is a lot of this stuff on Freelancer — check out his paper for details.

Freelancer is also used to generate content for spam purposes. This usually involves the creation of cheap 500-word articles that are used to fool Google and other search engines into giving a website a higher rating. I wrote about the process in a little more detail earlier this year after I interviewed one of the folks behind a similar scheme.

In this case, Motoyama commissioned 400-word articles on skin care products. He shared the results with me and they’re much the same as the stuff we’ve been getting back. Some are contain errors and horrible writing, but many do not. On the Flesch–Kincaid Grade Level, a measure based on word and sentence length, the pieces fall somewhere between Wikipedia and Cosmopolitan in terms of readability.  After a little quality control to weed out the worst workers, it’s seems that it be would relatively easy to recruit writers on Freelancer, just as I think it would be on Mechanical Turk.

That doesn’t mean that we’re finding our challenge easy. In our experiments over the past few weeks we’ve been struggling to get workers to summarize the papers as we’d like. It’s probably because we’re now experimenting with three papers that are more jargon-filled and conceptually complex that the study we used in our initial trials. We’ll update you in full once all the results are in.

scam jobs on Mechanical Turk

The cost of labour on Mechanical Turk is both tantilising and unsettling. Tantilising because it’s so cheap. That makes it possible to outsource skilled tasks like translation and transcription at remarkably low cost. As a journalist, it’d be great if I could afford to routinely transcribe interview tapes. Prices are still a little high for that, but my hunch is that they will come down.

The unsettling aspect concerns the impact of these wages. Some folks who work flat-out on Mechanical Turk probably earn $2.00 per hour. That’s okay in India, but many Turkers are based in the United States, where the federal minimum wage is $7.25 per hour. Discussion forums like Turker Nation are full of people complaining about low wages, but there are still plenty of US-based workers on the site. Sure, some workers find it a pleasant place to waste time and don’t see it as a full-time job. But that doesn’t account for all workers. I’d like to know how many people depend on the site.

The Turker forums are also full of workers complaining about scammers — employers who post jobs and don’t pay, or reject work arbitrarily, thus removing the need to pay. There is a lot of frustration directed at Amazon also. It’s clear that workers think that the company could be doing a better job of cleaning up the site.

I’ve been taking a look at these issues over the past couple of months. The results came out last week in New Scientist. The story is subscriber-only right now, but the brief summary is that scammers continue to evade Amazon’s moderator system. There are jobs that attempt to trick workers into giving away credit card details. Plus lots of jobs that are clearly lead generation scams. The worker fills in an online survey, pretending to be interested in, say, going back to college. Then the employer gets paid a referral fee from colleges looking for new recruits. So the college is being conned and, in the jobs I tried, the workers were too, because the employer didn’t pay me after I filled in the survey. (I’m still getting calls from colleges).

I was struck by the variety of these scams, but they don’t seem to bother experienced workers too much.  After the story came out, I thanked the workers on Turker Nation who had helped me, and posted my piece on the forum. One response to my story noted that the scams were easy to avoid and that it was low wages that are the problem.

Scams such as things offering $20 for me to sign up at whatever are not a real big concern for me on Mturk. Do most workers fall for this often? More than once? Ever?

The real problem for workers on Mturk is lowballing requesters. This is how I see it. It’s as if I were walking on a road that was 90% strewn with sharp slivers of glass, and someone is saying – The problem is that there are some huge potholes!”

version 0.2

As discussed last month, our initial attempt at crowdsourcing the journalism process led to a draft article that was okay, but not great. It certainly wasn’t good enough to be edited. If this were regular journalism, the editor would have emailed the piece back to the author together with a curt message about the need for cleaner writing.

Over the past couple of weeks, we’ve been talking with our collaborators at Carnegie Mellon. We know that we need to do a better job of quality control. Our system builds up each paragraph of the piece in parallel, which can mean that different workers create each chunk of copy. This should make the process quick and easy to outsource. But it also provides lots of opportunity for errors. We’ve been talking about how we can weed out inaccuracies as early as possible, before they become too great in number.

Part of the problem was, we think, carelessness on our behalf. We did a decent job of telling workers what to include in the story, but didn’t explain what to leave out. That led workers to produce jumbled paragraphs that included too much information.

We also want to incorporate fact-checking mechanisms into the early stages of our automated workflow. We’re going to experiment with a new round of tasks in which workers check the copy produced by other workers, so we can chuck out problematic paragraphs straight away. In fact, we think we might get better results just by telling our workers that this is going to happen. Research suggests that crowdsourced workers perform better when they know that their output is going to be compared with that from other workers, or checked for accuracy.

We hope to start running the new tasks this week or next. Results to come as soon as we have them!

technopoly

First visit to My Boss is a Robot? Try starting with the about the experiment page.
Technopoly, by Neil Postman

As we dig into the philsophical roots of radical crowdsourcing, we are finding that the idea that humans can be organized and ultimately made subservient to machines is not particularly new.

The book Technopoly, written in 1992 by American cultural critic, Neil Postman, lays out much of the history of society’s relationship with technology and, though it was written before the widespread use of computer networks, proves somewhat prescient about where the unexamined adoption of information technologies might lead.

Postman frames his argument with the story of King Thamus, described in Plato’s Phaedrus. Thamus is presented with a number of inventions–calculation, astronomy, and writing, to name a few–but is unimpressed. He takes specific issue with writing, claiming that it will cause people to stop remembering things in favor of writing them down, leading them to gain much information, but little wisdom. To the inventor, Theuth, he admonsishes, “the discoverer of an art is not the best judge of the good or harm that will accrue to those who practice it.”

In broad terms, Postman then describes the evolution of society from tool-using cultures where technology is integrated into daily life but is bound by a social or religious worldview, through technocracy–where technology plays a central role in a culture, becoming a source of social power and challenging traditional structures–and finally technopoly, which Postman calls the “submission of all forms of culture to the sovereignty of machines and technology.”

Postman writes that we are entering a period of technopoly, the immediate roots of which stretch back at least as far as Frederick Taylor, the father of scientific management. Taylor was famous for efficiency studies in which repetitive tasks were measured and standardized similarly to machine parts. Postman sees in this behavior “the first statement that society is best served when human beings are placed at the disposal of their techniques and technology, that human beings are, in a sense, worth less than their technology.”

The rest of the book examines the dawning information age and its attendant glut of data which, Postman argues, encourages an over-reliance on statistics–an “invisible technology”–to replace social or religious sources of meaning. Postman also has a special loathing for computers, which he sees as usurping decision-making power from people.

Despite immediate impressions, the book is more than just the ranting of a Luddite; Postman readily acknowledges the many conveniences and advances that technology has enabled. He simply cautions that society take a note from King Thamus and look carefully at what is lost when a technology is adopted.

One wonders what Postman, who died in 2003, would make of crowdsourcing sites like Mechancial Turk. The idea seems an almost pure expression of technopoly–people literally take direction from, and are compensated by, computers. Ever the technological skeptic, he might take heart to know that there may be a limit to this trend, perhaps demonstrated in some small way by the fact that our experiment to completely mechanize the process of writing a news article isn’t going very well.

back to the drawing board

First visit to My Boss is a Robot? Try starting with the about the experiment page.

We have now assembled an entire article using crowdsourced labour. Time to head to the editing stage. Except there’s a problem. Or rather there are lots of little problems. There are so many minor errors in the copy that there isn’t much point trying to edit it. An experienced editor would be able to clean it up, but we want to crowdsource the editing process. That will require cleaner copy than we have. So it’s time to go back to drawing board.

We think we know where we went wrong. In our work-flow, the laborers on Mechanical Turk construct the article paragraph by paragraph. The results looked quite reasonable at each stage — see, for example, Surprising good writing from the Turkers. But each paragraph has one or two problems. Some contained unnecessary information, others had minor errors. When the paragraphs are strung together the errors compound. The result is something of a mess.

To make the process work, we need to produce cleaner copy first time round. If we eliminate the errors in the initial writing stage we should, I think, be able to produce editable copy. To do so, we need to experiment with different quality-control mechanisms, such as having workers check paragraphs for accuracy, or having them follow a stricter template, similar to Martin Robbins’ brilliant satire of science “churnalism” for The Guardian.

I spent a day at a crowdsourcing workshop earlier this week and quality control mechanisms were a big part of the discussion. Crowds can execute tasks quickly and cheaply, but they are very hard to control. That’s one reason why CrowdFlower, which helps companies execute jobs on Mechanical Turk, is doing so well. (I’ve visited their offices several times over the past few years — almost every time I was directed to newer and bigger premises).

Anyway, it’s time to start rethinking our work-flow, with a new emphasis on quality. Niki Kittur and colleagues, our collaborators at Carnegie Mellon, are going to experiment with different quality-control mechanisms. These could include voting or fact-checking, for example. The idea is to find mechanisms that are quick, cheap and reliable. Results to come soon!

the automated interview

We already know that it’s possible to produce encyclopaedia entries quickly and cheaply using Mechanical Turk — our collaborators at Carnegie Mellon unveiled a system for doing so last year. But news articles are harder to crowdsource, in part because journalists need to do interviews. How can we automate the process of finding and interviewing expert sources?

Here’s our approach. Like I said in a previous post on the ethics of crowdsourced journalism, it’s something of a fudge. But it seems to work quite well, at least up to a point.

To find sources, we use the references section of the paper that we’re writing about. (Quick recap: our system takes a scientific paper and automates the process of producing a news article about that paper). We start by asking workers to find email addresses for the authors of relevant references. We’re still experimenting with the best definition of “relevant”, but using the first few citations works fairly well, since these tend to refer to studies that are closely related to the paper itself. To weed out random answers, we only use emails that are identified by several workers.

Once we have addresses for relevant experts, the robot boss emails our potential sources a copy of the paper that we’re writing about, together with a list of generic questions, such as “What are the applications of this work?” The emails are signed by us.

When the answers come back, the robot boss creates two final tasks. One bunch of workers selects sections of the email that sound most interesting; a second set reads the draft of the story and inserts the selections where appropriate. For example, here’s a quote that the workers culled from one expert’s response to our email. (By way of context: we’re writing about a study on the factors that make music popular).

“Without passing judgment on their talents, I wonder if YouTube creations like Justin Bieber and Russell Cooper would have become stars if YouTube did not post the number of times a video clip has been viewed.”

It’s a nice quote and, having seen the full email from the source, I think the workers did a good job of homing in on the quotable sections. But problems arose when we asked them to insert the quote into the story. In fact, the problems were significant enough for us to think that we need to tweak some of the steps the precede this quote-getting stage. More on that next week.