WinterMilestone 3 Crayons RepresentationIdea: Taking inspiration from successful community based sites

From crowdresearch
Jump to: navigation, search

Worker and requester representation (open governance)

Idea

Our idea is derived from the place where the similar concepts have been successfully implemented; places like like Wikipedia, Stack Exchange Network and Reddit. So one can safely put the idea to test.


Representation

  • A user can act as a requester as well as a worker. This unifies the whole history of that user at a single place. If a user is looking for the requester then he/she can check out the requester tab and vice versa.
  • Introduction of gamification in the terms of the karma points (worker & requester karma points). Every user will have 2 kinds of karma points - worker and requester karma points (explained further in the sub sections).
  • Based on the karma points, users get certain rights. This decides the level of moderation a user can do on the platform. Based on the points, one can flag the tasks being submitted to a HIT to be reviewed by the worker, one can flag the task for the improvement in the template, one can edit the rejected submissions or one can review the submissions, one can vote (upvote and downvote) on other users, so on and so forth. All of these community activities will increase the reputation of the user and in turn trust amongst the users. And, probably help in getting better results faster.
  • Introduction of a forum to discuss open ended problems. Here one can discuss about various UI improvements, ask questions about working with some specific kinds of HITs or manage conflicts and grievances.
Worker
  • Worker karma points. Each worker will have worker karma points which will increase as the user engages with the community and produces proper quality tasks.
  • Reviewing other users' submitted and rejected work. Other users given they have enough reputation points, can flag and even review the work submitted by other users so that it becomes a quality submission. This can be a huge help to the requester as well. Now, he doesn't have to check it as it has already been flagged or reviewed and he can ask the submitter to resubmit it. This will give the user more reputation points.
  • Editing other users' submitted and rejected work. If a user is feeling extra generous, then having the required reputation points, he/she can even do very minor edits on the flagged/rejected responses to make it proper for submission. This will give the user more reputation points (worker karma points).
  • The worker karma points of a worker will go down if he/she didn't produce the quality work and gets rejected.
  • Properly showing the work history in the chronological order (with most recent at the top) and probably with subtle color coding to show where user screwed up and where he excelled.
  • Based on the submission history, display stats to give a rough sense of the submission pattern of the user. Stats like submission rate, rejection rate, community edits etc.
Requester
  • Requester karma points. Each requester will have worker karma points which will increase as the user engages with the community and produces proper quality tasks.
  • Minor editing of other's posted HITs. One can edit other requester's posted HIT if he sees some template/format problems. One can also, flag and comment on it so that the requester can improve the HIT.
  • The requester karma points of a requester will go down if he/she rejected a submitted work without reviewing or giving a proper reasoning for the rejection.
  • Again, just like in the worker profile, requester tab should also have a posting history. Organized in proper chronological order with the same color coding for the negative and positive activity.
  • Based on the history, display stats to give a rough sense about the requester. Stats like HITs posting rate, rejection rate, community edits etc.

Design

With the above features proposed, there is a critical requirement for a proper design. No matter how efficient the system is, there is always a requirement for the proper UI/UX.

What are the goals of the design?

  • Keep it consistent
  • Help me score

Which aspects of your design reflect each goal? How does your design solution addresses the users' needs?

  • Keeping it consistent is directly the consequence of unifying the requester and worker modes in the same account with the similar features for both. The worker is on the platform to earn money and not waste time to learn the rules and UI on the platform. Everything should be as consistent and intuitive as possible.
  • Help me score (for both, workers and requesters) design goal aims at making the platform easy to score (reputation points) via tasks and quality results. And, with the history properly shown with the slight color coding, makes it easy to figure out how the worker is and how will the relationship be with him. This, also solves the problem of "making your voice heard".