Milestone 6 Research Proposal
This is one of the two options for Milestone 6, which is geared towards teams which are more interested in the research side of things. If your team is more interested in contributing to the basic code infrastructure for our platform, see Milestone 6 Code Infrastructure
In this milestone, your team will propose a new crowdsourcing platform by synthesizing some foundational ideas that have been proposed over the brainstorming and prototyping stages. You will propose it by writing an introduction to a mock research paper that summarizes the main contributions of a proposed platform, and how/why you expect that it improves on the current state-of-the-art.
- 1 Determine the foundational ideas in your proposed platform
- 2 Format of your research proposal
- 3 Read introductions of some existing papers
- 4 Submitting
Determine the foundational ideas in your proposed platform
First, you should find a set of ideas from the milestones that you believe will work well together in combination as a platform. Try to primarily focus on big ideas you believe are truly revolutionary and essential underpinnings of your platform ("foundational ideas"), then to features that are great to have but are not the core of what represents the platform. Foundations should aim to solve problems of trust and power that motivated us in our needfinding. Features are ideas which improve the strength of any platform but aren’t holistic or don’t give it a high-level purpose. For example, "workers review all tasks before posting and also make all payment decisions" and "workers organize themselves into collectives" would be foundations, whereas task recommender systems, mediation strategies, and specific feedback and rating mechanisms would be features.
One way to determine what the foundational ideas of your proposed platform are, are by thinking about how you would pitch your platform. If you had to describe why your platform is better than any of the countless existing crowd marketplaces in a sentence or two, what would you say? These are your foundational ideas. If your don't think you can explain the novelty and advantages of your system in just a sentence or two, you may want to revisit the set of ideas you have picked (see the meteor links above) - perhaps you are proposing a bag of features, with less novel/foundational ideas.
As a team, choose one to two main foundations for your platform, and one to three core features that you think will be important.
You can draw the set of foundational or feature ideas for your platform by synthesizing ideas and prototypes that have been proposed in Milestones 3, 4, and 5:
For more on foundations vs. features, see this week's slides.
Format of your research proposal
You will propose your platform in the form of an introduction to a mock research paper. Essentially, imagine you have built your system, incorporating in all the ideas that you wanted to have in it, have run your user studies and evaluations, and everything has gone as planned. How do you convince other researchers that you have built a platform that is novel and that it is more effective at addressing problems than any existing ideas that have been attempted in the past?
This is an extremely effective strategy for making your ideas concrete and persuasive.
An introduction of a research paper summarizes the main contributions of the research. It is generally roughly 1 page (roughly 1000 words), and consists of the following components.
Research papers should have titles which summarize, in one line, the primary research contribution (see below).
A concise summary of the background and your research contributions (described below). Usually around 150 words or less.
Each of the following sections should be one to two paragraphs each. Paper introductions are brief and impactful.
What is the problem that you are solving, and why is it important?
- Think about the needs we synthesized from Milestone 2 - ie, trust and power - when thinking about which problems you want to solve.
- This should be a specific problem! Not just “crowdsourcing”. More like how trust and power are broken.
What are the existing attempts to solve this problem that have been attempted in prior research papers and real-world systems? Why are their solutions unsatisfactory?
- You may want to search around Google Scholar to find existing work that is related to the ideas your system proposes.
This section should lay out this the foundational idea(s). These big ideas are the things that you'll be known for, and what other platforms would want to replicate. Explain: Why/how are they novel and better than anything that has been attempted in the past?
The insight above should explain the high level idea (e.g., "All workers are paid in chocolate"). Here, you explain how it works in specifics. (e.g., "We built a crowdsourcing platform called Chococrowd that mails dark chocolate candies to workers at the conclusion of each month. Requesters choose the quality of the dark chocolate based on the quality of the work.")
Once the platform you propose has been implemented, how will you determine whether your system actually solves the problem you wanted to solve? What are the results you hope you can realistically achieve? Why do these results show that you have solved the problem?
The reference section is where you cite prior work that you build upon. If you are aware of existing related research papers, list them here. We also encourage you to borrow ideas from the past submissions (see the meteor links above). Please list the links of the ideas you used to create this proposal (there's no restriction in terms of number of ideas or whether its yours or others'). You can use the following template:
- [Foundation Idea] Link...
- [Feature Idea] Link...
- [Foundation Idea] Link...so on, and so forth...
Read introductions of some existing papers
To see concrete examples of how HCI research papers that propose new platforms are structured, you should read the introductions of these papers. You will likely be familiar with the first two papers (mClerk and MobileWorks), as they were part of the Milestone 1 readings.
Vaish R, Wyngarden K, Chen J, et al. Twitch crowdsourcing: crowd contributions in short bursts of time. Proceedings of the 32nd annual ACM conference on Human factors in computing systems. ACM, 2014: 3645-3654.
Create a Wiki Page for your Team's Submission
Please create a page for your team's submission at http://crowdresearch.stanford.edu/w/index.php?title=Milestone_6_YourTeamName&action=edit (substituting in YourTeamName with the team name), copy over the template at Milestone 6 Research Proposal Template .
We have a service on which you can post research proposals you generated, comment on them, and upvote ones you like.
Post links to your research proposals only once they're finished. Give your posts the same title as your mock research paper. Do not include words like "Milestone", "Research Proposal", or your team name in the title.
-Please submit your finished research proposals by 11:59 pm 8th April 2015, and DO NOT vote/comment until 9th April 12:05 am
[Everyone] Peer-evaluation (upvote ones you like, comment on them) from 12:05 am 9th April until 9 am 10th April
Post submission phase, you are welcome to browse through, upvote, and comment on others' research proposals. We encourage you especially to look at and comment on submissions that haven't yet gotten feedback, to make sure everybody's submissions get feedback.
Step 1: Please use http://crowdresearch.meteor.com/needcomments to find submissions that haven't yet gotten feedback, and http://crowdresearch.meteor.com/needclicks to find submissions that haven't been yet been viewed many times.
Step 2: Once you find an idea of interest or less attended, please vote and comment upon it. Please perform this action from 3 to 5 submissions - this will help us balance the comments and votes. Please do not vote your team's research proposals. Once again, everyone is supposed to vote+comment, whether you're the team leader or not.
COMMENT BEST-PRACTICES: As on Crowdgrader, everybody reviews at least 3 submissions, supported by a comment. The comment should provide constructive feedback. Negative comments are discouraged - if you disliked some aspect of a submission, make a suggestion for improvement.
[Team Leaders] Milestone 6 Submissions
To help us track all submissions and browsing through them, once you have finished your Milestone 6 Research Proposal submission, go to the link below and post the link: