You'll DESIGN, BUILD, and TEST your own crowdsourcing / social computing system.
This is a team-based, semester-long design project, in which you'll create an original social computing application on your own. You'll work in teams of four people. More information about each milestone will be added to this page. Here is the timeline and grading weights for each milestone:
Now that you've mastered the arts and skills of social computing, it's important that you apply what you learned to a problem you deeply care about. It's a great way to learn further, and potentially make impact.
We'll create an assignment in KLMS for each milestone.
For each milestone deadline, all members of your team will lose 10% for each late day. Submissions will be accepted until three days after the deadline. After then you'll get 0 on that assignment. Please note that late submissions for midterm and final presentations are not allowed.
You'll need to find teammates to work on an exciting project this semester. Each team should have 4 people by default. In exceptional cases we'll accept 3-person teams.
Here are three methods you can use:
Please fill out the design project sign-up form.
In a team, you'll identify a problem that you'd like to tackle with your project, and brainstorm approaches to solving the problem.
In your report, please answer the following questions:
One report per team. Your report should be submitted as a zip file. The main report should be written in Markdown (please use the .md extension). Storyboards should be scanned in png or jpg, and need to be in a directory called images. We're going to publish your reports on the course website. Submit your team's report on KLMS.
Now that you've identified an interesting problem, a set of concrete tasks you want to support, and a set of possible solutions, it's time to turn these into a convincing pitch!
You'll have 7 minutes to do the following:
After the pitch, you'll have 5 minutes for Q and A.
Note #1: We'll enforce a strict 7-minute time limit by cutting off the presentation. Please plan and rehearse.
Note #2: Note that all team members should present at least once between the pitch and the final presentation. This means if your team decides to have only some members present in the pitch, the remaining members should definitely present in the final presentation.
You'll present in class and submit your slides after the class, which are due 11:59pm on the day of presentation.
Your team's slides should be submitted as a PDF file, via KLMS.
Your report should include:
One report per team. Your report should be submitted as a zip file. The main report should be written in Markdown (please use the .md extension). We're going to publish your reports on the course website. Submit using KLMS.
Now's the time for a fully functional and interactive prototype that is ready to be tested by your target users. You need to build a prototype that supports end-to-end scenarios captured in your earlier prototypes. Your prototype needs to support at least three distinct tasks. This does not mean you need to build three separate prototypes, but rather this means you need to build one complete prototype that is flexible enough to support the three tasks. You may choose to reuse or revise the tasks and the UI you created in earlier stages. Make sure your tasks are centered around novel social interaction you intend to support. Other features (e.g., detailed my page design, complex login management) can be hard-coded or fed with fake data.
Your report should include:
One report per team. Your report should be submitted as a zip file. The instructions should be written in Markdown (please use the .md extension). Submit using KLMS.
Now that you have an awesome prototype that is (hopefully) getting a lot of excitement from your crowd,
it's time to tell us about what you built and what you learned from having real users use the system.
In the project showcase session, each team will give a 2-minute pitch of their project
and do a live demo + interactive Q&A in breakout rooms.
Part 1. 2-minute pitch: Decide what part of the design process you want to convey to the audience, in 2 minutes. Which part do you think is most exciting and strongest? What is your unique point of view on the problem, and what kind of social interaction does it support or enable? You won't have time to explain details, so focus on the main points and lessons. You should assume that the audience knows nothing about the problem space and your solution. Also keep in mind that we'll be listening to 10 talks non-stop in class: think how your presentation could stand out. Make sure to include a hook that will get people excited about your project. Avoid using much text and actively use visual artifacts from various stages of the design process. You are allowed to use one slide for your pitch.
NOTE: You may use animations and embedded videos in your one slide. But we won't be manually advancing them on behalf of you. This means that everything should automatically advance/play. We will start your slide and move to the slide after 2 minutes.
Part 2. Demo: After the madness presentation, we will put you into a few breakout rooms organized by theme of your interface. This means (ideally) teams that are working in similar problem areas would be put together. In this session, each team will be given 5 minutes to show a live demo of their interface to the audience followed by 5 minutes of Q&A. You can share a link to your working prototype if you want others to live test it. Your team will get 10 minutes total (shorter with a bigger session).
Note #1: We'll enforce a strict 5-minute time limit by cutting off the presentation. Please plan and rehearse.
Note #2: Note that all team members should present at least once between the pitch and the final presentation. This means if your team had only some members present for the pitch, the remaining members should definitely present for the final presentation.
Now that you have deployed your system for a couple weeks, seen your crowd use the system, and collected useful data, it's time to wrap it all up! You'll write a short report and make an engaging video that showcases your system.
Record a 2-minute video that captures the user context and the killer features of your UI. Be creative in how you plan, structure, and record the video! Check out last year's project gallery for inspiration. Revisit your storyboards, as they capture the rich usage context. You need to set the stage by starting with users and their problem. Avoid using slides and try to capture realistic context, and don't hesitate to "act". Do not show the UI from the beginning. You need to show parts of your final prototype to demonstrate how the user might perform the task using your system. Rather than describe all the features you implemented, focus on the flow of the task.NOTE: Make sure to connect the user scenario and the solution. A common antipattern is to make the UI description too generic, not about solving the particular user problem captured earlier in the video.
Here's how your report will be graded.
Part 1: Report (12% toward your project grade)
Part 2: Video (13% toward your project grade)
Up to +10% on the final milestone
We'll reward 1-2 teams with most engaging videos. We'll announce the winner(s) and explain why they deserve the "Cool Video" title.
Up to +10% on the final milestone
Teams that successfully engage active users deserve some credit! We'll reward 1-2 teams that most successfully showed the power of the crowd. This does not just mean the most number of users, but includes the overall participation, quality of data, and your analysis of the data. We'll announce the winner(s) and explain why they deserve the "Best Crowdsourcer" title.