WinterMilestone 2 Team-UXCrowd

From crowdresearch
Revision as of 07:25, 23 January 2016 by Senadhipathigesumindaniranga (Talk | contribs) (Worker perspective: Turkopticon)

Jump to: navigation, search

Attend a Panel to Hear from Workers and Requesters

Deliverable

Observations:

- panel members are actively involving with Turk

- Most of them are run a blog, forum or a different kind of helping channels to help out the Turk society.

- They maintain a communication channel with requesters and recommend them how to choose workers for their tasks.

- Most of them don't have fixed working hours they work whenever they get a good task.

- Chance of getting a task is unpredictable.

- They take extra precautions when they work with a new requester. Because they don't like to get a negative feedback from them.

- it will take a couple of years to have a good worker profile.

- Even a physically disabled person can get a very good income using crowdsource platforms.

- Researchers find it's very easy to create surveys.

- Requesters use their own templates

- Earnings are various day by day. Its cant be predicted.


Interpretations:

- They all agree that there should be a better system.

- Some workers get the requesters contact details when they going to start their work. If they got a rejection they could contact the requester and can get an explanation.

- Estimations will help them to understand about the time frames.


Needs:

- Workers should complete their task with the highest quality.

- Workers should maintain a good profile, in order to get high pay tasks.

- Requesters Should craft their question carefully, so they could get a good answer.

- There should be a workflow system.

Reading Others' Insights

Worker perspective: Being a Turker

1) What observations about workers can you draw from the readings? Include any that may be are strongly implied but not explicit.

- The majority of Turkers (56%) are U.S. based.

- The primary reason for Turking is to earn money.

- Unfair rejection of work, slow payment, low wage and lack of communication with requesters.

- Requesters put the cost to workers of poorly designed tasks.

- There are no equivalent means for rating Requesters

- AMT deliberately hides the relationship between Turkers and Requesters

- Some Turkers had made decisions to accept somewhat (but not much) lower pay if a task was more enjoyable

- One of the turker has mentioned that “I would much rather have my salary back and drop turking” because of the low pay.


2) What observations about requesters can you draw from the readings? Include any that may be are strongly implied but not explicit.

- Actions can be taken against bad Requesters but the two sides are not treated in an evenhanded manner

- Requesters should understand that nurturing and supporting relationships should be highly beneficial.

- Anonymity does not mean a desire for no communication and cooperation

Worker perspective: Turkopticon

1) What observations about workers can you draw from the readings? Include any that may be are strongly implied but not explicit.

- Workers have no legal recourse against employers who reject work and then go on to use it.

- Amazon has little reason to prioritize worker needs in a market with a labor surplus.

- Workers are taking a risk when they accept a task because payments are not guaranteed.

- the workers as contractors subject to laws designed for freelancers and consultants; this framing attempts to strip workers of minimum wage requirements in their countries.

- By hiding workers behind web forms and APIs, AMT helps employers see themselves as builders of innovative technologies, rather than employers unconcerned with working conditions


2) What observations about requesters can you draw from the readings? Include any that may be are strongly implied but not explicit.

- Once a worker submits work, the requesters can choose whether to pay for it.

Requester perspective: Crowdsourcing User Studies with Mechanical Turk

1) What observations about workers can you draw from the readings? Include any that may be are strongly implied but not explicit.

2) What observations about requesters can you draw from the readings? Include any that may be are strongly implied but not explicit.

Requester perspective: The Need for Standardization in Crowdsourcing

1) What observations about workers can you draw from the readings? Include any that may be are strongly implied but not explicit.

2) What observations about requesters can you draw from the readings? Include any that may be are strongly implied but not explicit.

Both perspectives: A Plea to Amazon: Fix Mechanical Turk

1) What observations about workers can you draw from the readings? Include any that may be are strongly implied but not explicit.

2) What observations about requesters can you draw from the readings? Include any that may be are strongly implied but not explicit.

Do Needfinding by Browsing MTurk-related forums, blogs, Reddit, etc

List out the observations you made while doing your fieldwork. Links to examples (posts / threads) would be extremely helpful.

Synthesize the Needs You Found

List out your most salient and interesting needs for workers, and for requesters. Please back up each one with evidence: at least one observation, and ideally an interpretation as well.

Worker Needs

A set of bullet points summarizing the needs of workers.

  • Example: Workers need to be respected by their employers. Evidence: Sanjay said in the worker panel that he wrote an angry email to a requester who mass-rejected his work. Interpretation: this wasn't actually about the money; it was about the disregard for Sanjay's work ethic.

Requester Needs

A set of bullet points summarizing the needs of requesters.

  • Example: requesters need to trust the results they get from workers. Evidence: In this thread on Reddit (linked), a requester is struggling to know which results to use and which ones to reject or re-post for more data. Interpretation: it's actually quite difficult for requesters to know whether 1) a worker tried hard but the question was unclear or very difficult or an edge case, or 2) a worker wasn't really putting in a best effort.


Milestone Contributors

S.S.Niranga @niranga,