Innovation Communities (Fall 2017)


 * Innovation Communities: How Business Can Harness the DIY Dynamic
 * COM597F - Masters of Communication in Communities and Networks (MCCN) Elective, Department of Communication
 * Instructor: Benjamin Mako Hill (University of Washington)
 * Assistent: Nate TeBlunthuis
 * Course Websites:
 * We will use Canvas for announcements, turning in assignments, and discussion
 * Everything else will be linked on this page.
 * Course Catalog Description:


 * Can innovation be crowdsourced? Equipped with a range of new digital communication technologies, “users” innovate every day — creating solutions to their own problems through sharing and collaboration. Disruptive new models of collective innovation are emerging in forums, in “free” and “open source” efforts, and in hacking initiatives. Organizations increasingly want to tap into this community-driven DIY dynamic but struggle to structure their own innovation processes in relation to these unique communities. This class will explore some of the techniques that firms can use to harness this surge of innovation by introducing a new free, democratized, and user-centric innovation paradigm. We’ll look at how online communities bolster their ability to innovate through specific technological tools and innovative social routines. Through practical examples, you will learn how to effectively use communities both as sources of inspiration and as collaborators.

Overview and Learning Objectives
I believe that in the twenty-first century innovation will be managed in dramatically different ways than it was in the previous century — by professionals like the students in in CommLead rather than by engineering managers in R&D departments.

This course will help prepare you for this future by bringing together several decades of research into the sources of innovation with practical advice and hands-on experience putting this research into action.

I will consider the course a complete success if every student is able to do each of these things at the end of the quarter:


 * Distinguish community innovation, free innovation, and user innovation from traditional forms of innovation and recognize examples in their own personal and business lives.
 * Describe techniques for finding innovations created by users including lead user search, innovation toolkits, broadcast search and crowdsourcing, and user communities and feel comfortable using each.
 * Anticipate challenges associated with community innovation and respond to these challenges effectively.
 * Have experience using at least one user innovation method to find a new innovation that solves a problem relevant to the student's employment or personal interests.

Notes About This Syllabus
You should expect this syllabus to be a dynamic document. Although I've taught this course a couple times and the core expectations for this class are fixed, the details of readings and assignments will shift based on how the class goes, guest speakers that I arrange, my own readings in this area, etc. As a result, there are three important things to keep in mind:


 * Although details on this syllabus will change, I will try my best to ensure that I never change readings more than six days before they are due. This means that if I don't fill in a "To Be Determined" one week before it's due, the item is dropped. This also means that if you plan to read more than one week ahead, you should contact me first or you'll be at risk of reading things that might not stick around on the syllabus.
 * Closely monitor your email or the announcements section on the course website on Canvas. Because this syllabus is a wiki, you will be able to track every change by clicking the history button on this page. I will summarize these changes in an announcement on Canvas once each week that will be emailed to everybody in the class. I will try to send this material the day after the class.
 * I will ask the class for voluntary anonymous feedback frequently — especially toward the beginning of the quarter. Please let me know what is working and what can be improved. In the past, I have made many adjustments to courses that I teach while the quarter progressed based on this feedback.

Organization
The course is organized into two main components:

Component 1: Community Innovation Methods

In the first half of the class (Weeks 1-5), we will focus on learning practical methods for finding innovations using communities and users. In the first session, I will make a strong case for the importance of user innovation techniques. In each of the next four weeks, we will focus on learning four practical techniques for harnessing community innovation:


 * Lead user search
 * Innovation toolkits / open source innovation
 * Broadcast search / crowdsourcing
 * Collaborative / information sharing user communities

Because I want students to start early on their projects — and because the course project will involve applying these methods — the first sessions are organized roughly from what I believe will be the least familiar to the most intuitive. They are also organized from what I think you will be most likely to use to what you will be least likely to use. During the first half of the quarter, there will be more reading and less expectation that you will be working on your course project.

Component 2: Community Innovation Applications and Challenges

In the second half of the course, we will dig deeper into examples of community innovation and focus on applications, examples, and challenges associated with their use.

During this half of the quarter, we will rely more heavily on case studies of firms putting community innovation methods into practice and focus on in-class exercises that prompt critical consideration of how community innovation takes place in different domains as well the challenges associated with using these methods (e.g., intellectual property, balancing commercial interests with community interests).

Readings


The primary book we will be using in this course is Eric von Hippel's Democratizing Innovation. Prof. von Hippel has very generously made the book available at no cost online. Physical copies of book is also available for purchase from MIT Press for $21.95 or Amazon for $16.97 and I think it is nice to support these open access efforts. Both Amazon and MIT Press also have copies of the book available for free download.

Prof. von Hippel has published a new book this year called Free Innovation which is much more focused on innovation policy than business. It is also free online and we'll be reading some of it as well.

The rest of the material will either be placed in Canvas or is available through the UW libraries. The UW libraries have put together a useful website on getting access to e-resources while off campus. If you have trouble getting any of the material, please [mailto:makohill@uw.edu email me] immediately and I will make sure you can get access.

Assignments
The assignments in this class are designed to give you an opportunity to try your hand at community innovation methods. There will be no exams, tests, or quizzes.

Unless otherwise noted, all assignments are due at the end of the day (i.e., 11:59pm on the day they are due).

Participation and Cases
The course relies heavily on participation, discussion, and the case study method. Although they are not used frequently in the Communication Leadership program, case studies are probably the most common model of teaching in business schools. A standard “case” usually involves reading around to 20-35 pages of background about an organization or group facing an ambiguous or difficult challenge. I will mark certain readings as "[Cases]" in the syllabus and I will expect you to read these particularly closely.

It is important to realize that we will not summarize case material in class and I will not cover it in lecture. I expect you all to have read it and we will jump in and start discussing it.

Cases ask students to put themselves in the positions of managers in the firms described to tease out the tensions and forces at play in the case and to construct — through group discussion — the broader lessons and takeaways. Cases are a wonderful way to connect the sometimes abstract concepts taught in many academic courses to real examples of the type of ambiguous situations that you will likely encounter in your career. Generally speaking, there are not right and wrong answers in cases.

Typically, professors teaching cases cold call on students in rooms of hundred students. Since our class will be smaller than a typical case-based class, cold calling might not be necessary very often although I will sometimes use it and you should always be ready to answer every question. I expect every student to be in class every week and to be prepared to discuss the cases and the readings. If you have not spoken all class, I may cold call on you.

The "Participation Rubric" section of my detailed page on assessment gives the rubric I will use in evaluating participation. Please read that page carefully.

Projects
There will be three assignments and each will build on the previous toward a final project. The "Writing Rubric" section of my detailed page on assessment gives the rubric I will use to evaluate these projects and your written papers.

Domain/Problem Identification

 * Maximum Length: 600 words (~2 double spaced)
 * Due Date: October 9th
 * Deliverables: Turn in on Canvas

In this assignment, you should concisely identify an problem or thematic area you are interested in — and that you hope to pursue in your final project. I am hoping that each of you will pick an area or domain that you are intellectually committed to and invested in (e.g., in your business or personal life).

You will be successful if you describe the scope of the problem and explain why you are interested in using community innovation methods to find innovations in this domain and/or solutions to your stated problem.

I will give you feedback on these write-ups and will let you each know if I think you have identified an area that might be too ambitious, too trivial, too broad, too narrow, etc.

Project Proposal

 * Maximum Length: 1500 words (~5 pages)
 * Due Date: October 30th
 * Deliverables: Turn in on Canvas

Building on your problem identification assignment, you should describe a method for finding innovations or solutions in the innovation or domain problem you have identified.

To do this effectively, you will need to have evaluated each of the four methods introduced in the first half of the quarter. That said, the primarily goal of this assignment is not to test your comprehension but to have you to tell me what you will do in your final project. You will need to understand the course material to construct a relevant and effective proposal. As long as you successfully use the course material to argue for your proposal's appropriateness, it is absolutely fine if your proposal is for a combination of, or even an elaboration or extension of, the methods we cover in the course.

A successful proposal will (a) describe clearly what you plan to do to find innovation and (b) use the course material to make an argument that your proposal is the most effective and appropriate way for you to go about finding innovation given the resources at your disposal.

I will give you feedback on these proposals and suggest changes or modifications that are more likely to make them successful or compelling and to work with you to make sure that you have the resources and support necessary to carry out your project successfully.

Final Project

 * Presentation Date: December 7th
 * Maximum presentation length: ~10 minutes (to be confirmed)
 * Presentation deliverables: Turn in slides on Canvas (details to be announced)


 * Paper Due Date: December 15th
 * Maximum paper length: 4500 words (~18 pages)
 * Paper deliverables: Turn in on Canvas

For your final project, I expect students to build on the first two assignments to describe what they have done and what they have found. I'll expect every student to give both:


 * A short presentation to the class
 * A final report that is not more than 4500 words (~18 pages)

I expect that your reports will include text from the first two assignments and reflect comprehensive documentation of your project. Each project should include: (a) the description of the problem or domain you have identified, (b) the community innovation methods you have used to find a solution and, (c) the results.

You will be evaluated on the degree to which you have demonstrated that you understand and have engaged with the course material and not on the quality of the innovations you have found. If you do not find great solutions to your problem in the communities you've identified, that's fine. Whether or not your proposal is successful, I want you to reflect on why the methods worked (or did not work) and how they might have worked better. What did you do right? What would you do differently in the future? What did the course and readings not teach that they should have?

A successful project will tell a compelling story and will engage with, and improve upon, the course material to teach an audience that includes me, your classmates, and MCCN students taking this class in future years, how to take advantage of community innovation more effectively. The very best papers will give us all a new understanding of some aspect of course materal and change the way I teach some portion of this course in the future.

Grading
I have put together a very detailed page that describes the grading rubric we will be using in this course. Please read it carefully I will assign grades for each of following items on the UW 4.0 grade scale according to the weights below:


 * Participation: 30%
 * Problem Identification: 5%
 * Project Proposal: 10%
 * Final Presentation: 15%
 * Final Paper: 40%

September 28: The User Innovation Paradigm
Resources: [Accessible through Canvas]


 * Week 1 Reading Note
 * Week 1 Slides — Introduction to User and Free Innovation
 * Week 1 Slides — General Overview

Assignment (due in class):


 * Think of an example of a user innovation that are you willing to share and discuss with the class. I'll be extra excited if you are the innovator!

Required Readings:


 * von Hippel, Eric. Democratizing Innovation. Cambridge, Massachusetts: The MIT Press, 2005.
 * Chapter 1: Introduction and Overview (pgs. 1-17)
 * Chapter 3: Why Many Users Want Custom Products (pgs. 33-44)
 * Chapter 9: Democratizing Innovation (pgs. 121-132)
 * Pisano, Gary P., and Roberto Verganti. “Which Kind of Collaboration Is Right for You.” Harvard Business Review 86, no. 12 (2008): 78–86. [Also Available through UW Libraries] (Alternate Link)
 * von Hippel, Eric. Free Innovation. Cambridge, Massachusetts: The MIT Press, 2017.
 * Chapter 3: Viability Zones for Free Innovation (pgs. 37-52)

Optional Readings:


 * Kragh, Peter, and Sandra Walder. Join the User Innovation Revolution. Users Innovate Publishing, 2012. [Available from Instructor]
 * Baldwin, Carliss, and Eric von Hippel. “Modeling a Paradigm Shift: From Producer Innovation to User and Open Collaborative Innovation.” Organization Science 22, no. 6 (December 2011): 1399 –1417. [Also Available through UW Libraries] (This is mostly the same material covered in the chapter from Free Innovation.)

October 5: Finding Innovations: Lead Users
Resources: [Accessible through Canvas]


 * Week 2 Reading Note
 * Week 2 Slides — Lead user methods

Required Readings:


 * von Hippel, Eric. Democratizing Innovation. Cambridge, Massachusetts: The MIT Press, 2005.
 * Chapter 2: Development of Products by Lead Users (pg 19-32)
 * Chapter 10: Application: Searching for Lead User Innovations (pg 133-146)
 * [Case] Thomke, Stefan and Ashok Nimgade. Innovation at 3M Corp. Harvard Business School Press, 2002. [Available in Canvas]
 * von Hippel, Eric, Stefan Thomke, and Mary Sonnack. “Creating Breakthroughs at 3M.” Harvard Business Review 77, no. 5 (September 1999): 47–57. [Also Available through UW Libraries]

Optional Readings:

Although it's long, the Project Handbook may be extremely useful for anybody who wants to use lead user methods for their class project:


 * Churchill, Joan, Eric von Hippel, and Mary Sonnack. Lead User Project Handbook: A practical guide for lead user project teams. (Selections)

Finally, this video by Eric von Hippel on lead user methods.

October 12: Finding Innovations: Toolkits
Resources: [Accessible through Canvas]


 * Week 3 Reading Note
 * Week 3 Slides — Innovation toolkits

Required Readings:


 * von Hippel, Eric. Democratizing Innovation. Cambridge, Massachusetts: The MIT Press, 2005.
 * Chapter 5: Users’ Low-Cost Innovation Niches (pg 63-76)
 * Chapter 11: Application: Toolkits for User Innovation and Custom Design (pg 147-164)
 * Hinkle, Mark. “Open Source: A Platform for Innovation | Innovation Insights.” Wired: Innovation Insights, November 13, 2013. (Moved!)
 * Raymond, Eric S. The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary. Edited by Tim O’Reilly. Sebastopol, CA: O’Reilly and Associates, 1999. (Moved!)
 * [Case] “Living a Second Life.” The Economist, September 28, 2006.
 * [Case] Kohler, Thomas, Kurt Matzler, and Johann Füller. “Avatar-Based Innovation: Using Virtual Worlds for Real-World Innovation.” Technovation 29, no. 6–7 (June 2009): 395–407. [Available through UW Libraries]

Optional Readings:


 * Thomke, Stefan, and Eric von Hippel. “Customers as Innovators: A New Way to Create Value.” Harvard Business Review 80, no. 4 (April 2002): 74–81. [Available through UW Libraries] (Alternate Link)
 * von Hippel, Eric. “‘Sticky Information’ and the Locus of Problem Solving: Implications for Innovation.” Management Science 40, no. 4 (April 1994): 429–439. [Available through UW Libraries] (Alternate Link)
 * von Hippel, Eric. “Perspective: User Toolkits for Innovation.” Journal of Product Innovation Management 18, no. 4 (July 2001): 247–57. [Available through UW Libraries]
 * von Hippel, Eric, and Ralph Katz. “Shifting Innovation to Users via Toolkits.” Management Science 48, no. 7 (July 2002): 821–33. [Available through UW Libraries]

October 19: Finding Innovations: Broadcast Search and Contests
Resources: [Accessible through Canvas]


 * Week 4 Reading Notes
 * Week 4 Slides — Broadcast Search

Required Readings:


 * Howe, Jeff. “The Rise of Crowdsourcing.” Wired Magazine 14, no. 6 (2006): 1–4. [Free Online]
 * [Case] Lakhani, Karim R., InnoCentive.com (A). Harvard Business School Press, 2009. [Available in Canvas]
 * Boudreau, Kevin J., Nicola Lacetera, and Karim R. Lakhani. “Incentives and Problem Uncertainty in Innovation Contests: An Empirical Analysis.” Management Science 57, no. 5 (May 2011): 843–863. [Available through UW Libraries]
 * Wright, Randall S. “Thinking of Running an Open Innovation Contest? Think Again.” MIT Technology Review, June 5, 2013.
 * Boudreau, Kevin J., and Karim R. Lakhani. “How to Manage Outside Innovation.” MIT Sloan Management Review, July 1, 2009. [Available through UW Libraries] [Alternative Link in Canvas]

Optional Reading:


 * Crowdsourcing. Cambridge, Massachusetts ; London, England: The MIT Press, 2013. (Amazon Link) [Available from Instructor]

October 26: Finding Innovations: Collaborative Communities
Resources: [Accessible through Canvas]


 * Week 5 Reading Notes
 * Week 5 Slides — Collaborative Communities Intro
 * Week 5 Slides — Attracting Contributors

Required Reading:


 * von Hippel, Eric. Democratizing Innovation. Cambridge, Massachusetts: The MIT Press, 2005.
 * Chapter 7: Innovation Communities (pg 93-106)
 * [Case] Rao, Hayagreeva, Robert I. Sutton, David W. Hoyt. Mozilla: Scaling Through a Community of Volunteers. Stanford Graduate School of Business, 2009. [Available in Canvas]
 * Hill, Benjamin Mako. Almost Wikipedia. [Free Online]
 * Murray, Fiona, and Siobhan O’Mahony. “Exploring the Foundations of Cumulative Innovation: Implications for Organization Science.” Organization Science 18, no. 6 (November 1, 2007): 1006–1021. [Available through UW Libraries]

Also, make sure you're ready to discuss the two pieces we read on free and open source software we read two weeks ago but didn't get to in class:


 * Hinkle, Mark. “Open Source: A Platform for Innovation | Innovation Insights.” Wired: Innovation Insights, November 13, 2013.
 * Raymond, Eric S. The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary. Edited by Tim O’Reilly. Sebastopol, CA: O’Reilly and Associates, 1999.

November 2: Applications: Hackers and the Innovation Underground
Resources: [Accessible through Canvas]

Required Readings:
 * Week 6 Reading Notes
 * Week 6 Slides — Hacking Cameras with CHDK


 * Mollick, Ethan. “Tapping into the Underground.” MIT Sloan Management Review 46, no. 4 (2005): 21. [Alternative link in Canvas]
 * Rosenbaum, Ron. “Secrets of the Little Blue Box.” Esquire Magazine, 1971, 116.
 * [Case] Viard, V. Brian, and Pamela Yatsko. Blizzard v. bnetd.org: Managing Intellectual Property (A). Stanford Graduate School of Business, 2006. [Available in Canvas]
 * Wayner, Peter. “Tweaking a Camera to Suit a Hobby.” The New York Times, May 26, 2010, sec. Technology / Personal Tech.

Optional Reading:


 * Mollick, Ethan. “The Engine of the Underground: The Elite-Kiddie Divide.” SIGGROUP Bull. 25, no. 2 (2005): 23–27. [Available through UW libraries]
 * Scacchi, Walt. “Computer Game Mods, Modders, Modding, and the Mod Scene.” First Monday 15, no. 5 (2010). [Free Online]

November 9: Applications: Creative Collaboration
Resources:


 * Week 7 Reading Notes

Guest Lecture (Planned):


 * Andrés Monroy-Hernández who is the director of Snap Research's Seattle based research lab will attend to talk with us about creative collaboration. Andrés is a technologist and researcher in social computing and civic media and an expert in remixing. He has a PhD from the MIT Media Lab.

Alternate Guest Lecture:

Because Andrés was sick and had to cancel, we filled in with a talk by Mako about research into Scratch and with a talk by Sayamindu Dasgupta. Sayamindu is a Moore/Sloan & WRF Innovation in Data Science Postdoctoral Fellow here at UW.

Slides for the three presentations are here:


 * Mako's presentation on Remixing in Scratch
 * Sayamindu's presentation on Remixing As a Pathway to Computational Thinking
 * Sayamindu's presentation on Scratch Community Blocks

The four projects that Mako talked about in his presentation are here:


 * Hill, Benjamin Mako, and Andrés Monroy-Hernández. 2013. “The Remixing Dilemma: The Trade-Off Between Generativity and Originality.” American Behavioral Scientist 57 (5): 643–63. [Available through UW Libraries]
 * Hill, Benjamin Mako, and Andrés Monroy-Hernández. 2013. “The Cost of Collaboration for Code and Art: Evidence from a Remixing Community.” In Proceedings of the 2013 Conference on Computer Supported Cooperative Work (CSCW ’13), 1035–1046. New York, New York: ACM. [Available through UW Libraries]
 * Hill, Benjamin Mako, Andrés Monroy-Hernández, and Kristina Olson. 2010. “Responses to Remixing on a Social Media Sharing Website.” In Proceedings of the 4th AAAI Conference on Weblogs and Social Media (ICWSM ’10), 74–81. Palo Alto, California: AAAI Press. [Available through UW Libraries]
 * Monroy-Hernández, Andrés, Benjamin Mako Hill, Jazmin Gonzalez-Rivero, and danah boyd. 2011. “Computers Can’t Give Credit: How Automatic Attribution Falls Short in an Online Remixing Community.” In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI ’11), 3421–3430. New York, New York: ACM Press. [Available through UW Libraries]

The two projects that Sayamindu presented about are available online here:


 * Dasgupta, Sayamindu, and Benjamin Mako Hill. 2017. “Scratch Community Blocks: Supporting Children As Data Scientists.” In Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems (CHI ’17), 3620–3631. New York, New York: ACM Press. [Available Free Online]
 * Dasgupta, Sayamindu, William Hale, Andrés Monroy-Hernández, and Benjamin Mako Hill. 2016. “Remixing As a Pathway to Computational Thinking.” In Proceedings of the 19th ACM Conference on Computer-Supported Cooperative Work & Social Computing (CSCW ’16), 1438–1449. New York, New York: ACM. [Available Free Online]

Required Readings:


 * Lessig, Lawrence. Remix: Making Art and Commerce Thrive in the Hybrid Economy. Penguin Press HC, 2008. (Introduction) [Available Free Online]
 * [Skim] Agapie, Elena, Jaime Teevan, and Andrés Monroy-Hernández. 2015. “Crowdsourcing in the Field: A Case Study Using Local Crowds for Event Reporting.” In Proceedings of the Third AAAI Conference on Human Computation and Crowdsourcing. Palo Alto, California: AAAI. [Available through UW Libraries]
 * [Skim] Cranshaw, Justin, Andrés Monroy-Hernández, and S.A. Needham. 2016. “Journeys & Notes: Designing Social Computing for Non-Places.” In Proceedings of the 2016 CHI Conference on Human Factors in Computing Systems, 4722–4733. CHI ’16. New York, New York: ACM. [Available through UW Libraries]
 * [Video Case] Lakhani, Karim R., and Zahra Kanji. Threadless: The Business of Community. Harvard Business School Press, 2008. [See link in Week 7 Announcement in Canvas.]

Optional Readings:


 * Sinnreich, Aram. Mashed Up: Music, Technology, and the Rise of Configurable Culture. University of Massachusetts Press, 2010. [Available from Instructor]
 * Vaidhyanathan, Siva. Copyrights and Copywrongs: The Rise of Intellectual Property and How It Threatens Creativity. New York: New York University Press, 2001. [Available from Instructor]
 * Hill, Benjamin Mako, and Andrés Monroy-Hernández. “The Remixing Dilemma The Trade-Off Between Generativity and Originality.” American Behavioral Scientist 57, no. 5 (May 1, 2013): 643–663. [Available through UW Libraries]

November 16: Applications: Ecological Perspectives
Required Readings:


 * Hoff, Lynn. Introduction to Organizational Ecology. A short Youtube video that explains the basics of organizational ecology.
 * George, Cherian. The Rise of the Mighty Microbrew, Stanford Graduate School Insights. 2002
 * Meyer, Marc H.and Seliger, Robert. Product Platforms in Software Development, MIT Sloan Management Review, 1998

Our case will about a website called Area 51 on a platform called Stack Exchange. There's nothing to read but I want you to spend an at least 45 minutes reading about the site and exploring things:


 * [Case] Stack Exchange article on Wikipedia and list of sites
 * [Case] Area 51 (Click through and explore 5-6 proposals at different stages)
 * [Case] Area 51 FAQ

Optional Reading:


 * Zhu, Haiyi, Jilin Chen, Tara Matthews, Aditya Pal, Hernan Badenes, and Robert E. Kraut. 2014. “Selecting an Effective Niche: An Ecological View of the Success of Online Communities.” In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI ’14), 301–310. New York, New York: ACM.
 * TeBlunthuis, Nathan Shaw, Aaron Hill, Benjamin Mako. 2017. Density dependence without resource partitioning on an online petitioning platform. Working Paper.

November 30: Applications: Human Computation
The class will focus on issues in crowdsourcing and human computation. Our discussion will emphasize Amazon's Mechanical Turk Marketplace and Zooniverse.

Guest Lecture:


 * We'll have a guest lecture from Justin Cranshaw at Microsoft Research. He's a researchers at FUSE Labs at Microsoft Research focusing on social computing and human-computer interaction. He's going to talk about a system he built called calendar.help which is a system that brings together humans and algorithms in a novel way.

Required Readings:


 * Amazon Mechanical Turk Requester UI Guide [Skim, but make sure you're ready to submit tasks.]
 * Amazon Mechanical Turk Best Practices Guide. [Skim, but make sure you're ready to submit tasks.]
 * Shaw, A. (2015). Hired Hands and Dubious Guesses: Adventures in Crowdsourced Data Collection. In E. Hargittai & C. Sandvig (Eds.), Digital Research Confidential: The Secrets of Studying Behavior Online. The MIT Press. [To Be Provided]
 * von Ahn, Luis. Massive Scale Human Collaboration (TedX video lecture).
 * Chris Lintott's TEDxCERN talk on How to discover a planet from your sofa. 2013.
 * Cranshaw, Justin, Emad Elwany, Todd Newman, Rafal Kocielnik, Bowen Yu, Sandeep Soni, Jaime Teevan, and Andrés Monroy-Hernández. 2017. “Calendar.Help: Designing a Workflow-Based Scheduling Agent with Humans in the Loop.” In Proceedings of the 2017 CHI Conference on Human Factors in Computing Systems, 2382–2393. CHI ’17. New York, NY, USA: ACM. [Available through UW libraries]

Assignment before class:


 * mTurk - Find and complete at least 2 "hits" as a worker on Amazon Mechnical Turk. Note that to do this you will need to create a worker account on Mturk.
 * Record (write down) details and notes about your tasks: What did you do? Who was the requester? What could you was the purpose of the task (as best you could tell)? What was the experience like? What research applications can you (not) imagine for this kind of system?
 * If you're not a US citizen, creating an requester account is much more complicated because it involves getting paid and ensuring that you have authorization to work. Please just skip this part.
 * mTurk Create a "requester" account. Doing so may require up top 48 hours to be approved so please do that immediately so you have it ready to go in class.
 * Zooniverse - Complete at least 1-2 tasks in two different projects of your choice on Zooniverse. Come to class ready to talk about it.

In class exercise:


 * Design and deploy a small-scale research task on Mturk. Note that to do this, you will need to create a requester account on Mturk. Be sure to allow some time to get the task design the way you want it! Some ideas for study designs you might do:
 * A small survey.
 * Classification of texts or images (e.g., label tweets, pictures, or comments from a discussion thread).
 * A small experiment (e.g., you can do a survey where you insert different images and ask the same set of questions. Check out the Mturk requester getting started guide
 * Prepare to share details of your small-scale research task in class, including results (they will come fast).

Note: In terms of running your task, it will cost real money and you have to put money on your Amazon account yourself. You've each got a $3 budget. Please use your credit card to put $3 on your account right away. I will pay each of you $3 in cash next week to reimburse you for the cost of running the experiment.

December 7: Final Presentations
Note: The final session will be devoted to final presentations.

Optional Readings:


 * Morison, Elting. “[Gunfire at Sea: A Case Study of Innovation.” Men, Machines, and Modern Times, 1966, 17–44.

Practices and Policies
Most of the rest of the material in the syllabus will be familiar to students who have taken other Communication Leadership classes. That said, most of this material is important enough that it warrants looking at again.

Attendance
As detailed in my page on assessment, attendance in class is expected of all participants. If you need to miss class for any reason, please contact a member of the teaching team ahead of time (email is best). Multiple unexplained absences will likely result in a lower grade or (in extreme circumstances) a failing grade. In the event of an absence, you are responsible for obtaining class notes, handouts, assignments, etc.

Office Hours
Normally, I do not hold regular office hours. In general, I will be available to meet before and after class and at other times that are convenient for you. Please contact me on email to arrange a meeting then or at another time.

Disability Accommodations Statement
To request academic accommodations due to a disability please contact Disability Resources for Students, 448 Schmitz, 206-543-8924/V, 206-5430-8925/TTY. If you have a letter from Disability Resources for Students indicating that you have a disability that requires academic accommodations, please present the letter to me so we can discuss the accommodations that you might need for the class. I am happy to work with you to maximize your learning experience.

Comm Lead Electronic Mail Standards of Conduct
Email communications (and all communications generally) among Comm Lead community members should seek to respect the rights and privileges of all members of the academic community. This includes not interfering with university functions or endangering the health, welfare, or safety of other persons. With this in mind, in addition to the University of Washington's Student Conduct Code, Comm Lead establishes the following standards of conduct in respect to electronic communications among students and faculty:
 * If, as a student, you have a question about course content or procedures, please use the online discussion board designed for this purpose. If you have specific questions about your performance, contact me directly.
 * I strive to respond to Email communications within 48 hours. If you do not hear from me, please come to my office hours, call me, or send me a reminder Email.
 * Email communications should be limited to occasional messages necessary to the specific educational experience at hand.
 * Email communications should not include any CC-ing of anyone not directly involved in the specific educational experience at hand.
 * Email communications should not include any blind-CC-ing to third parties, regardless of the third party’s relevance to the matter at hand.

Grading
Grades in this class are based on a rating scale: Rating-scale grades are based on the faculty member's assessment of each assignment as opposed to a calculation from earned and possible points. The broad criteria for the ratings are given below. The ratings for some assignments may be multiplied by a constant (e.g. 2 or 3) so as to count more toward the final grade. The final grade is calculated as the average of all ratings.
 * 4.0 - 3.9: Excellent and exceptional work for a graduate student. Work at this level is extraordinarily thorough, well reasoned, methodologically sophisticated, and well written. Work is of good professional quality, shows an incisive understanding of digital media-related issues and demonstrates clear recognition of appropriate analytical approaches to digital media challenges and opportunities. Clients who received a deliverable of this quality would likely develop loyalty toward the vendor to the exclusion of other vendors.
 * 3.8 - 3.7: Strong work for a graduate student. Work at this level shows some signs of creativity, is thorough and well-reasoned, indicates strong understanding of appropriate methodological or analytical approaches, and demonstrates clear recognition and good understanding of salient digital media-related challenges and opportunities. Clients who received a deliverable of this quality would likely recommend this vendor to others and consider a longer-term engagement.
 * 3.6 - 3.5: Competent and sound work for a graduate student; well reasoned and thorough, methodologically sound, but not especially creative or insightful or technically sophisticated; shows adequate understanding of digital media-related challenges and opportunities, although that understanding may be somewhat incomplete. This is the graduate student grade that indicates neither unusual strength nor exceptional weakness. Clients who received a deliverable of this quality would likely agree to repeat business with this vendor.
 * 3.3 - 3.4: Adequate work for a graduate student even though some weaknesses are evident. Moderately thorough and well reasoned, but some indication that understanding of the important issues is less than complete and perhaps inadequate in other respects as well. Methodological or analytical approaches used are generally adequate but have one or more weaknesses or limitations. Clients who received a deliverable of this quality would likely entertain competitor vendors.
 * 3.0 - 3.2: Fair work for a graduate student; meets the minimal expectations for a graduate student in the course; understanding of salient issues is incomplete, methodological or analytical work performed in the course is minimally adequate. Overall performance, if consistent in graduate courses, would be in jeopardy of sustaining graduate status in "good standing." Clients who received a deliverable of this quality would likely pay the vendor in full but not seek further engagement.
 * 2.7 - 2.9: Borderline work for a graduate student; barely meets the minimal expectations for a graduate student in the course. Work is inadequately developed, important issues are misunderstood, and in many cases assignments are late or incomplete. This is the minimum grade needed to pass the course. Clients who received a deliverable of this quality would likely delay payment until one or more criteria were met.

Academic Misconduct
Comm Lead is committed to upholding the academic standards of the University of Washington’s Student Conduct Code. If I suspect a student violation of that code, I will first engage in a conversation with that student about my concerns. If we cannot successfully resolve a suspected case of academic misconduct through our conversations, I will refer the situation to the Anita Verna Crofts, Comm Lead Associate Director of Academic Affairs. The Comm Lead Associate Director of Academic Affairs, in consultation with the Comm Lead Director, can then work with the COM Chair to seek further input and if necessary, move the case up to the Dean. While evidence of academic misconduct may result in a lower grade, Comm Lead faculty (indeed, all UW faculty) may not unilaterally lower a grade without taking the necessary steps outlined above.

Overview
In closing, Comm Lead students are expected to:


 * Write coherently and clearly.
 * Complete assignments on time and as directed.
 * Not miss more than two classes a quarter, unless due to extreme circumstances.
 * Engage as much as possible with colleagues and the instructor.
 * Stay current with the latest developments in the field of communications and digital media.