PRODUCTCAMP 6                  SATURDAY 8.18.12WEB: www.pcampatl.comTWITTER: @pcampatl #pcampatl               Web: www.pc...
The UX Challenge:Why traditional UX doesn’t jibe with lean andhow you can make it work for stellar product success.Darryl ...
@UX_Life  @UX_Life
@UX_Life  @UX_Life
Lean is NOT Agile                    @UX_Life
Lean is NOT Agile                    @UX_Life
Lean is NOT Agile                    @UX_Life
Lean is NOT Agile                    @UX_Life
Lean is NOT Agile                    @UX_Life
Lean is NOT Agile                    @UX_Life
Lean is NOT Agile                    @UX_Life
@UX_Life
Lean is also NOT:                    @UX_Life
Lean is also NOT:                    @UX_Life
Lean is also NOT:                    @UX_Life
Lean is also NOT:                    @UX_Life
Lean is also NOT:                    @UX_Life
Lean is also NOT:                    @UX_Life
@UX_Life
1.Eliminate Waste                    @UX_Life
1.Eliminate Waste2.Build Quality In                     @UX_Life
1.Eliminate Waste2.Build Quality In3.Create Knowledge                     @UX_Life
1.Eliminate Waste2.Build Quality In3.Create Knowledge4.Defer Commitment                     @UX_Life
1.Eliminate Waste2.Build Quality In3.Create Knowledge4.Defer Commitment5.Deliver Fast                     @UX_Life
1.Eliminate Waste2.Build Quality In3.Create Knowledge4.Defer Commitment5.Deliver Fast6.Respect People                     ...
1.Eliminate Waste2.Build Quality In3.Create Knowledge4.Defer Commitment5.Deliver Fast6.Respect People7.Optimize the Whole ...
@UX_Life
@UX_Life
Start        Finish                 @UX_Life
Start        Repeat                 @UX_Life
Traditional UX cycle                       @UX_Life
Traditional UX cycle Requirements  Requirements Document                          @UX_Life
Traditional UX cycle Requirements  Requirements Document UX Design  Design Specifications                          @UX_Life
Traditional UX cycle Requirements   Requirements Document UX Design   Design Specifications Implementation   Product       ...
Traditional UX cycle Requirements   Requirements Document UX Design   Design Specifications Implementation   Product Verific...
Traditional UX cycle Requirements   Requirements Document UX Design   Design Specifications Implementation   Product Verific...
This is Your Brain on Lean          Start                  Sprint                    Sprint                       Sprint  ...
StartRequirements  Requirements DocumentDesign - UX                             Sprint  Design SpecificationsImplementation...
StartRequirements  Requirements DocumentDesign - UX                             Sprint  Design SpecificationsImplementation...
Where Lean Goes Wrong                        @UX_Life
Where Lean Goes WrongForcing developers to design                               @UX_Life
Where Lean Goes WrongForcing developers to designPretending surveys are UX                               @UX_Life
Where Lean Goes WrongForcing developers to designPretending surveys are UXDepending solely on A/B testing, clicks, hits or...
Where UX Goes Wrong                      @UX_Life
Where UX Goes WrongNot measuring results                        @UX_Life
Where UX Goes WrongNot measuring resultsTrying to tell people that they’re doing it wrong                                 ...
Where UX Goes WrongNot measuring resultsTrying to tell people that they’re doing it wrongConflicting with the lean culture ...
@UX_Life
Get in Rhythm      Figure 5.1, “Implementing Lean Software Development: From Concept to Cash,” Poppendieck, Mary and Tom (...
Get in RhythmSet the course           Figure 5.1, “Implementing Lean Software Development: From Concept to Cash,” Poppendi...
Get in Rhythm                                                          Guide the ship      Figure 5.1, “Implementing Lean ...
Get in Rhythm            Figure 5.1, “Implementing Lean Software Development: From Concept to Cash,” Poppendieck, Mary and...
@UX_Life
@UX_Life
@UX_Life
The metronome is ticking                           @UX_Life
No Fancy ReportsRequirements  Requirements DocumentDesign - UX  Design SpecificationsImplementation  ProductVerification  Fi...
No Fancy ReportsRequirements  Requirements DocumentDesign - UX  Design SpecificationsImplementation  ProductVerification  Fi...
No Fancy ReportsRequirements  Requirements DocumentDesign - UX  Design SpecificationsImplementation  ProductVerification  Fi...
No Fancy ReportsRequirements  Requirements DocumentDesign - UX  Design SpecificationsImplementation  ProductVerification  Fi...
No Time for 7 to 12 Users                            @UX_Life
No Time for 7 to 12 Users  Maintain priorities                            @UX_Life
No Time for 7 to 12 Users  Maintain priorities  Set up consistent user testing                                   @UX_Life
No Time for 7 to 12 Users  Maintain priorities  Set up consistent user testing  Be an expert                              ...
Use The Strengths of Lean                       @UX_Life
Use The Strengths of LeanDelayed Commitment                       @UX_Life
Use The Strengths of LeanDelayed CommitmentFlexibility                       @UX_Life
Use The Strengths of LeanDelayed CommitmentFlexibilityQuick reactions                       @UX_Life
Use The Strengths of LeanDelayed CommitmentFlexibilityQuick reactionsChange Metrics                       @UX_Life
@UX_Life
“Statistics are like bikinis. What they reveal is suggestive, but what they conceal is vital.”                    - Aaron ...
@UX_Life
@UX_Life
@UX_Life
Use your judgement!                      @UX_Life
What if I’m already in my development cycle?                                     @UX_Life
“When you find yourself in a hole, stopdigging.”           - Will Rodgers                                  @UX_Life
Key Take Aways                 @UX_Life
Key Take AwaysAgile is not LeanDon’t try to control the processGet in syncTrim the fatUse the strengths of leanBe an exper...
Feedback@UX_Life
Thank you!Diamond Sponsor:Platinum Sponsors:  Gold Sponsors: Silver Sponsors:
Upcoming SlideShare
Loading in …5
×

Why Traditional UX doesn't Jibe with Lean and How You Can Make it Work for Stellar Product Success - product camp2012

333
-1

Published on

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
333
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • worked as a UX developer end to end spent a lot of time trying to increase the use of UX and contemplating how UX could fit into the lean and agile process\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • book doesn’t talk a lot about UX research and design but I did get a chance to meet Mary and Tom Poppendieck and ask them about how UX fits in and this presentation is about\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • no lean presentation would be complete without explaining why it’s not agile.\nUnderstand this and you’ll automatically be one of the smartest people in the room.\nMary & Tom Poppendieck\n\n\n\n
  • 7 Principles of lean I recommend “Implementing Lean Software Development: From Concept to Cash” by Mary and Tom Poppendieck\n
  • 7 Principles of lean I recommend “Implementing Lean Software Development: From Concept to Cash” by Mary and Tom Poppendieck\n
  • 7 Principles of lean I recommend “Implementing Lean Software Development: From Concept to Cash” by Mary and Tom Poppendieck\n
  • 7 Principles of lean I recommend “Implementing Lean Software Development: From Concept to Cash” by Mary and Tom Poppendieck\n
  • 7 Principles of lean I recommend “Implementing Lean Software Development: From Concept to Cash” by Mary and Tom Poppendieck\n
  • 7 Principles of lean I recommend “Implementing Lean Software Development: From Concept to Cash” by Mary and Tom Poppendieck\n
  • 7 Principles of lean I recommend “Implementing Lean Software Development: From Concept to Cash” by Mary and Tom Poppendieck\n
  • Sounds simple enough\n
  • \n
  • first take was to get rid of the end and continually improve.\nlean takes this a step farther\n
  • For any given product this is the traditional UX cycle it’s how we’re taught in school. \nThis works assuming a waterfall or iterative waterfall method by black boxing implementation and breaks Lean Principles:\nDeliver fast, Creates waste, commits too early\n
  • For any given product this is the traditional UX cycle it’s how we’re taught in school. \nThis works assuming a waterfall or iterative waterfall method by black boxing implementation and breaks Lean Principles:\nDeliver fast, Creates waste, commits too early\n
  • For any given product this is the traditional UX cycle it’s how we’re taught in school. \nThis works assuming a waterfall or iterative waterfall method by black boxing implementation and breaks Lean Principles:\nDeliver fast, Creates waste, commits too early\n
  • For any given product this is the traditional UX cycle it’s how we’re taught in school. \nThis works assuming a waterfall or iterative waterfall method by black boxing implementation and breaks Lean Principles:\nDeliver fast, Creates waste, commits too early\n
  • For any given product this is the traditional UX cycle it’s how we’re taught in school. \nThis works assuming a waterfall or iterative waterfall method by black boxing implementation and breaks Lean Principles:\nDeliver fast, Creates waste, commits too early\n
  • how do you fit into this. This is the UX challenge how to take what you know and fit it into this type of process.\nTalk to the deliverables at the end of each\n
  • \n
  • because of this challenge and the admitted strengths of lean companies skimp on UX\n“We’re doing well and the stats look good why do we need UX?” I DON’T KNOW, THAT’S THE POINT -- IF YOU DON’T MEASURE IT... YOU COULD BE LOSING USERS BC YOU DON’T MEET EXPECTATIONS. \n
  • because of this challenge and the admitted strengths of lean companies skimp on UX\n“We’re doing well and the stats look good why do we need UX?” I DON’T KNOW, THAT’S THE POINT -- IF YOU DON’T MEASURE IT... YOU COULD BE LOSING USERS BC YOU DON’T MEET EXPECTATIONS. \n
  • because of this challenge and the admitted strengths of lean companies skimp on UX\n“We’re doing well and the stats look good why do we need UX?” I DON’T KNOW, THAT’S THE POINT -- IF YOU DON’T MEASURE IT... YOU COULD BE LOSING USERS BC YOU DON’T MEET EXPECTATIONS. \n
  • \nYOU DON’T CONTROL THE PROCESS, YOU INFLUENCE IT AT CRITICAL POINTS.\ndon’t bother telling them why your way is better than their way\n
  • \nYOU DON’T CONTROL THE PROCESS, YOU INFLUENCE IT AT CRITICAL POINTS.\ndon’t bother telling them why your way is better than their way\n
  • \nYOU DON’T CONTROL THE PROCESS, YOU INFLUENCE IT AT CRITICAL POINTS.\ndon’t bother telling them why your way is better than their way\n
  • What do you do about it? how do we make it fit?\nwe have to get in sync our process can’t take a month\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • How do we move that fast?\nwe need to trim the fat. Use the strengths of lean to support UX shortcomings don’t sweat the small stuff\nParticipate in the daily scrums too if you can\n\n
  • first thing you’ll like this. get rid of the reports let’s talk to people\n
  • first thing you’ll like this. get rid of the reports let’s talk to people\n
  • first thing you’ll like this. get rid of the reports let’s talk to people\n
  • How do you get away with this?\nremember what’s important focus on your goals first the core product is most important\nUse your judgement\n
  • How do you get away with this?\nremember what’s important focus on your goals first the core product is most important\nUse your judgement\n
  • How do you get away with this?\nremember what’s important focus on your goals first the core product is most important\nUse your judgement\n
  • you’re only testing what has been agreed will be developed\nit doesn’t have to be perfect the first time keep testing and fix design issues as they come up don’t stress\n\n
  • you’re only testing what has been agreed will be developed\nit doesn’t have to be perfect the first time keep testing and fix design issues as they come up don’t stress\n\n
  • you’re only testing what has been agreed will be developed\nit doesn’t have to be perfect the first time keep testing and fix design issues as they come up don’t stress\n\n
  • you’re only testing what has been agreed will be developed\nit doesn’t have to be perfect the first time keep testing and fix design issues as they come up don’t stress\n\n
  • we all know about lying with statistics. but this isn’t really about intentional lying or even about the statistics themselves it’s about when the truth of statistics doesn’t match the reality we live in.\n
  • \n
  • remember to be an expert use your judgement and experience to decide if you’re going to test something or not. what are your priorities?\n
  • remember to be an expert use your judgement and experience to decide if you’re going to test something or not. what are your priorities?\n
  • SIMPLE ENOUGH OF A CHANGE THAT IT DOESN’T AFFECT THE PURPOSE or meaning \n
  • \n
  • \n
  • assess what you have already first to make sure you don’t have any glaring issues already released to the public.\nBe sure to use the guiding principles discussed that will allow you to be in sync so that you can catch up\n
  • don’t try to control change or even criticize the lean process in your company without upper management support it just puts a target on your back you want to influence it at key points\n\nstreamline and become rhythmic\n\nbut be wary of statistics\n
  • \n
  • \n
  • Why Traditional UX doesn't Jibe with Lean and How You Can Make it Work for Stellar Product Success - product camp2012

    1. 1. PRODUCTCAMP 6 SATURDAY 8.18.12WEB: www.pcampatl.comTWITTER: @pcampatl #pcampatl Web: www.pcampatl.comFACEBOOK: facebook.com/productcampatlanta Twitter: @pcampatl Facebook: facebook.com/productcampatlanta
    2. 2. The UX Challenge:Why traditional UX doesn’t jibe with lean andhow you can make it work for stellar product success.Darryl Prince @UX_Life
    3. 3. @UX_Life @UX_Life
    4. 4. @UX_Life @UX_Life
    5. 5. Lean is NOT Agile @UX_Life
    6. 6. Lean is NOT Agile @UX_Life
    7. 7. Lean is NOT Agile @UX_Life
    8. 8. Lean is NOT Agile @UX_Life
    9. 9. Lean is NOT Agile @UX_Life
    10. 10. Lean is NOT Agile @UX_Life
    11. 11. Lean is NOT Agile @UX_Life
    12. 12. @UX_Life
    13. 13. Lean is also NOT: @UX_Life
    14. 14. Lean is also NOT: @UX_Life
    15. 15. Lean is also NOT: @UX_Life
    16. 16. Lean is also NOT: @UX_Life
    17. 17. Lean is also NOT: @UX_Life
    18. 18. Lean is also NOT: @UX_Life
    19. 19. @UX_Life
    20. 20. 1.Eliminate Waste @UX_Life
    21. 21. 1.Eliminate Waste2.Build Quality In @UX_Life
    22. 22. 1.Eliminate Waste2.Build Quality In3.Create Knowledge @UX_Life
    23. 23. 1.Eliminate Waste2.Build Quality In3.Create Knowledge4.Defer Commitment @UX_Life
    24. 24. 1.Eliminate Waste2.Build Quality In3.Create Knowledge4.Defer Commitment5.Deliver Fast @UX_Life
    25. 25. 1.Eliminate Waste2.Build Quality In3.Create Knowledge4.Defer Commitment5.Deliver Fast6.Respect People @UX_Life
    26. 26. 1.Eliminate Waste2.Build Quality In3.Create Knowledge4.Defer Commitment5.Deliver Fast6.Respect People7.Optimize the Whole @UX_Life
    27. 27. @UX_Life
    28. 28. @UX_Life
    29. 29. Start Finish @UX_Life
    30. 30. Start Repeat @UX_Life
    31. 31. Traditional UX cycle @UX_Life
    32. 32. Traditional UX cycle Requirements Requirements Document @UX_Life
    33. 33. Traditional UX cycle Requirements Requirements Document UX Design Design Specifications @UX_Life
    34. 34. Traditional UX cycle Requirements Requirements Document UX Design Design Specifications Implementation Product @UX_Life
    35. 35. Traditional UX cycle Requirements Requirements Document UX Design Design Specifications Implementation Product Verification Final Report @UX_Life
    36. 36. Traditional UX cycle Requirements Requirements Document UX Design Design Specifications Implementation Product Verification Final Report Repeat @UX_Life
    37. 37. This is Your Brain on Lean Start Sprint Sprint Sprint Repeat @UX_Life
    38. 38. StartRequirements Requirements DocumentDesign - UX Sprint Design SpecificationsImplementation Vs. Sprint Product SprintVerification Final ReportRepeat Repeat @UX_Life
    39. 39. StartRequirements Requirements DocumentDesign - UX Sprint Design SpecificationsImplementation Vs. Sprint Product SprintVerification Final ReportRepeat Repeat @UX_Life
    40. 40. Where Lean Goes Wrong @UX_Life
    41. 41. Where Lean Goes WrongForcing developers to design @UX_Life
    42. 42. Where Lean Goes WrongForcing developers to designPretending surveys are UX @UX_Life
    43. 43. Where Lean Goes WrongForcing developers to designPretending surveys are UXDepending solely on A/B testing, clicks, hits or otherquantitative measures @UX_Life
    44. 44. Where UX Goes Wrong @UX_Life
    45. 45. Where UX Goes WrongNot measuring results @UX_Life
    46. 46. Where UX Goes WrongNot measuring resultsTrying to tell people that they’re doing it wrong @UX_Life
    47. 47. Where UX Goes WrongNot measuring resultsTrying to tell people that they’re doing it wrongConflicting with the lean culture or process @UX_Life
    48. 48. @UX_Life
    49. 49. Get in Rhythm Figure 5.1, “Implementing Lean Software Development: From Concept to Cash,” Poppendieck, Mary and Tom (2007) @UX_Life
    50. 50. Get in RhythmSet the course Figure 5.1, “Implementing Lean Software Development: From Concept to Cash,” Poppendieck, Mary and Tom (2007) @UX_Life
    51. 51. Get in Rhythm Guide the ship Figure 5.1, “Implementing Lean Software Development: From Concept to Cash,” Poppendieck, Mary and Tom (2007) @UX_Life
    52. 52. Get in Rhythm Figure 5.1, “Implementing Lean Software Development: From Concept to Cash,” Poppendieck, Mary and Tom (2007) Instigate corrections @UX_Life
    53. 53. @UX_Life
    54. 54. @UX_Life
    55. 55. @UX_Life
    56. 56. The metronome is ticking @UX_Life
    57. 57. No Fancy ReportsRequirements Requirements DocumentDesign - UX Design SpecificationsImplementation ProductVerification Final ReportRepeat @UX_Life
    58. 58. No Fancy ReportsRequirements Requirements DocumentDesign - UX Design SpecificationsImplementation ProductVerification Final ReportRepeat @UX_Life
    59. 59. No Fancy ReportsRequirements Requirements DocumentDesign - UX Design SpecificationsImplementation ProductVerification Final ReportRepeat @UX_Life
    60. 60. No Fancy ReportsRequirements Requirements DocumentDesign - UX Design SpecificationsImplementation ProductVerification Final ReportRepeat @UX_Life
    61. 61. No Time for 7 to 12 Users @UX_Life
    62. 62. No Time for 7 to 12 Users Maintain priorities @UX_Life
    63. 63. No Time for 7 to 12 Users Maintain priorities Set up consistent user testing @UX_Life
    64. 64. No Time for 7 to 12 Users Maintain priorities Set up consistent user testing Be an expert @UX_Life
    65. 65. Use The Strengths of Lean @UX_Life
    66. 66. Use The Strengths of LeanDelayed Commitment @UX_Life
    67. 67. Use The Strengths of LeanDelayed CommitmentFlexibility @UX_Life
    68. 68. Use The Strengths of LeanDelayed CommitmentFlexibilityQuick reactions @UX_Life
    69. 69. Use The Strengths of LeanDelayed CommitmentFlexibilityQuick reactionsChange Metrics @UX_Life
    70. 70. @UX_Life
    71. 71. “Statistics are like bikinis. What they reveal is suggestive, but what they conceal is vital.” - Aaron Levenstein @UX_Life
    72. 72. @UX_Life
    73. 73. @UX_Life
    74. 74. @UX_Life
    75. 75. Use your judgement! @UX_Life
    76. 76. What if I’m already in my development cycle? @UX_Life
    77. 77. “When you find yourself in a hole, stopdigging.” - Will Rodgers @UX_Life
    78. 78. Key Take Aways @UX_Life
    79. 79. Key Take AwaysAgile is not LeanDon’t try to control the processGet in syncTrim the fatUse the strengths of leanBe an expert @UX_Life
    80. 80. Feedback@UX_Life
    81. 81. Thank you!Diamond Sponsor:Platinum Sponsors: Gold Sponsors: Silver Sponsors:
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×