Winter Milestone 3

From crowdresearch
Jump to: navigation, search

Note: The idea submissions for Milestone 2 can still be accessed

Due date (PST): 8:00 pm 31st Jan 2016 for submission, 12 pm 1st Feb 2016 for peer-evaluation.

This week, we will take the set of needs that we collectively identified in the previous milestone and use those insights to generate design ideas.

  • Youtube link of the meeting today: watch
  • Winter Meeting 3 slideshow: slides pdf

Needs from Milestone 2

We synthesized the main needs identified in Milestone 2 below:

Worker and Requester Needs

Please see this week's slides

Our synthesis

These needs boil down to two main issues: 1) task ranking and reputation, and 2) worker and requester representation (open governance).


  • How to improve reputation system beyond Boomerang? (read this paper to learn more about Boomerang).
  • How would reputation work for new comers - workers or requesters?
  • How do workers find relevant work, and requesters find ideal worker?


  • How to make your voice heard?
  • How to represent concerns/rights as workers and requesters? Who has the power to post work?
  • What would open governance look like on Daemo?

As we brainstorm, we should be thinking about solutions that holistically address these issues of reputation and open governance, not just surface fixes that get at micro-elements of the system.

Dive Deeper into Specific Ideas (Mandatory)

For the two topics - reputation and representation, pitch an idea for each, that you would like to pursue, and expand on them a bit further. In addition to describing the idea itself, make sure you also tell us:

  • What are the goals of the design? For example, Google's Android design goals are: delight me in surprising ways, simplify my life, and make me amazing (e.g., grant me special powers).
  • Which aspects of your design reflect each goal? How does your design solution address the users' needs?


For each of the 2 ideas (1 for reputation, 1 for representation), describe (using diagrams, sketches, storyboards, text, or some combination) the ideas in further detail.

Please create a separate wiki page for each of your ideas, so we can link to them individually. The title of the wiki page should be WinterMilestone 3 followed by your team name and a description of the idea itself (ex: WinterMilestone 3 YourTeamName ReputationIdea: Automatic Suggestion for Tasks based on Average Completion Time). Post a link to each of your reputation-related ideas to and a link to each of your representation-related ideas to when done.

Dark Horse idea (Mandatory)

Now that you've identified some design directions you like, it's time to change tack and toss in a dark horse idea. A dark horse, in horse racing, is a contender who most people don't think will win, but may turn in an unexpectedly strong performance and produce a huge payoff. Dark horse ideas are intended to be something far out there or nearly impossible. In the best case, your dark horse ideas might end up winning the race. However, even in the worst case, they can give us tremendous design insight and prevent design fixation, where the design space shrinks too rapidly.

There are three requirements for dark horse ideas. First, they must be "dark": they must explore a space that is risky, radical, infeasible, and/or in a direction orthogonal to previously explored solutions. They should feel slightly uncomfortable. Second, they must be brainstormed after the more traditional ideas — you can't have a dark path without a traditional "light" path to contrast it against. Third, they must be refined enough that they could be prototyped and objectively tested. That is, it cannot be infeasible: it needs to be something that we could put in front of real people to see whether it would work.

If you have dark horse ideas that came up in your initial brainstorm, you can use that. If you're not satisfied, brainstorm some! Try using Powers of Ten and other techniques to push further and generate even more. After you brainstorm and sketch out dark horse ideas, choose one that you'd like to include among your set of two top candidates from before. Expand on your dark horse idea like you did in the previous section.


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

Research Engineering (All)

Great job on the issues from last week. For those of you who have been doing tutorials and reading documentation now it's time to put that into practice. This week we will improve and finalize some of the issues we started last week, and we will also complete new ones.

- issue-forms (done), issue-profile (almost there, finalizing), issue-csv (cont'd this week) and issue-task (to be finalized)

- new issues: #645 (timer), #646 (advanced project properties), #647 (template item data_source), #648 (bug, task creation)

announce in #research-engineering that you are working on a particular issue and please let the others know about the progress of the issues you are working on (so that we don't do duplicate work). You are encouraged to work together.

For any questions ping @aginzberg, @dmorina, and @shirish.goyal on Slack #research-engineering

Usability Experience (Test Flight)

You may have played with Daemo's live version, but never got a chance to reflect on your experiences. That's your first test flight. Please login to the website, and try to work on it. Now that you have basic experience working on a crowd platform - MTurk, Microworkers etc; you may be able to add to your experience further.


Reach out to people within Crowd Research community, who are not participating in this test flight and get them to use a specific feature of Daemo and get their feedback on it. You are free to reach out to people outside Daemo too, but they must have minimal crowd platform experience and don't share it publicly. We're not ready for huge traffic at this point. Report a synthesis of your findings along with your own experience. Your report should include 1) actionable item, one that can be implemented into Daemo quickly; 2) good-to-have long term vision item, one that you'd like to see at some point of time. There is no limit to how many people you work with, it can be 1, it can be 10, it can be none (means you reflect your own findings). Note: be respectful of others time, and don't push people for it - you can always report your own experience only.

For questions/discussions, go to #usability-testflight. Your DRI for this milestone is @catherine.mullings

Recommended Readings (Optional)

Coming up with good, novel visions and ideas is a crucial part of doing successful research, and reading other researchers' visions and ideas can help you come up with better ideas yourself. These readings discuss visions that crowdsourcing researchers have thought of related to future crowd marketplaces. This week's readings are optional and don't have a deliverable, but are highly recommended.

Design notes for a future crowd work market

Design notes for a future crowd work market - This is a Medium post written by researchers involved with Turkopticon in response to hearing about this research project. It discusses their vision for a future crowd marketplace, where workers are more involved in the management of the marketplace.

The future of crowd work

Kittur A, Nickerson J V, Bernstein M, et al. The future of crowd work. Proceedings of the 2013 conference on Computer supported cooperative work. ACM, 2013: 1301-1318. - This paper envisions a future crowd marketplace that emphasizes on workers' long-term development, and where people can be proud to be workers. It is a long paper. Feel free to focus on just the parts that particularly interest you.


Create a Wiki Page for your Team's Submission

Please create 5 wiki pages for each topic - 1) reputation, 2) representation, 3) dark horse, 4) actionable and 5) long-term. See the template here for more details on "how to title and link different pages" WinterMilestone 3 Template . If you have never created a wiki page before, please see this or watch this.

[Team Representative] Submission or Post the links to your ideas until 8:00 pm 31st Jan 2016

We have a [Reddit like service] on which you can post the links to the wiki-pages for the submissions, explore them, and upvote them.

NEW INSTRUCTIONS - Create 5 wiki pages

Please use the same login avenue (Facebook, Twitter, or email address) as you’ve done in the past with Meteor​. This will help us identify and track your contributions better.

For newcomers joining Crowd Research, when it asks you to pick your username, pick the same username as your Slack.

On Meteor, there are 5 submission categories, for each, create a separate wiki page - see WinterMilestone 3 Template for tips on how to set the title of your submission:

1- [Mandatory] where you can post link to the wiki page for 1 reputation related idea you generated in the "Dive Deeper into Specific Ideas" stage

2- [Mandatory] where you can post link to the wiki page for 1 representation related idea you generated in the "Dive Deeper into Specific Ideas" stage

3- [Mandatory] where you can post a link to the wiki page for your dark horse idea

4- [Test flight] where you can post actionable ideas based on your usability study/experience.

5- [Test flight] where you can post long term ideas based on your usability study/experience.

Give your posts titles which summarize your idea. Viewers should be able to get the main point by skimming the title ("Automatic Suggestion for Tasks based on Average Completion Time" is a good title. "YourTeam TrustIdea 1" is a bad title).

-Please submit your finished ideas by 8:00 pm 31st January 2016, and DO NOT vote/comment until then

[Everyone] Peer-evaluation (upvote ones you like, comment on them) from 8:05 pm 31st Jan until 12 pm 1st Feb 2016

Post submission phase, you are welcome to browse through, upvote, and comment on others' ideas. We encourage you especially to look at and comment on ideas that haven't yet gotten feedback, to make sure everybody's ideas gets feedback.

COMMENT BEST-PRACTICES: Everybody in the team reviews at least 3 ideas, supported by a comment. The comment has to justify your reason for upvote. The comment should be constructive, and should mention positive aspect of the idea worth sharing. Negative comments are discouraged, rather make your comment in the form of a suggestion - such as, if you disliked an idea, try to suggest improvements (do not criticize an idea, no idea is bad, every idea has a scope of improvement).