Milestone 3 Triple Clicks

From crowdresearch
Revision as of 21:47, 18 March 2015 by Mikeyoung (Talk | contribs) (Dive Deeper into Specific Ideas)

Jump to: navigation, search

Initial Brainstorm

Trust-related Ideas

  • Verification process and indicator of verified identity (both for requestors and for workers).
    • Example: Airbnb (Verified email address, phone number, Facebook / LinkedIn, Reviews, Drivers License or other official ID)
    • Would be curious to know if requestors and workers prefer to be anonymous but still “verified” by the system? Does anonymity support or deter trust building?
  • Requestors must have a valid Credit Card, Bank Account, PayPal, or pre-purchased credits on file
    • Example: Elance (Requestor posts funds for the project and if s/he doesn’t approve funds for release within X number of days, the Elance system will do so automatically)
  • Recognizing the community support (unpaid time) that workers gift to the platform. It may not be monetary, but being able to showcase what a worker is doing for others and what they excel would help highlight their contributions and help requestors recognize the greater community at hand.
  • Development of policies / procedures / code of conduct / integrity around community behavior. Adhering to these lets you stay on the platform and continue to be an active user. Violating these will have you removed or put on suspension pending further investigation.
    • Similarly, standardized and readily accessible documentation and technical support.
  • Algorithmic and community-driven efforts to scale moderation and anti-fraud measures.
  • Text that is pasted into a field is automatically subjected to a Captcha to submit.
    • Meant mostly for surveys or forms where there are multiple text fields.
    • This would, hopefully, be such a pain to deal with that scamming workers will skip such tasks.
  • Pair up new workers with new requesters for each one’s first/early HITs.
  • Make Requesters have to earn a certain amount of money as a Worker before they can submit HITs as a Requester. Or make their first five tasks free and before they need to earn money as a Worker.
  • Allow Workers to vote on the fairness and respect they felt when dealing with a Requester. Requesters that have been voted as fair and respectful by enough Workers will have an icon designating them as Super Requesters (or something...)
  • In order to verify that a Worker is who she says she is, a Requester can ask the Worker for a proof of ID, essentially a photo with written text supplied by the Requester.
    • But how does this verify anything other than appearance…?
  • Allow Workers to create teams which will self-police their members. Allow Requesters to create teams which will self-police their members.
  • Auction Style pricing with min and max willing to work for/pay for
  • Surge pricing. $ increases with demand (uber)
  • When requesters submit HITS they're shown average $/time for that tasks to anchor their pricing
  • Show requesters response rate
  • In app browser chat

Power-related Ideas

  • A platform should have a tool that evaluates a task’s needed skills, time, clarity, and requirements to recommend a price on the task that is fair, too high, or too low.
    • Example: Early textbook selling site in the US would tell you what the average price was for the same book across different condition types (e.g. Chegg, Amazon). Based on that, buyers could see how to competitively price their books well as being able to see the ratings, number of books sold, credibility and pricing of other competing sellers to help ensure that they can sell their books.
  • Requestors that are rejecting work or HITs should be required to provide commentary or constructive feedback as to why they are declining submissions. If the rejection is without cause, a worker could then file a complaint or flag the task or work for formal review by the platform.
  • Workers should be able to flag or block requestors and file formal complaints. Community support or account abuse teams to open investigation into offending requestors, mediate discussion, and come to a verdict about how to handle the case.
    • Example: eBay does dispute resolution between buyers and sellers. Similarly, most social media sites (e.g. Facebook, Twitter) allow for reporting of users, offensive content, spammers, or unsafe persons and/or content.
  • Companies or organizations that are submitting a large number of tasks or work to a platform could be identified with official / verified account information. A requestor tied to a company or organization should be linked/affiliated with the company or organization.
  • Workers should be able to submit suggestions/tips back to the requester about how to improve their tasks (e.g. pricing, description, quality, etc). Some consensus building (e.g. Reddit upvote) might be helpful among workers working for a shared requestor on a batch of tasks.
  • Create a pool of money (funded by a nominal surcharge on tasks) which will go to Workers who improve HIT design, answer requesters’ questions, help other workers, etc…
  • Allow workers to vote on a HIT’s design once it is posted. They will be able to vote on specific aspects of a HIT, such as its payment, its design, etc. Once a HIT has received enough down votes, it will be returned to the requester for redesigning.
    • A requester will then be able submit the task for workers to redesign it.
  • Estimated completion times for specific Workers, like Strava’s estimated race times.
    • The platform will track how long it takes a worker to complete certain tasks. After logging enough tasks, workers will be able to see estimates for each task, specific to how they work. The more tasks a worker completes, the better the estimates will be.
  • Workers can take proficiency test when joining, and have icons showing what kind of expertise they possess. They can also take certified online courses (Coursera) and apply that certification to their profile.
  • A Requester leaderboard.
  • Turn money into chips/tokens/credits so as to make it less like a payment, making Requesters spend money more freely…?
  • Paying a Worker with ‘appreciation’ = the Worker getting more money.
  • Allow Workers to bid up on HITs. If a set of tasks is priced too low for Workers, they can submit a higher bid, essentially voting up the price of the tasks. The Requester can see what the bids are and decide if she wants to pay the higher price, knowing that a number of Workers will now accept the HITs.
    • This is partially based on how I remember going about structuring their loans in the early days. Borrowers would submit an amount they needed and Lenders would bid on interest rates.
  • Allow requesters to target their workers by segment. Both parties are notified to get more accurate and streamlined tasks
  • Coding-free module-based interface

Dive Deeper into Specific Ideas

Trust-related Ideas

Power-related Ideas

Dark Horse idea

Describe your dark horse idea (using diagrams, sketches, storyboards, text, or some combination).

Please create a separate wiki page for your dark horse idea so we can link to it individually. Post the link on when done