WinterMilestone 2 Ganler=edit
1. Make grammatical mistakes while writing
2. Find it huge to correct a tense change
3. Find it difficult to trim the size of the written paragraph
4. Find it difficult to explain the task to workers
5. Commonly make spelling mistakes
6. Take help from friends and people they know to proof read or reduce the article size
7. Expects further help in complex tasks
8. Expects text correction delay time to be less – prefers real time
9. Is concerned about the task and content privacy
10. Wants an interface which is understandable and helps him progress
11. Waits for the correction to be clearly differentiable from the original data
12. Looks out for what part of the sentence has been compressed and which part has been expanded
13. Looks out for people who can complete the task on time – get things in limited pages and within the deadline
14. Is concerned and wants to confirm if the worker has understood the task – wants to confirm
15. Wants the control in his hands to accept the corrections or not
16. Wants to notify only the change required in certain pages or paragraphs
17. Finds it difficult to express the correction method correctly to the computer in case of scripting.
18. Finds it difficult sometimes even to express to workers on what correction is to be done
19. Wants to decide on how many people should work on his content
20. Wants to avoid lazy turkers waste his time
21. Similarly wants to avoid Eager Beavers as they complicate the task for him
22. Wants to keep a check on if the workers are motivated enough while working
1. Find it easy to make corrections in already written sentences
2. Generally help in article corrections
3. Perform spell checks
4. Have a cognitive load to maintain the sentence meaning right.
5. Find it not easy to every time get the article they understand
6. Maintain the privacy of the content and task
7. Sometimes unsure if they made the right corrections – expecting another proof-read
8. Look for an option to filter their area of comfort in article selection
9. Is concerned if the requester is fine with his understanding of the task – wants to confirm
10. Expects the requestor to accept the rightly done work.
11. Finds it difficult to understand the current interfaces on how to intimate the requestor on the changes made
A Plea to Amazon: Fix Mechanical Turk!
1. Find it much easier to navigate through amazon.com than through Turk
2. Frustrated on repeating the same thing again and again
3. People are building on top of MTurk to improve their ease of work
4. People find it very difficult and so are trying to make a better marketplace than MTurk
5. People want to Scale up, manage the complex API, manage execution time and ensure quality
6. Posting tasks should be easy for requestors
7. They find the interface very difficult to manage
8. Sometimes requestors are hiring full time developers to get the complex tasks done
9. It is very difficult for small requestors to grow
10. Very few requestors have one-pass tasks. And the requestors who have huge number of tasks are not comfortable using MTurk.
11. Some users build and inframe-powered HIT misuse the system and get away
12. For a long term user, this kind of additional personalized interface works, but not for short term users
13. Requestors cannot easily differentiate good workers from bad workers
14. Getting the task done by multiple uninterested workers and get the quality check done is a huge frustration and a waste of time for the user
15. User wants to get these questions verified
a. Does the worker have the proper English writing skills?
b. Can the worker proofread?
16. Want to provide rating without cognitive load.
17. Requestor is the most affected guy in MTurk unlike the sellers in amazon.com
18. Rating must be given from the side which is getting affected.
19. Requesters might have an idea or not have an idea of the time required to complete the task
1. Good workers are unable to get to the requestors
2. Wants to be rated correctly by the requestor
3. Wants to be able to appeal to the requestor on the work being rejected
4. Want to be able to differentiate the type of tasks they are about to work
5. Workers are not expert at all tasks, so they want to choose tasks only which they are comfortable at
6. Workers want to rate the requestors according to their purpose.
7. Workers wait for the requestor to start paying so that they can work further and rely upon the previous experience.
8. Check for the speed of payment from the requester
9. Check for the rejection rate for the requester
10. Want to appeal for a rejection
11. Check the previous work ratings and experiences with the requesters
12. Like to know an estimate of how long it will take to complete the task
13. Look for most recent HIT groups or the most HIT groups ignoring the smaller ones