1430 jeff gothelf - the ladders case study - sll-conf_2011_gothelf

7,600 views

Published on

Published in: Business
1 Comment
7 Likes
Statistics
Notes
  • download option enable please
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
7,600
On SlideShare
0
From Embeds
0
Number of Embeds
701
Actions
Shares
0
Downloads
0
Comments
1
Likes
7
Embeds 0
No embeds

No notes for slide
  • #LeanUX hash tag
  • 1430 jeff gothelf - the ladders case study - sll-conf_2011_gothelf

    1. How TheLadders.com Got Out of the Deliverables Business<br />A Case Study<br />#LeanUX | @jboogie<br />http://talkingtraffic.org/wp-content/images/stack_documents.jpg<br />
    2. Who is this guy?<br />I like to point<br />Jeff Gothelf<br />Currently: <br />Director of UX at TheLadders.com<br />Previously: <br />Publicis Modem, Webtrends, AOL, Fidelity and an assortment of startups<br />Blog: <br />www.jeffgothelf.com/blog<br />Twitter: <br />@jboogie<br />Email: <br />jgothelf@theladders.com<br />
    3. Job site for professionals earning $100k or more and the recruiters/employers looking to hire them.<br />#LeanUX | @jboogie<br />
    4. Everything was butterflies and rainbows in our waterfall world<br />I couldn’t find a pic of a waterfall, a rainbow AND butterflies….sorry.<br /><ul><li> 3-9 month release cycles
    5. Thick functional specs
    6. In-depth wireframe decks
    7. Long visual design cycles
    8. Late-stage user validation and testing
    9. Explicit hand-offs</li></ul>#LeanUX | @jboogie<br />http://www.niagarafallscanadapics.net/Niagara-falls-Canada-rainbow-pdam2.jpg<br />
    10. We were in the deliverables business<br />It was the way we’d “always” worked<br />#LeanUX | @jboogie<br />http://www.niagarafallscanadapics.net/Niagara-falls-Canada-rainbow-pdam2.jpg<br />
    11. …and then we became an Agile shop<br />Moving away from big design up front and deliverables<br />We needed to get out of the deliverables business!<br />#LeanUX | @jboogie<br />
    12. Tactic 1: Style guides<br />#LeanUX | @jboogie<br />
    13. Style guides get the mundane out of the way<br />Allow team to focus on core design problems<br />#LeanUX | @jboogie<br />
    14. Create a re-usable asset library<br />Not just for designers, but for developers too!<br />#LeanUX | @jboogie<br />
    15. Tactic 2: Collaborative Problem Solving<br />#LeanUX | @jboogie<br />
    16. Design studios<br />Focus the team on solving a problem, not implementing a solution<br />#LeanUX | @jboogie<br />
    17. Outcome, not output<br />Create just enough design to get started<br />#LeanUX | @jboogie<br />
    18. Tactic 3: Pair developers and designers<br />#LeanUX | @jboogie<br />
    19. Pairing saves time<br />It also levels the playing field<br />#LeanUX | @jboogie<br />http://hoveringartdirectors.tumblr.com/page/2<br />
    20. Big Learning #1: Human to human > Paper to human<br />#LeanUX | @jboogie<br />
    21. Conversation and collaboration are faster<br />Get to validated learningsearlier<br />#LeanUX | @jboogie<br />http://www.enterpriseirregulars.com/wordpress/wp-content/uploads/2010/04/conversation.jpg<br />
    22. Big Learning #2: Personality and attitude are key to success<br />#LeanUX | @jboogie<br />
    23. Stay open to new ways of working together<br />Transparency builds trust<br />#LeanUX | @jboogie<br />
    24. Thanks!<br />Please reach out with questions.<br />@jboogie<br />jeff@jeffgothelf.com<br />www.jeffgothelf.com/blog<br />#LeanUX | @jboogie<br />

    ×