Difference between revisions of "WinterMilestone 3 hamdur.rahman automatic rating and staged process"

From crowdresearch
Jump to: navigation, search
Line 61: Line 61:
 
** All the suggestion will have scale for acceptance by the requester
 
** All the suggestion will have scale for acceptance by the requester
 
*** Not required, Partially required, Required, Completely required
 
*** Not required, Partially required, Required, Completely required
 +
[[File:Suggestion Need.png|thumb|Suggestion]]
 
*** The scale will determine the payment to the worker
 
*** The scale will determine the payment to the worker
 
** It will have number of effect on worker and requester
 
** It will have number of effect on worker and requester

Revision as of 12:02, 31 January 2016

Reputation-related Idea

Representation-related Idea

Dark Horse idea (Mandatory)

I have tried to holistically address the issue of reputation and representation through some ideas and concepts and I cannot separate it into two parts.

My Interpretation of reputation and representation:

  • Reputation through rating is flawed because
    • It is influenced by the last result of any problem.
    • How the negotiation has taken between two person.
    • State of mind at the time of providing rating.
  • Representation is mostly about positive conflict resolution and upholding rights.
  • Amazon marketplace takes care of both
    • It has a rating system
    • But the most important is that it care of the sellers (person whose hard work is on stake) by securing the payment.

Aim of the System (New generation Crowd-sourcing platform):

  • Take care of worker (person whose hard work is on stake) by making the system automated.
  • Bring "Work" in focus, every detail needed to complete the work in focus (Clarity, Success criteria, Payment, timeline, related works).
  • Requesters and workers become independent of each other. They are only related to work.


Skill sets (New Idea)

  • Consist of skill to complete a work. It is measured on scale (BE: Below expectation, ID: In development, ME: Meet expectation, EE: Exceed expectation)
Worker and Requester Rating
  • Requester need skills to create works and accept high quality work.
    • Example: Task clarity, Total value of posted work, Accepting suggestion and task success criteria, payment
  • Worker need skills to complete work and accepting money for the completed work
    • Example: HTML, JS, CSS, User Testing
    • Worker can increase their rating by providing suggestion, verifying solution and do new work
  • Skillset are assigned to requester, worker and work
    • Skillset to requester
      • By requester himself
      • By workers with whom he has worked
      • By system with time (Learning with more work)
    • Skillset to worker
      • By worker himself
      • By requester and worker with whom he has worked
      • By system with time (Learning with more work)
    • Work
      • Requester
      • Worker
      • System

Stage and Status of a work (New Idea)

Stages and status of Work
  • Different stages through which a work has to proceed before being accepted by requester and payment made to worker.
  • Status are Draft, For clarity, For estimation (Time and Money), In Work, For Verify, Done

How it Works

  • Requester create work or batch of work in the crowd-sourcing platform
    • Requester will provide information (like Work to do, success criteria)
    • System will provide/attach skill set needed to complete this work
    • Requester will add/remove skills needed and apply the scale needed for each skill
  • Requester will change the status of work from "Draft" to "For Clarity" and also add the number of workers with specific skills needed to provide suggestion, clarification
    • The system will select workers with the specified skills or previous experience of same type of work and provide work in their work feed.
    • Once worker accepts this work:
      • In this status the workers will provide suggestion to bring clarity on the work and its success criteria
      • He can also add/remove skills
    • All the suggestion will have scale for acceptance by the requester
      • Not required, Partially required, Required, Completely required
Suggestion
      • The scale will determine the payment to the worker
    • It will have number of effect on worker and requester
      • Worker skill scale will be increased
      • Worker will get payment for suggestion
      • Task clarity is increased
      • These workers will be preferred for completing the work in next stages
      • Requester cannot cheat the worker as any suggestion added to the work will also be reflected to the worker.
  • After completion of this phase the worker will change the status of the work to "For estimation"
    • System will provide rough estimate (on scale) by:
      • Comparing with earlier similar works done on the platform
      • Earlier similar works done by workers with same skill set
      • Comparing with related work in the same batch work created by requester.
    • Again worker with skill set will notified and they will bid for the work. They will also be assisted by the system by providing estimates from the worker history of work.
      • Workers in this stage can send the work back to "For clarity" if the information are missing or down voted by most selected workers.
  • Worker will select the work and the status will change to "In Work"
  • Once the worker will complete the work he/she will change the status to "For verify"
    • System will select worker and provide the work in their work feed.
    • Verification worker will verify the work with the provided success criteria
    • Payment of the verification work will be provided from the original worker payment. (Workers are working as consultant and outsourcing their work to other worker)
    • Motivation for verification is for new workers as it is the easiest way to increase their skillset.
    • What we are doing here is making spamming expensive as compared to completing the work with quality.
    • Worker after accepting the verification suggestion will change the status to "Done"
  • Requester will be notified.
  • In all the process the rating of the worker and requester is provided by the system by the result of different stages. For example
    • The requester "Work clarity" rating will be low if he accept lot of changes in the work.
    • Manual requester rating is not important as worker take care or are part of important stages like:
      • Clarification
      • Estimation
      • Verification


Usability Test Flight (People who want to head start with UX)

Please create separate wiki pages for your actionable items and long term vision ideas, so we can link to it individually.

Actionable items

Report on the basis of interview + your own experience. If you cannot find someone to interview, report your own experience.


Long term vision items

Report on the basis of interview + your own experience. If you cannot find someone to interview, report your own experience.

Milestone Contributors

@hamdur.rahman