Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

10 Lessons Oz Ia


Published on

Published in: Business, Technology

10 Lessons Oz Ia

  1. 1. Fast, cheap & somewhat in control 10 lessons from the design of SlideShare <ul><li>Rashmi Sinha </li></ul><ul><li>SlideShare & Uzanto </li></ul>
  2. 2.
  3. 3. working at a startup…
  4. 4. traditional UX methods or agile design
  5. 5. SlideShare <ul><li>launched Oct 2006 </li></ul>
  6. 6. Presentations are hard to share <ul><li>Large-scale sharing like pictures/video </li></ul><ul><li>Office 2.0? </li></ul>
  7. 8. on slideshare... <ul><li>Users drive navigation (tags, popularity) </li></ul><ul><li>Popular content floats to top </li></ul><ul><li>Slides as microcontent </li></ul><ul><li>Mash up slides with audio </li></ul>
  8. 9. What people share on SlideShare <ul><li>Venture capitalists share advise </li></ul><ul><li>Ministers share sermons </li></ul><ul><li>Teachers share lesson plans </li></ul><ul><li>Entrepreneurs share business plans </li></ul>
  9. 10. 10 Lessons from SlideShare
  10. 11. 1. The alpha as the first reaction
  11. 12. 2. The beta is the market probe <ul><li>Research is about hypotheticals, quick feedback to real thing </li></ul>
  12. 13. the risk of failure?
  13. 14. social sites as complex systems
  14. 15. How developed should the Beta be? <ul><li>Get basic concept across and no more </li></ul><ul><li>Leave room for flexibility </li></ul>
  15. 16. 3. You don’t need personas <ul><li>When you know your users by name </li></ul><ul><li>They want to visit your offices </li></ul><ul><li>They email you everyday </li></ul>
  16. 17. Get into a conversation with users <ul><li>Answer emails personally </li></ul><ul><li>Monitor blogs, subscribe to RSS </li></ul><ul><li>Customer service as user research </li></ul>
  17. 18. 4. Launch first, refine later <ul><li>Avoid analysis - paralysis </li></ul><ul><li>Look at best practices, take a guess </li></ul><ul><li>Put it out there. Respond. Refine. </li></ul>
  18. 19. 5. Just in time design <ul><li>Design – development hand in hand </li></ul><ul><li>Deliverables editable by everyone </li></ul>
  19. 20. <ul><li>Feedback email </li></ul>Personal emails Blog posts Shadow App Web analytics Phone conversations User forum Slideshows about SlideShare
  20. 21. Get yourself a shadow app <ul><li>Simpler than web analytics </li></ul><ul><li>Track crucial metrics daily </li></ul><ul><li>Measure project success, iterate </li></ul>
  21. 22. 6. designer-developer role is crucial <ul><li>Easier communication </li></ul><ul><li>Reduced design work </li></ul>
  22. 23. 7. Under invest in visual design <ul><li>users feel ownership of space </li></ul><ul><li>unpolished look is fine </li></ul>
  23. 24. 8. Pay attention to technical simplicity Complex > slower, riskier, harder to maintain
  24. 25. 9. Single biggest win: make app faster
  25. 26. 10. There is something about social websites <ul><li>Design for individual </li></ul><ul><li>Usability </li></ul><ul><li>Interaction </li></ul><ul><li>Engagement </li></ul>Design for crowds Social networks People interacting Wisdom of crowds
  26. 27. Forget the ipod!
  27. 28. Give up control This is messy!
  28. 29. Beyond hand-crafted IA
  29. 30. Plant seeds, let people connect
  30. 31. emergent architecture (or Social IA)
  31. 32. Finally...
  32. 33. sometimes process / methods become baggage when to let it go programmers are switching to agile methods when will it be time for designers?
  33. 34. Capitulate Collaborate or Initiate <ul><li>Marianne Sweeny </li></ul>
  34. 35. be experimental. create something Mashup RSS feeds (Yahoo Pipes) Build your own social network (Ning) Play with an API (Google Maps) Read Emergence , Wisdom of Crowds
  35. 36. <ul><li>Share slides at </li></ul><ul><li> </li></ul><ul><li>you can find me at </li></ul><ul><li> </li></ul>
  36. 38. Do you need traditional UX methods to design a SlideShare ?
  37. 39. YES : When feedback becomes a torrent <ul><li>Feedback form not enough. Too unstructured </li></ul><ul><li>Issues need prioritization. Diff user groups </li></ul><ul><li>Users have specific expectancies from product </li></ul><ul><li>New team members need summary info </li></ul><ul><li>Improvements beyond low hanging fruits </li></ul><ul><li>Designing completely new features </li></ul>