Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Iterating Awesomeness: Designing Value Through Shared Understanding

Iterating Awesomeness: Designing Value Through Shared Understanding

Lean UX places a greater emphasis on the actual experience being delivered rather than bloated specifications and other documentation. Learn how to move from an environment driven by requirements documents to one that is based on constantly validated measurable outcomes. Utlize design studio and pair designing to maximize shared understanding and team buy-in. Iterate Awesomeness!

4bfb73a8679cbcb7a36c9557e75fba0f?s=128

Michael Jovel

May 02, 2013
Tweet

Transcript

  1. Iterating Awesomeness Designing Value Through Shared Understanding Michael Jovel- @mjovel

    b a
  2. None
  3. The opinions expressed here are those of the Presenter and

    do not necessarily reflect the positions of the U.S. Department of Defense. Despite his statements to the contrary he does not have the authority or capability to order a drone strike based on the geolocation data of your snarky tweets.
  4. http://www.comicvine.com/ forums/battles-7/bugs-bunny- vs-popeye-the-sailor- man-757492/

  5. None
  6. None
  7. None
  8. history of production

  9. Courtesy Niagara Aerospace Museum

  10. http://www.leafletprinting.co.uk/blog/printing-history-the-gutenberg-press/

  11. Document Design Develop Test Launch Waterfall

  12. Exhaustive Specifications

  13. History of the World Part I

  14. None
  15. That is not what they wanted

  16. That is not what they wanted

  17. None
  18. Iteration http://visual.ly/lean-startup

  19. Iteration

  20. where do we start?

  21. Focus on the Problem

  22. “People don’t want to buy a quarter-inch drill. They want

    a quarter-inch hole.” - Theodore Levitt
  23. Create a sign-up form Instead of: Outcome Increase User Subscriptions

  24. create an e-mail account where Public affairs officers can submit

    content Instead of: Outcome Increase the number of content that come in from PA shops from the fleet
  25. Hypothesis

  26. a tentative assumption made in order to draw out and

    test its logical or empirical consequences merriam-webster
  27. Why Hypothesis •Rather than make assertions it puts forth a

    question which must be validated •Engages Team Creativity
  28. •What assumptions do you have that if proven false will

    cause your solution to fail?
  29. Basic Hypothesis WE BELIEVE ___________ and if this is true

    we should see __________
  30. Prioritize

  31. Get out of the building

  32. None
  33. Low inventory

  34. http://www.carolinabarcode.com/choosing-barcode-inventory-software-a-45.html

  35. Design Idea Inventory •high number of unvalidated design ideas leads

    to large deliverables •leads to lag in production as team awaits deliverables • maximizes the risk as there more time between creation and validation
  36. Pattern Libraries

  37. Pattern Library •Library of UI Patterns that developers can use

    (i.e. buttons, fields, etc. •Library of UI Components composed of multiple patterns (i.e. forms, video player, etc.)
  38. http://patternry.com/

  39. focus on experience instead of just ui

  40. helps developers when prototyping

  41. http://styletil.es/

  42. http://danielmall.com/articles/rif-element-collages/

  43. Design Studio

  44. http://designforamericayale.wordpress.com/

  45. Supplies •Butcher paper, painters tape, sharpies and stop watch, grid

    template sheets •Build small 3-4 person teams composed of designer, developers and business team. •Give each team a persona to focus on
  46. http://500px.com/Twitter

  47. Sketch •8-10 minutes to sketch individually •Could be flow diagrams,

    wireframes, etc.
  48. Individual Pitch •3 minutes to pitch team

  49. Critique •Each member lists 1 or 2 ways in which

    sketch achieves goal •each member Lists 1 or 2 ways in which sketch fails to achieve goal
  50. Team Sketching •Team takes 10 minutes to iterate on best

    aspecs of Sketch
  51. Team Pitch •Team selects one member to pitch teams solution

    to larger team
  52. http://500px.com/Twitter

  53. That is great but we are a distributed team

  54. None
  55. http://popapp.in

  56. http://www.fiftythree.com/paper

  57. Raise Unicorns

  58. None
  59. Mythical user experience designer with an advanced and adaptive skill

    range. Outstanding skills in graphic design, rapid prototyping, front end development, user testing, technical specifications, marketing and branding. It does not have an opinion, it has a process, and will harmonize with any environment. http://uxunicorn.com/ Unicorn?
  60. Promote Code literacy

  61. Promote Design literacy

  62. Promote Business literacy

  63. literacy is not fluency

  64. Pair Designing

  65. Benefits of Pair Design • Make sure designers and developers

    spend time working together • saves time on implementation • promotes ownership
  66. http://500px.com/Twitter

  67. http://www.flickr.com/photos/rohdesign/6131523904/

  68. Validation •send multi-disciplined team to meet with customer •take a

    copy of the MVP to visit customers •have one members lead the interview while the others observe and record
  69. where Lean UX STRUGGLES

  70. AD Agency •Structured around deliverables •Based on finite term of

    relationship
  71. Government •Contractor agreements based around specifications & deliverables •Failure is

    subject to public scrutiny
  72. DON’T GET CAUGHT UP ON PROCESS

  73. “It’s easier to ask forgiveness than it is to get

    permission” - U.S. Navy Rear Admiral Grace Hopper
  74. None
  75. http://nordstrominnovationlab.com/

  76. Questions? Michael Jovel- @mjovel mjovel@gmail.com