Crowds and Creativity

2,921 views

Published on

Here is a talk from Mike Krieger of the Stanford HCI Group that he gave at an Adobe Plerk Workshop. HCI being Human Computer Interaction. It examines how people react when you task them with creativity for crowd solutions.

Published in: Technology, Education
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,921
On SlideShare
0
From Embeds
0
Number of Embeds
1,307
Actions
Shares
0
Downloads
51
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Crowds and Creativity

  1. 1. Crowds & Creativity Mike Krieger Stanford HCI Group Adobe Plerk Workshop
  2. 2. Big PictureHow can we tap intothe creative potentialof online crowds?
  3. 3. Big Picture Outline 1. C urrent projectsHow can we tap into 2. When do crowdsthe creative potential ma ke sense for aof online crowds? project? 3. How can we design for better collaboration & creativity? (4 principles)
  4. 4. Wisdom of ...or tyrannythe crowd... of the m asses?
  5. 5. Positive traitsdiversity ofbackground,expertise, thoughts,ideaspower in numbers“collectiveintelligence”validation &feedback
  6. 6. SuccessfulProjects
  7. 7. Evaluating Scenarios 6
  8. 8. Evaluating Scenarios 6
  9. 9. Evaluating Scenarios 6
  10. 10. 7
  11. 11. 7
  12. 12. 7
  13. 13. “Persona lly I think the Reactions idea fr om storyboard g. one is m ore compellin“Personally I prefer the idea The re ason for this isof storyboard one. This is that I would be ding outbecause the user freely in terested in fin ationwalks around the museum as inte resting inform workthey would traditionally, yet about a piece of art atautomatically receive info or a par ticular artist thabout exhibits - a virtual I couldnt just get at theguide without user input. museum . The map ofMuch more impressive.” th e museum is an get som ething that I c at the museum on a pie ce of paper that to be does nt require me pulling out my phone and wast ing the battery to get t o an exhibit.”
  14. 14. !"#$%&!()*+,-*#+.(&/.! (;<15=45>19012234556718499:18;<15=45>19
  15. 15. *>43?2@A=4>1489@53@B3@;5@A2CD471B;2E
  16. 16. -6FF68A4F>62GH@A24I;83895119?F621HA69:8:@<8?51894;5429842H9:1F6>1C
  17. 17. D68B5612H%:6F68629:1J@K118:@<514H62G9:121A8<4<15C
  18. 18. Phil’s in the Coffee Shop!-6FFL8<:@214F1598:6=9:49:68B5612H682145I3:4762G4J@K11C
  19. 19. Hi Phil!-6FFH1J6H189@H5@<6242H:4714J@K11A69:%:6FC
  20. 20. ! Price Latte#8:11291589:18:@<?:68<:@214F1598:6=9@9:1H43L88<1J64F@K158C
  21. 21. Why sucessful?fun activitieshidden ambitionssmall, parallelizedtasksencouragingexperimentation &iterationright representation
  22. 22. Not-so-successfulones
  23. 23. Why notsucessful?lack of conceptualintegritylack of constructivebehaviorasking too much, orin the wrong way
  24. 24. 9 guidelines1. When diversity 6. Lea rn from hacks, matters mods, re-use from crowd2. Small chunks/ delegate-able 7. Enable novel actions knowledge discovery3. Easy verification 8. Maintain vision &4. Fun activity, or design consistency hidden ambition 9 . Not just about5. Better than lowering costs computers at performing a task
  25. 25. Designingfor crowdcreativityto let them runwild, you needcareful design &constraints
  26. 26. Project:CrowdBrai nstorming
  27. 27. Inbrainstorming,constructive “yes,ideation is and...”critical
  28. 28. Currentsystems looklike Digg...
  29. 29. Currentsystems looklike Digg...
  30. 30. S o folks actlike they’re onDigg(no constructiveideation)
  31. 31. Our project:Ideas2Ideas
  32. 32. Our project:Ideas2Ideas
  33. 33. Our project: Ideas2Ideas Dell IdeaStorm Clone Non-building ideas 35 52Ideas2Ideas Constructive ideas 43 25 !2 test of independence = 10.8776, p < 0.001
  34. 34. 2 designprinciples1. the value ofdesigning forconstructiveideation2. reducingstaleness byvisualizing “longtail” of crowdcontributions
  35. 35. Project 2Not just buildingoff ideas, butothers’ work aswell
  36. 36. Project 2Not just buildingoff ideas, butothers’ work aswell Wi kiTasks
  37. 37. QuestionHow does theWikipedia crowdof editorsorganize theiractions (to-dos),on a personaland site-widelevel?
  38. 38. Insights1. Bottom-up 4 . Disconnectstructure between ind ividual & site-2. Existing system wide goalsdoesn’t encourage“next action” thinking 5. La ck of support for contextual3. Lack of triage discovery
  39. 39. WikiTasksPrototype
  40. 40. WikiTasksPrototype
  41. 41. FindingsLowers barriers toparticipationEncouragescollaborative task-making70% of completedactions originatedfrom someone else
  42. 42. designprinciples1. Contextual display 2. Sliding scale ofof task and work part icipation andinformation alongside bottom-upcrowd’s work creation
  43. 43. wrapping it up1. strong potential forcreative crowds2. but need toconsider rightapplications forcrowds3. and keep designprinciples in mindwhen building“crowd-powered”sites
  44. 44. thanks! Scott Klemmer & Joel Brandt for guidance and feedbackmkrieger@hci.stanford.edu C ollaborators & Wikipedia participants Eve ryone here for participating

×