Daemo: A well orchestrated democracy

From crowdresearch
Jump to: navigation, search

Introduction

Daemo, as a crowdresearch platform, has the ability to influence the future of open government within marketplaces. To aid this effort, team Veloce presents improved open government with 4 key features: guilds and union pages, a poll-based feedback system, and a system of trends.

Guild and Union Pages

In the brainstorming process, many teams ideated upon a guild system within Daemo that would help bind workers in a particular skill together. But, this created a big question: Guilds are normally made up of skilled workers of a specific trade, and are thought of exhibiting a high quality...so how should we better accommodate a sense of community between all workers on the platform? That's why we came up with two separate methods of worker grouping, guilds and unions.

Guilds should be places where workers that exhibit high work quality in a specific area are bound together by the platform based on their performance on tasks and their skills. Also, their reputation would have to be monitored/analyzed by some reputable people, at the very beginning, when guilds are first being created/built up (i.e., the creators of Daemo, or other well known crowdworkers we could source from AMT)


Unions exist for each field, and all workers should be allowed to join them the minute they join Daemo and start doing tasks in certain areas

To better organize guilds and unions, each guild and union will have their own page, where both workers and requesters can write posts. This would lead to a greater sense of community on the marketplace, and help break down the invisible barrier that exists on most crowdsourcing sites between workers and requesters, hopefully leading to longer relationships between workers and requesters, and greater retention. This should also lead to greater workers enrichment, as workers will finally have a place to be able to discuss ways to get better at certain tasks, and progress in a certain field.

Here is what the worker's dashboard for guild and union pages:

Ssgov1.png

Each page would appear as a card within a guild or union card, with the latest post and its creator displayed. In this particular instance, the worker is not eligible to join a guild, and will be added to one once they reach a certain number of tasks completed with a base quality level.

This is what that union page would look like with posts selected:

Ssgov2.png

It's pretty similar to any other social network. The only difference here is that workers' names will be written in black, while requesters names will be written in the purple color used in the navigation bar. As you can see, the posts here were all written by a worker.

Poll-based Feedback

There should be two types of requests that workers can make to openly govern what happens on the platform, requests to the platform and requests to the requester. These would both work by using peer feedback. For example, if you wanted to change something with a requester, you, as a worker, would place a poll on your union page, and at least two guild members and 5 union members from the same industry would have to also upvote the request before it appears on the requester’s dashboard as something the requester must solve before posting or viewing tasks. If you wanted to change something to the platform, your poll would appear on each of the union’s pages, and would have to be upvoted by at least 4 guild members, with at least 2 being from a different field, and 12 union members before it is passed to the platform engineers for a decision on the change.

Request to Requester Use Case

Here I am, as a new worker. I’ve done some pretty good work and lately and have been fortunate enough to be able to join a guild related to design work. I’m currently working on a task for a requester and realized that they threw a bunch of tasks together and bunched them up into one long video and would prefer that they split the video up into multiple videos, each one representing a task, so I create a poll and have it voted on/reviewed by guild and union members. I list the poll with the title “Split Single Video Explaining Tasks into Smaller Individual Tasks”, and it appear's on my guild's page in a similar card style as the posts with the polls button toggling if polls should appear on the screen, and I just so happen to get enough votes and the issue gets sent to the requester. The requester must either follow the suggestion or post to the guild with reasons why the change was not implemented to be able to access their tasks at log in.

Request to Platform Use Case

Again, here I am as a worker, now with a good reputation and membership in a guild. I’ve realized there is some sort with the poll system and that it’s missing the ability to add custom tags (that describe the type of issue I want to create) and so I create a poll with the explanation of how it would be more beneficial to the workers if we could create custom tags. People vote and it ends up getting sent to the platform engineers, who have to either follow the suggestion or post to the guilds or unions involved with an explanation for why the change was not made.

Trends

The guild and union pages can provide both workers and requesters with information they can use to improve their work or the way they assign and handle tasks, respectively. This would appear on their profile page as a notification.

For workers', the trends in requester needs for industries they have worked in will appear. This could be rates, types of tasks, and ways to be a better worker.

For requesters, the trends in worker's needs for industries they frequently post tasks for will appear. This could be most favored types of tasks, most favorable pay, and ways to be a more effective manager.

Trends would work by taking the most upvoted posts and polls for a given industry, and turning them into vectors, much like the process employed in Googles' Word2Vec(https://code.google.com/archive/p/word2vec/). These vectors would then be compared to find trends with an r-value closes to 1. The magnitude of the resulting trend vector will then be turned into words again, and appear on the worker's and requester's screens. Additionally, this trend vector could be compared against Google Books' API(https://developers.google.com/books/) and tweets from Twitter's Search API(https://dev.twitter.com/rest/public/search) to display actual literature that the worker and requester could read improve themselves. This would lead to more awareness between workers and requesters, leading to better quality, greater work acceptance by a requester, and less worker complaints.

Contributors

Samarth Sandeep - @samarthsandeep

Freddie Vargus - @freddievargus