Difference between revisions of "WinterMilestone 2 Team-UXCrowd"

From crowdresearch
Jump to: navigation, search
(Deliverable)
(Deliverable)
Line 25: Line 25:
  
 
- Requesters use their own templates
 
- Requesters use their own templates
 +
 +
- Earnings are various day by day. Its cant be predicted.
  
  
Line 31: Line 33:
 
- They all agree that there should be a better system.
 
- 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:'''  
 
'''Needs:'''  
Line 40: Line 45:
  
 
- Requesters Should craft their question carefully, so they could get a good answer.
 
- Requesters Should craft their question carefully, so they could get a good answer.
 +
 +
- There should be a workflow system.
  
 
== Reading Others' Insights ==
 
== Reading Others' Insights ==

Revision as of 20:02, 22 January 2016

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.

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

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.

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

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,