Lean UX Principles in Practice (Zach Larson on SideReel's iOS App)

3,289 views
3,097 views

Published on

Zach will discuss the 9 LeanUX principles and how his team used them as they built and exited a company. Few of the principles were intentionally picked but most became apparent once codified. He'll specifically talk about a few key practices (Information Radiators and Vicious Prioritization) that helped make the SideReel team a phenomenal success.

See also http://www.balancedteam.org/balconf-2011-resources/ for other Balanced Team Conference talks.

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

No Downloads
Views
Total views
3,289
On SlideShare
0
From Embeds
0
Number of Embeds
1,135
Actions
Shares
0
Downloads
1
Comments
0
Likes
6
Embeds 0
No embeds

No notes for slide

Lean UX Principles in Practice (Zach Larson on SideReel's iOS App)

  1. 1. LeanUX Principles In Practice SideReel’s iOS App How the Balanced Team community and LeanUX principles made a good team great and helped us exit for a gazillion* dollars. #balconf Zach Larson | @zachlarson | zachlarson.orgMonday, September 26, 2011
  2. 2. Me • Co-Founder and CPO of SideReel, now Director of Product Management at Rovi • SideReel was founded, grew to profitability, and exited in just over 4 years • @zachlarson on TwitterMonday, September 26, 2011
  3. 3. Talk about history... • Anders & Lane • AgileUX/Balanced Team/Whatever Summits (no, seriously) • Janice, LeanUX Principles • Meetups • This is a thing...Monday, September 26, 2011
  4. 4. Lean UX Principles (courtesy of Janice Fraser) • Design + product management + development = 1 product team • Focus on high-value issues without losing sight of big picture • Test design hypotheses via rapid cycles of think–make–check • Externalize your work–be collaborative and visible • Research with users is the best source of information • Know when to utilize quantitative and qualitative info • 3 most important words in UX: context, context, contextMonday, September 26, 2011
  5. 5. SideReel iOS Project • SideReel is the best way to find and track all your favorite tv shows online • Started in 2006, didn’t get to mobile until late 2010 • Wanted to extend SideReel’s core non-watching functionality as a companion screen • Was our second consulting engagement type of project • Conception to delivery in ~7 weeks, over 250K installs so far • Currently at >250K installs with mediocre ratingsMonday, September 26, 2011
  6. 6. Monday, September 26, 2011
  7. 7. SideReel flew to Michigan to work with the Atomic Object. We brought personas and use casesMonday, September 26, 2011
  8. 8. In three days we defined the project....Monday, September 26, 2011
  9. 9. ...created user flows...Monday, September 26, 2011
  10. 10. ...sketched wireframes...Monday, September 26, 2011
  11. 11. ...and started coding.Monday, September 26, 2011
  12. 12. Along the way to release we: • Did user testing with paper prototypes and my phone • Got builds almost every day • Developed the necessary APIs to support the app, by the same team • Iterated around the many design problems we encounteredMonday, September 26, 2011
  13. 13. Monday, September 26, 2011
  14. 14. Lean UX Principles (courtesy of Janice Fraser) • Design + product management + development = 1 product team • Focus on high-value issues without losing sight of big picture • Test design hypotheses via rapid cycles of think–make–check • Externalize your work–be collaborative and visible • Research with users is the best source of information • Know when to utilize quantitative and qualitative info • 3 most important words in UX: context, context, contextMonday, September 26, 2011
  15. 15. Things that worked... • TALKING TO USERS!!! • Vicious prioritization • Information radiators • Partnering with iOS experts (Atomic Object) • Pre-existing personas and key use cases • Extensive team cross-pollinization • Paper prototype testing • Incremental deliveryMonday, September 26, 2011
  16. 16. Things that didn’t.... • Physical separation was hard • We weren’t ready for the technological hurdles imposed by the mobile platform especially w/r/t maintenance • Some technical challenges • I wish I’d been able to fly my whole team out for the first session • Prrobably should’ve designed for a higher rating...maybeMonday, September 26, 2011
  17. 17. Conclusion An integrated team, focusing on the same goals, working in an iterative rhythm, testing their hypotheses, and all sharing the same data built something great. (we also communicated pretty well)Monday, September 26, 2011

×