Your SlideShare is downloading. ×
Iterating awesomeness
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Iterating awesomeness


Published on

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 …

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!

Published in: Design, Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Iterating Awesomeness Designing Value Through Shared Understanding Michael Jovel- @mjovel ba
  • 2. 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.
  • 3. forums/battles-7/bugs-bunny- vs-popeye-the-sailor- man-757492/
  • 4. history of production
  • 5. Courtesy Niagara Aerospace Museum
  • 6.
  • 7. Document Design Develop Test Launch Waterfall
  • 8. Exhaustive Specifications
  • 9. History of the World Part I
  • 10. That is not what they wanted
  • 11. That is not what they wanted
  • 12. Iteration
  • 13. Iteration
  • 14. where do we start?
  • 15. Focus on the Problem
  • 16. “People don’t want to buy a quarter-inch drill. They want a quarter-inch hole.” - Theodore Levitt
  • 17. Create a sign-up form Instead of: Outcome Increase User Subscriptions
  • 18. 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
  • 19. Hypothesis
  • 20. a tentative assumption made in order to draw out and test its logical or empirical consequences merriam-webster
  • 21. Why Hypothesis •Rather than make assertions it puts forth a question which must be validated •Engages Team Creativity
  • 22. •What assumptions do you have that if proven false will cause your solution to fail?
  • 23. Basic Hypothesis WE BELIEVE ___________ and if this is true we should see __________
  • 24. Prioritize
  • 25. Get out of the building
  • 26. Low inventory
  • 27.
  • 28. 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
  • 29. Pattern Libraries
  • 30. 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.)
  • 31.
  • 32. focus on experience instead of just ui
  • 33. helps developers when prototyping
  • 34.
  • 35.
  • 36. Design Studio
  • 37.
  • 38. 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
  • 39.
  • 40. Sketch •8-10 minutes to sketch individually •Could be flow diagrams, wireframes, etc.
  • 41. Individual Pitch •3 minutes to pitch team
  • 42. 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
  • 43. Team Sketching •Team takes 10 minutes to iterate on best aspecs of Sketch
  • 44. Team Pitch •Team selects one member to pitch teams solution to larger team
  • 45.
  • 46. That is great but we are a distributed team
  • 47.
  • 48.
  • 49. Raise Unicorns
  • 50. 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. Unicorn?
  • 51. Promote Code literacy
  • 52. Promote Design literacy
  • 53. Promote Business literacy
  • 54. literacy is not fluency
  • 55. Pair Designing
  • 56. Benefits of Pair Design • Make sure designers and developers spend time working together • saves time on implementation • promotes ownership
  • 57.
  • 58.
  • 59. 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
  • 60. where Lean UX STRUGGLES
  • 61. AD Agency •Structured around deliverables •Based on finite term of relationship
  • 62. Government •Contractor agreements based around specifications & deliverables •Failure is subject to public scrutiny
  • 64. “It’s easier to ask forgiveness than it is to get permission” - U.S. Navy Rear Admiral Grace Hopper
  • 65.
  • 66. Questions? Michael Jovel- @mjovel