Interpreting Feedback

22,469 views
22,093 views

Published on

This was a presenentation I made at the Future of Web Apps conference in London. October, 2007.

Published in: Technology, News & Politics
0 Comments
28 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
22,469
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
654
Comments
0
Likes
28
Embeds 0
No embeds

No notes for slide

Interpreting Feedback

  1. 1
  2. Mozilla.org Public Site Redesign in 2004 2
  3. Mozilla.org Public Site Redesign in 2004 I don't like it a bit. What was wrong with the current one? 3
  4. Mozilla.org Public Site Redesign in 2004 I don't like it a bit. What was wrong with the current one? Looks like your average small company website. 4
  5. Mozilla.org Public Site Redesign in 2004 I don't like it a bit. What was wrong with the current one? Looks like your average small company website. Keep the old colors and ditch the new ones. It's too depressing. 5
  6. Mozilla.org Public Site Redesign in 2004 I don't like it a bit. What was wrong with the current one? Looks like your average small company website. Keep the old colors and ditch the new ones. It's too depressing. IMHO the current design looks MUCH better than this mess. 6
  7. Feedback is More than ‘Good’ or ‘Bad’ 7
  8. Digg & Pownce Established vs.Young Communities 8
  9. Pownce 3 months old (100,000+ people) Young community People feel connected to the site’s growth Positive, energetic, forgiving Nimble and responsive site 9
  10. Digg 3 years old (almost 2 million people) People have invested themselves Patterns and familiarities have formed Expectations of performance have been created 10
  11. How does feedback influence change? Before: Is the change worth it? During: Gathering feedback After: Reacting to feedback 11
  12. Example: New Digg Comments System Goals: More sophisticated threading Faster page loads More on-topic discussions 12
  13. Is the Change Worth It? Rely on previous feedback Know your community, stay in touch Anticipate areas of friction Focus groups and usability studies Decide how to measure success 13
  14. Is the Change Worth It? Rely on previous feedback Know your community, stay in touch Anticipate areas of friction Focus groups and usability studies Decide how to measure success 14
  15. Is the Change Worth It? Rely on previous feedback Know your community, stay in touch Anticipate areas of friction Focus groups and usability studies Decide how to measure success 15
  16. Is the Change Worth It? Rely on previous feedback Know your community, stay in touch Anticipate areas of friction Focus groups and usability studies Decide how to measure success 16
  17. Is the Change Worth It? Rely on previous feedback Know your community, stay in touch Anticipate areas of friction Focus groups and usability studies Decide how to measure success 17
  18. Gathering Feedback Type 1: Positive Feedback! 18
  19. Gathering Feedback Type 1: Positive Feedback! I just stumbled across your example today! Very nice! Greatly appreciated! 19
  20. Gathering Feedback Type 1: Positive Feedback! The new stuff looks great!! Now I know what you’ve been working so hard on!!! Dad 20
  21. Gathering Feedback Type 2: Bug Reports When I select a username I get a 404 error. 21
  22. Gathering Feedback Type 3: Negative Feedback I want it to be like it was before... I hate it! (the designer should be fired!!) It doesn’t do something I wanted... It’s ok, but what took so long? 22
  23. Gathering Feedback Type 4: Expert Feedback I am going to both share my opinion on what the problems are and actually _address_ them... 23
  24. Gathering Feedback Type 5: Implicit Feedback Observing user behavior Objective metrics Speaks for the silent users 24
  25. Total comments increased by over 30% Unique commenters increased by around 20% Unique comments per person increased by about 15% 25
  26. Total comments increased by over 30% Unique commenters increased by around 20% Unique comments per person increased by about 15% 26
  27. Total comments increased by over 30% Unique commenters increased by around 20% Unique comments per person increased by about 15% 27
  28. Reacting to Feedback Step 1: Don’t do anything! (...except fix bugs) Step 2: Identify themes & strong ideas Step 3: Engage your community Step 4: Iterate 28
  29. Reacting to Feedback Step 1: Don’t do anything! (...except fix bugs) Step 2: Identify themes & strong ideas Step 3: Engage your community Step 4: Iterate 29
  30. Reacting to Feedback Step 1: Don’t do anything! (...except fix bugs) Step 2: Identify themes & strong ideas Step 3: Engage your community Step 4: Iterate 30
  31. Reacting to Feedback Step 1: Don’t do anything! (...except fix bugs) Step 2: Identify themes & strong ideas Step 3: Engage your community Step 4: Iterate 31
  32. Reacting to Feedback Step 1: Don’t do anything! (...except fix bugs) Step 2: Identify themes & strong ideas Step 3: Engage your community Step 4: Iterate 32
  33. Lessons Learned Plan for a lot of feedback Anticipate negative feedback Listen to your community Make time for user testing and focus groups Don’t react immediately Make time for iteration You can’t please everyone, don’t try 33
  34. Lessons Learned Plan for a lot of feedback Anticipate negative feedback Listen to your community Make time for user testing and focus groups Don’t react immediately Make time for iteration You can’t please everyone, don’t try 34
  35. Lessons Learned Plan for a lot of feedback Anticipate negative feedback Listen to your community Make time for user testing and focus groups Don’t react immediately Make time for iteration You can’t please everyone, don’t try 35
  36. Lessons Learned Plan for a lot of feedback Anticipate negative feedback Listen to your community Make time for user testing and focus groups Don’t react immediately Make time for iteration You can’t please everyone, don’t try 36
  37. Lessons Learned Plan for a lot of feedback Anticipate negative feedback Listen to your community Make time for user testing and focus groups Don’t react immediately Make time for iteration You can’t please everyone, don’t try 37
  38. Lessons Learned Plan for a lot of feedback Anticipate negative feedback Listen to your community Make time for user testing and focus groups Don’t react immediately Make time for iteration You can’t please everyone, don’t try 38
  39. Lessons Learned Plan for a lot of feedback Anticipate negative feedback Listen to your community Make time for user testing and focus groups Don’t react immediately Make time for iteration You can’t please everyone, don’t try 39
  40. Thanks! Have any feedback or questions? Slides will be available at www.deltatangobravo.com Illustrations by Ryan Putnam (via istockphoto.com) 40

×