WinterMilestone 2 vaastav
- 1 About
- 2 Needfinding Lectures
- 3 Attend a Panel to Hear from Workers and Requesters
- 4 Reading Others' Insights
- 5 Do Needfinding by Browsing MTurk-related forums, blogs, Reddit, etc
- 6 Synthesize the Needs You Found
This page contains the information I gathered about Workers' needs and Requesters' needs.
But before I get into details about the needs I found, I just want to take a step back and talk about the needfinding methods the lectures talked about.
- Watching people perform a task can help build empathy for them. This in turn allows us to think from their perspective and better understand the problems that they face.
- Deep Hanging Out : Living people's life is another good way of trying to understand more about the needs of the people in that working situation. ( The whole concept of the TV reality series Undercover Boss is based on this. )
- 5 Key things to take from Participant Observation:
1. What do people do now? 2. What values & goals do people have? 3. How are these particular activities embedded in a larger ecology? 4. Similarities & Differences across people 5. Other types of context ( Basically Science of Deduction. TL;DR Be Sherlock )
- Be a work apprentice. ( This is kind of like how medical interns learn a lot by shadowing a doctor )
- Pay attention to how people remind themselves of things. ( Notepads, Post-it notes )
- Errors are a "goldmine".
- Don't focus on what people say but rather on what people do
- Get people who are representatives of the target userbase
- Approximate if necessary ( Get the closest thing to a representative )
- "Self-consciousness is the enemy of interestingness"
Anatomy of a good interview question:
- Don't ask leading questions.
- More open-ended the questions are, more interesting the answers will be.
Attend a Panel to Hear from Workers and Requesters
Report on some of the observations you gathered during the panel.
Reading Others' Insights
Worker perspective: Being a Turker
This paper analysed the posts and threads on Turker Nation and dealt exclusively with the opinions of the workers.
- The main reason why Turkers Turk is for monetary gain aka to earn money.
- They would like to do this for actually learning stuff but for some people this is vital to generating their income to make ends meet. So they take up this lousy pay for work. ( Example 1 in the paper )
- They get frustrated when their work gets unfairly rejected or if they feel that the requesters didn't provide good enough reasons to reject their work. They also hate being subjected to demeaning comments and being blocked. ( Example 5 in the paper ).
- Although they are very understanding if they feel their rejection was valid and their work wasn't upto the mark. Additionally, they like it when they are politely communicated to. ( Example 7 in the paper )
- The only way they can avoid "bad" requesters is by avoiding their tasks. There is no way for them to block the requesters like the requesters can. So there is imbalance of power.
- Sometimes they only pay those who gave answers which were part of the majority
- They don't like being duped by bots.
Worker perspective: Turkopticon
Requester perspective: Crowdsourcing User Studies with Mechanical Turk
Requester perspective: The Need for Standardization in Crowdsourcing
Both perspectives: A Plea to Amazon: Fix Mechanical Turk
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.
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.
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.