Milestone 2 convectors

From crowdresearch
Jump to: navigation, search

Attend a Panel to Hear from Workers and Requesters

Deliverable

Report on some of the observations you gathered during the panel.

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.

1. Turkers work for fun but mostly they do it for the monetary compensation.
2. Many a turkers do crowdsourcing for hand to mouth monetary support purpose.
3. Workers tend to laud requester when they approve HIT and criticize when HIT gets rejected.Turkers have an emotional involvement.
4. A good engaging design, fast response time are a couple of features turkers expect from requester.
5. Experienced turkers are concerned about the acceptance rate whereas the novice workers are more concerned about the HIT count.
6. Turkers do not want media interfering and ruining the freedom of crowdsourcing.

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

 1.Requesters help us how to handle hits on mturk.
 2.Requesters see that workers are provided with the liberty to work.

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.

 1.workers should be paid for how much they have worked which sometimes is not happening.
 2.communication gap exists between worker and requester which is not okay with the worker.
 3.Turkopticon brings together diverse range of workers and promotes social integrity and inter dependency.

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

  1.Requesters are not as helpful as they tend to be.
  2.workers are judged without analyzing the effort they put. 

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.

  1.workers tend to take up hits of higher cost.
  2.They expect most of their hits to be approved.
  3.Most of the workers give away random answers in order to get the task completed.

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

  1.Answers should be validated in such a way that it should be beneficial to the workers.
  2.Providing incremental knowledge through wide varieties of questions.
  3.all the workers cannot be experts,so questions should be framed keeping it in context.

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.

  1.Not much innovative ratings of what the workers are doing.
  2.Talent mismatch always happens.

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

   1. Requesters pay different wages for different activities of the same kind. eg: Text editing 10 lines costs different from text editing 100 lines.
   2.Requesters benefit more from standardizing the tasks by building reliability.

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.

 1.Both the good and bad workers get paid equally.
 2.workers cannot contact the requester until the requester's name is provided.

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

1. Need problems that have been over years to be addressed(Quality, estimated time, API management etc.)
 2. The interface for requester is too complicated. 
 3. If a requester needs quality work done, he needs to take care of lot of things (Quality assurance, qualification of workers, break tasks to workflow etc.)
 4. With reduction in quality, requesters tend to treat good and bad workers alike. 

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.

 1. Some of the hits are attractive and some are boring.
     For instance there are hits which have a reward of $15 and the time limit is just 20 minutes and they can be even accomplished within the time.
 2.Some hits need qualifications to accept.
   some hits in mturk require specific qualifications to be accepted and solved..

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. 1. Freedom. Best practices can create excellence, but every task doesn't deserve a best practice or a micro-managed approach. (Yes, even you, fast food industry.)

Autonomy and latitude breed engagement and satisfaction. Latitude also breeds innovation. Even manufacturing and heavily process-oriented positions have room for different approaches. 2. Targets. Goals are fun. Everyone—yes, even you—is at least a little competitive, if only with themselves. Targets create a sense of purpose and add a little meaning to even the most repetitive tasks.

Without a goal to shoot for, work is just work. And work sucks. 3. Consistency. Most people can deal with a boss who is demanding and quick to criticize... as long as he or she treats every employee the same. (Think of it as the Tom Coughlin effect.)

While you should treat each employee differently, you must treat each employee fairly. (There's a big difference.) A worker's efforts has to be bestowed by the requester.

  • 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.

 1.Requesters need to be interactive with the workers.
 2.Requesters have to give the liberty to the workers to work on all the tasks.
  • 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.