Lean Prototyping


Published on

Lean Prototyping presentation from Boston UXPA 2013

Published in: Design, Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Just in case I say something offensive…
  • We’re going to break this up into twoparts.
  • Muda is a Japanese word. It’s part of the philosophy of the Toyota Production System.
  • And then they can’t adapt what they’ve built to match the design.
  • Possible causes: Flawed design, laziness, overwhelmed by constraints, or an overinflated sense of design abilities.
  • Including specs, wireframes, comps, and copy decks.
  • Four incompatible design documents: Specs, wireframes, comps, and copy deck.It can be exhausting to keep these all in sync, so they usually aren’t.Development then has no idea which is the correct version.Two development teams…
  • Too many designs are optimized for “sunny-day” scenarios.They blow up with long (or short) values, or long or empty lists..
  • Now we’re at the really bad ones.There are degrees of art, from the completely impossible to the impossible within time, budget, or platform constraints.
  • This is pure waste.At least art is attempting to solve a real problem.
  • At least one of these, two of these, three of these….
  • Prototyping is a great way to avoid these!Don’t Try This at Home: You’ll find out what the standard controls are and what are custom controls.Developer Disconnect: Unlikely if development is actively involved in the prototype.Premature Developmentation: Harness that enthusiasm and energy and apply it to prototyping and research spikes.Developer redesign: Unnecessary if they are invested in the design.
  • 4. Quadruplication: The prototype becomes the single truth for interactions, visual, content, and specifications.3. Edge Case Surprise: Use templates and simple data models to test various cases within the prototype.2. Art: You can’t prototype art. If the prototype works, you’re good.1. Imagineering: Use a combination of lean startup/customer development + a prototype or simulation.
  • What’s a simulation?Or really, what’s the difference between a prototype and a simulation?We’re abusing the word “prototype”
  • A simulation imitates software.
  • A prototype IS software.
  • These are all imitations
  • Big Prototype Up FrontExample: Web applicationGoal: transfer directly into development
  • The biggest benefit of Big Prototype Up Front is that you will find more showstoppers early in the process.
  • First we need to define it.
  • We need to find a way to balance the priorities of the various disciplines so we can deliver value to our customers for a profit.Great design that ignores the medium will increase development, testing, and maintenance efforts.Poor design will increase sales & marketing effort.Poor design will increase training & support effort.Development shortcuts will increase maintenance work.
  • Someone wants it.We can build it.We can make money doing it.If those are true, you are probably building the right thing.
  • Questions
  • Across all activities.
  • Splitting up the requirements work from both a technical and design viewpoint is better.Trusting in a single Subject Matter Expert / BA can be dangerous.
  • To put it a little more nicely, the vast majority of human beings are not wired to think abstractly about software.That is why we earn good money.Show, don’t tell.
  • Product Manager should own the “should we do it?” decisions.CTO should own the “can we do it?” decisions.Avoid committees like the plague.
  • People are less likely to criticize a finished-looking design.
  • Target platforms and tools are changing so rapidly.
  • Avoid big reveals, big design rounds, and long design review meetings.Release designs to users and stakeholders feature by feature or screen by screen as soon as they are ready.
  • Within your team: share as early as possible.To stakeholders: Not much longer after that.
  • Don’t get all fancy.
  • It’s too easy to delay a project for months perfecting obscure corners. Just let them suck for now.It’s OK, you can come back to it later.
  • Get everything working and usable, then make it beautiful.UT2003 vs UT2004
  • It’s a great sales tool. It’s “Alpha”.I’ve done this at conferences. Get feedback on day one, go back to the hotel room and prototype their requests, then demo on day two.
  • Good developers will work nights and weekends on optional but interesting challenges.Theymight not do it for what they have to do, but they will do it for what they want to do.
  • Lean Prototyping

    1. 1. Jason Stehle@jasonstehlejasonstehle@gmail.comhttp://leanproto.com
    2. 2. The views stated hereare not necessarilythose of my employersor of my clients.
    3. 3. AGENDA• 8 Wastes & Prototyping• Questions• 12 Lean Practices• Questions
    4. 4. The Top 8 Wastes ofSoftware Design
    5. 5. Muda (waste):Wasted time, money,materials, and energy.
    6. 6. Keep count of howmany of these youhave experienced:
    7. 7. Don’t Try This at Home:The assumption that your team cando what Google, Apple, orFacebook did with your relativelytiny budget and skill set.#8
    8. 8. DeveloperDisconnect:The development team makes amajor misinterpretation of how adesign should work.#7
    9. 9. PrematureDevelopmentation:The development team startsbuilding the system before designhas started.#6
    10. 10. Developer Redesign:The development team changes adesign without consulting thedesigners.#5
    11. 11. Quadruplication:Making edits to multiple designdeliverables to handle a singlechange.#4
    12. 12. leanproto.com @jasonstehleWireframesCompsCopy DeckSpecificationDevelopmentRulesInteractionsAppearanceContentWhere’stheTruth?Current State: Designs of Record
    13. 13. Edge Case Surprise:Finding out your design is brokenwhen real-world data is loaded.#3
    14. 14. Art:A design that cant be built.#2
    15. 15. Imagineering:Solving a problem that onlyexists in your imagination.#1
    16. 16. How many of thesehave you experienced?• Don’t Try This at Home• Developer Disconnect• Premature Developmentation• Developer Redesign• Quadruplication• Edge Case Surprise• Art• Imagineering
    17. 17. The Solution:• Don’t Try This at Home… Prototype• Developer Disconnect… Prototype• Premature Developmentation…Prototype• Developer Redesign… Prototype
    18. 18. The Solution:• Quadruplication… Prototype• Edge Case Surprise… Prototype• Art… Prototype• Imagineering… Customer Development+ Prototype/Simulation
    19. 19. Prototype vs.Simulationor, taking back the word “prototype”
    20. 20. Simulation:The imitative representation of thefunctioning of one system orprocess by means of thefunctioning of another.Source: http://www.merriam-webster.com
    21. 21. Prototype:A first full-scale and usuallyfunctional form of a new type ordesign of a construction.Source: http://www.merriam-webster.com
    22. 22. Simulations:• Paper prototypes• Clickable comps• Interactive wireframes
    23. 23. Prototype:• Built in the medium (HTML,native desktop, native mobile…)
    24. 24. Get the Server out ofthe Way• Front-end only, ideally• Presentation logic only
    25. 25. leanproto.com @jasonstehleVisualRefinement(CSS, Imagery)SketchesInteractiveRefinement(JS)Annotations(Inline, JSON)Content(Markdown)Prototype DevelopmentDesign of RecordFuture State: BPUFLayout(HTML)
    26. 26. Project Energyleanproto.com @jasonstehleFind showstoppers hereNot here• Find major problems when the team ismost energized and nothing is locked in.• Showstoppers found during the slograrely get elegant solutions.
    27. 27. How do we know if weare building the rightthing?
    28. 28. Interaction &Visual DesignTraining, Support,& MaintenanceSales &MarketingDevelopment& TestingThe Right ThingEverybody has their own ideas.“A great user experience” “A great feature set”“Easy to sell a lot of it”“Easy to support”
    29. 29. The Right Thing:• An implementable solution• to a real problem• that we can deliver for aprofit.A customer-validated prototype is probably thebest way.
    30. 30. Questions &Clarification
    31. 31. A lean processminimizes wastewhile delivering valueto the customer.
    32. 32. The top 12 leanpractices I couldthink of:
    33. 33. The Office of theBusiness Analyst:Beware of SMEs. Everymember of the core designteam should be part businessanalyst.#12
    34. 34. Imaginations Fail:Don’t ask your customers touse their imagination.They don’t have any.#11
    35. 35. BenevolentDictatorships:Keep final decision-making powerin as few hands as possible.Product Manager and CTO areideal.#10
    36. 36. Laziness Is a Virtue:Leave the prototype rough.You’ll get better feedback.#9
    37. 37. Learn Hard:The real work is inunderstanding the problemdomain and the platform.#8
    38. 38. Everybody Has anAttention Deficit:It’s only a matter of timebefore you trigger it.#7
    39. 39. Look Stupid:Deliver flawed straw menearly and often.Many ideas grow better when transplanted intoanother mind than in the one where they sprungup.- Oliver Wendell Holmes#6
    40. 40. No Geniuses Here:Don’t innovate for innovation’ssake. Just challengeassumptions, apply gooddesign, and test.#5
    41. 41. StrategicEmbarrassment:Put your effort where your userslive. Everything else can suck.Exception: Initial user experience(registration, payment, etc.)#4
    42. 42. Code Before Comps:Don’t prematurely optimize.#3
    43. 43. I Want to Believe:Make it easy to prototypewithin a released application.#2
    44. 44. Progressive UXEnhancement:Create good, better, and bestlevels of design for features thatare difficult to implement.#1
    45. 45. Thanks!Jason Stehle@jasonstehlejasonstehle@gmail.comhttp://leanproto.com