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.
Fast, cheap and somewhat in control 10 Lessons from the design of SlideShare <ul><li>Rashmi Sinha </li></ul>
First  <ul><li>www.slideshare.net </li></ul><ul><li>www.themindcanvas.com </li></ul>
 
Designing SlideShare
1. Documents are hard to share  <ul><li>What would large-scaling sharing look like? </li></ul><ul><li>Is office 2.0 just e...
2. A simple sharing website  <ul><li>A space, not a utility </li></ul><ul><li>For sharing and connecting </li></ul><ul><li...
First generation Social Networks (Friendster, LinkedIn…) 1) I am linked to -> -> to you  --->You are linked to her -> --->...
Second generation social network  (networks with objects in between, e.g., Flickr, Yahoo answers) 1) I share my pics ->   ...
Viral sharing  (passing on interesting stuff, e.g., YouTube videos) <ul><li>How it works </li></ul><ul><li>Individual to i...
3.   good content  floats to the  top   <ul><li>Multiple models of popularity </li></ul><ul><li>Users drive navigation </l...
4. Slides as   MICROCONTENT <ul><li>URL for every slide </li></ul><ul><li>Comment on individual slides </li></ul>
5. What  people share  on SlideShare <ul><li>Ministers  share  sermons </li></ul><ul><li>Teachers  share  lesson plans </l...
10 Lessons
1. The  beta  is the  market probe  <ul><li>User research is hypothetical </li></ul><ul><li>Get feedback to the real thing...
How  developed  should the  Beta  be?   <ul><li>Get basic concept across and no more </li></ul><ul><li>Leave room for flex...
2. You don’t need personas <ul><li>When you know your users by name </li></ul><ul><li>They want to visit your offices  </l...
3. Get into a  conversation  with  users  <ul><li>Answer emails personally </li></ul><ul><li>Monitor blogs, subscribe to R...
4. Get yourself a  shadow app  <ul><li>Keep a pulse on main metrics </li></ul><ul><li>Experiments without A-B setup </li><...
When  feedback  becomes a  torrent <ul><li>Feedback form not enough. Too unstructured  </li></ul><ul><li>Issues need prior...
5. Launch  first,  refine  later <ul><li>UX folks can over analyze </li></ul><ul><li>Look at examples, take a guess </li><...
6.  designer-developer  role is crucial <ul><li>Easier communication </li></ul><ul><li>Reduced design work </li></ul>
7. Under invest in  visual design <ul><li>Let users feel ownership of space </li></ul><ul><li>Unpolished look is fine </li...
8. Pay attention to  technical simplicity Balance user needs & technical simplicity Complexity > slower, riskier, harder t...
9.  Help users kick ass Everything else is secondary No step by step ROI calculations Have sound business model, but don’t...
10. Single biggest win:  make app faster
Finally  <ul><li>www.slideshare.net/rashmi </li></ul>
Upcoming SlideShare
Loading in …5
×

Fast cheap and somewhat in control: 10 lessons from the design of SlideShare

3,297 views

Published on

Published in: Technology, Education
  • Be the first to comment

Fast cheap and somewhat in control: 10 lessons from the design of SlideShare

  1. 1. Fast, cheap and somewhat in control 10 Lessons from the design of SlideShare <ul><li>Rashmi Sinha </li></ul>
  2. 2. First <ul><li>www.slideshare.net </li></ul><ul><li>www.themindcanvas.com </li></ul>
  3. 4. Designing SlideShare
  4. 5. 1. Documents are hard to share <ul><li>What would large-scaling sharing look like? </li></ul><ul><li>Is office 2.0 just editing & collaboration? </li></ul><ul><li>A social critique of PowerPoint </li></ul>
  5. 6. 2. A simple sharing website <ul><li>A space, not a utility </li></ul><ul><li>For sharing and connecting </li></ul><ul><li>Sharing and finding both user driven </li></ul>
  6. 7. First generation Social Networks (Friendster, LinkedIn…) 1) I am linked to -> -> to you --->You are linked to her -> ---> on… <ul><li>How it works </li></ul><ul><li>People connect to each other </li></ul><ul><li>Six degrees of separation </li></ul><ul><li>“ Are you my friend” type of awkwardness </li></ul>
  7. 8. Second generation social network (networks with objects in between, e.g., Flickr, Yahoo answers) 1) I share my pics -> -> with you ---> -->You share your pics -> ---> with him <ul><li>How it works </li></ul><ul><li>People share objects | watch others </li></ul><ul><li>Connections through objects </li></ul><ul><li>Social info streams: emergence of popular, interesting items </li></ul>
  8. 9. Viral sharing (passing on interesting stuff, e.g., YouTube videos) <ul><li>How it works </li></ul><ul><li>Individual to individual to individual </li></ul><ul><li>Popularity based navigation track “viral” items </li></ul>1) I send video I like -> -> to you. You pass on --> --> to her, who sends on to her, who passes on…
  9. 10. 3. good content floats to the top <ul><li>Multiple models of popularity </li></ul><ul><li>Users drive navigation </li></ul>
  10. 11. 4. Slides as MICROCONTENT <ul><li>URL for every slide </li></ul><ul><li>Comment on individual slides </li></ul>
  11. 12. 5. What people share on SlideShare <ul><li>Ministers share sermons </li></ul><ul><li>Teachers share lesson plans </li></ul><ul><li>Friends share memories </li></ul><ul><li>Entrepreneurs share business plans </li></ul>
  12. 13. 10 Lessons
  13. 14. 1. The beta is the market probe <ul><li>User research is hypothetical </li></ul><ul><li>Get feedback to the real thing </li></ul><ul><li>What is the risk of failure? </li></ul>
  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. 2. 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. 3. 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. Get yourself a shadow app <ul><li>Keep a pulse on main metrics </li></ul><ul><li>Experiments without A-B setup </li></ul><ul><li>Simpler than logs, faster than usability testing </li></ul><ul><li>Whole team responds to it </li></ul>
  18. 19. When feedback becomes a torrent <ul><li>Feedback form not enough. Too unstructured </li></ul><ul><li>Issues need prioritization </li></ul><ul><li>Diff users want diff features </li></ul><ul><li>New team members need summary info </li></ul><ul><li>Improvements beyond low hanging fruits </li></ul>
  19. 20. 5. Launch first, refine later <ul><li>UX folks can over analyze </li></ul><ul><li>Look at examples, take a guess </li></ul><ul><li>Put it out there. Respond. Refine. </li></ul>
  20. 21. 6. designer-developer role is crucial <ul><li>Easier communication </li></ul><ul><li>Reduced design work </li></ul>
  21. 22. 7. Under invest in visual design <ul><li>Let users feel ownership of space </li></ul><ul><li>Unpolished look is fine </li></ul>
  22. 23. 8. Pay attention to technical simplicity Balance user needs & technical simplicity Complexity > slower, riskier, harder to maintain
  23. 24. 9. Help users kick ass Everything else is secondary No step by step ROI calculations Have sound business model, but don’t sacrifice user good
  24. 25. 10. Single biggest win: make app faster
  25. 26. Finally <ul><li>www.slideshare.net/rashmi </li></ul>

×