Your SlideShare is downloading. ×

10 Lessons Oz Ia

2,900
views

Published on

Published in: Business, Technology

0 Comments
8 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,900
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
68
Comments
0
Likes
8
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

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

    ×