UX Lessons from the USSR: The Trouble With Manifestos

334 views
268 views

Published on

This presentation was given by our Creative Director, Erik von Stackelberg at FITC Toronto 2013.

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

  • Be the first to like this

No Downloads
Views
Total views
334
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

UX Lessons from the USSR: The Trouble With Manifestos

  1. 1. UX Lessons fromthe USSR: TheTrouble withManifestos
  2. 2. UX&professionalservices.
  3. 3. Erik von who?Erik von Stackelberg,Creative Director@stackelberg
  4. 4. The Argument
  5. 5. Creating digital productsis an interdisciplinaryundertaking. Equally, theprocess we use shouldalso embrace diversemethods where theymake sense.
  6. 6. Goals, in order of usefulness…•  Discussion for process wonks.•  Survey of techniques.•  A sample process for buildingdigital products (no patentspending!)
  7. 7. Disclaimer•  This isn’t sexy.•  This is anecdotal.•  I’m not from Russia.•  I speak really quickly.
  8. 8. On Manifestos
  9. 9. Wikipedia says:“A manifesto usually accepts apreviously published opinion orpublic consensus and/orpromotes a new idea withprescriptive notions for carryingout changes the author believesshould be made.”
  10. 10. TheCommunistManifesto.On Manifestos
  11. 11. Religiouscreed.On Manifestos
  12. 12. Brandmanuals.On Manifestos
  13. 13. Processmanifestos.On Manifestos
  14. 14. Adaptive:TheAgileManifesto.On Manifestos
  15. 15. The Agile Manifesto (Abbreviated)•  Individuals and interactions overprocesses and tools•  Working software overcomprehensive documentation•  Customer collaboration overcontract negotiation•  Responding to change overfollowing a plan
  16. 16. A Really Reductive Explanation of Agile
  17. 17. Predictive:TheWaterfallManifesto.On Manifestos
  18. 18. A Really Reductive Explanation of Waterfall
  19. 19. TheLean“Manifesto.”On Manifestos
  20. 20. TheUCD“Manifesto.”On Manifestos
  21. 21. On Interpretation
  22. 22. Wordsdon’tkillprocess.On Manifestos
  23. 23. Peoplekillprocess.On ManifestosOpinion!
  24. 24. Proposed Spectrum of Interpretation•  Fundamentalist•  Dogmatist•  Moderate
  25. 25. Appropriateandmashup.On Manifestos
  26. 26. On Bricolage
  27. 27. Wikipedia says:“…bricolage is the constructionor creation of a work from adiverse range of things thathappen to be available, or awork created by such a process.”
  28. 28. A spectrum of interpretation.•  Fundamentalist•  Dogmatist•  Moderate•  Bricoleur
  29. 29. Processbricoleurs.On Manifestos
  30. 30. BeingagileaboutAgile.On Manifestos
  31. 31. TheLeanuser-centredAgilewaterfallbricolage.On Manifestos
  32. 32. Disclaimer:Apples&oranges.On Manifestos
  33. 33. Key Roles &Team Structure
  34. 34. Team StructureThere’s no “I” in team. Onmixing the traditionalcreative process with someAgile flavouring.
  35. 35. Deathofthedesignhero.Jeff GothelfTeam Structure
  36. 36. Nunchukskills,bowhuntingskills.Team Structure
  37. 37. Teampwnership.Team Structure
  38. 38. Collaborativeclientbuy-in.Team Structure
  39. 39. Key RolesBalancing expertise andempathy. On modifyingtraditional Agile roles toshare responsibility butmaintain diversity.
  40. 40. Key Roles
  41. 41. Creative&TechReps.Key Roles
  42. 42. POasUXstrategist.Key Roles
  43. 43. “We’respecial”-ists.Key Roles
  44. 44. Process
  45. 45. Process
  46. 46. Process: DiscoveryOn adding an earlydash of UCD researchand Lean validationinto the Agileframework.
  47. 47. “What”isdangerous.Process: Discovery
  48. 48. Askwhybeforewhat.Process: Discovery
  49. 49. Process: Product DefinitionOn mashing some user-centered designplanning into the Agileframework.
  50. 50. UIshouldbepop,nothighart.Opinion!Process: Product Definition
  51. 51. Backlogsareuseful.Process: Product Definition
  52. 52. Storymapsarehellauseful.Jeff PattonProcess: Product Definition
  53. 53. Lookma,it’stheMVP!Process: Product Definition
  54. 54. Process: UX DefinitionOn adding models intothe mix to net waterfall-like client comfort anddesign vision (and Leanearly validation).
  55. 55. Dawnberret,begindesignstudio.Process: UX Definition
  56. 56. Stopandsmelltheflowers.Process: UX Definition
  57. 57. Createanarchiveofcheatsheets.Process: UX Definition
  58. 58. Getearlyeffortestimates.Process: UX Definition
  59. 59. Anyonecanplay!Process: UX Definition
  60. 60. Playwithsomemodels.Process: UX Definition
  61. 61. Colours,lensflares,bevels,oohlala!Process: UX Definition
  62. 62. Defy themishmashGUI.Process: UX Definition
  63. 63. There’smoretolife than beingridiculouslygood-looking.Process: UX Definition
  64. 64. Complementaryheadmassage?Process: UX Definition
  65. 65. Process: UX DefinitionOn MacGyveringexperience criteria intothe backlog.
  66. 66. MOAR!Process: UX Definition
  67. 67. DefinetheMDP.Process: UX Definition
  68. 68. Process: ImplementationOn integrating UCDpractices into Agilesprints.
  69. 69. Inlinevs.staggereddesign.Process: Implementation
  70. 70. Clientinputwindows.Process: Implementation
  71. 71. Creating digital productsis an interdisciplinaryundertaking. Equally, theprocess we use shouldalso embrace diversemethods where theymake sense.
  72. 72. SansBricolage
  73. 73. Sans BricolageThere are argumentsagainst process bricolage.Here are some.
  74. 74. Ifyouhavetochangeit,you’redoingitwrong.Sans Bricolage
  75. 75. Aren’twesupposedtostayflexible?Sans Bricolage
  76. 76. First,becomeamaster.Sans Bricolage
  77. 77. Becomeamasteroftheprinciples.Sans Bricolage
  78. 78. Thisisallkosher.Sans Bricolage
  79. 79. Wrapping Up
  80. 80. Creating digital productsis an interdisciplinaryundertaking. Equally, theprocess we use shouldalso embrace diversemethods where theymake sense.
  81. 81. Sample Pro-Services UX Bricolage•  Roles: T-shaped people•  Lean Research: Asking why before what•  UCD Backlog: Story maps•  Collaborative Visioning: Design studios•  Models: Art boards, key archetypes•  MDP: Experience criteria•  Implementation: Lean validation
  82. 82. Resources I wish we had 4 years ago.
  83. 83. Erik von Stackelberg@stackelbergThank you!Myplanet Digitalmyplanetdigital.com@myplanetdigital
  84. 84. UX Lessons fromthe USSR: TheTrouble withManifestos
  85. 85. Dwight D. Eisenhower says:“In preparing for battle I havealways found that plans areuseless, but planning isindispensable.”
  86. 86. Sun Tzu says:“Strategy without tactics is theslowest route to victory. Tacticswithout strategy is the noisebefore defeat.”
  87. 87. On ManifestosMacGuyver Momenthttp://www.youtube.com/watch?v=L9L0gVzOLds2:05
  88. 88. Items•  MAKEITUSEFULFORTHEAUDIENCE.•  MAKETITENTERTAINING.•  Moreanecdotes?•  Todo:mineresponsivedesignforquips./•  Intro,Framing•  5min MPD/ErikIntro•  5min Argument:Manifestos,valuesystemsareproductsofmetanarratives.Peoplecommitsoheavilytoaparticularideologyorliteralapproach(fundamentalism)thattheycansometimesforgettheintention(USSR/marxismhistoryhere.)Bricolageinhibitsfundamentalismbecauseitexposesustootherapproachesconstantly.Troublewithmanifestosisactuallytroublewithfundamentalism.Fundamentalism(Stalin)—>Moderates(selectivechurchgoers—don’tdoeverything)—>Bricoleurs(usingthepiecesthatmakesensebutactuallyaddingtheirowntoo)(Canadians).Giveartexample?Realists,Modernists,Postmodernists?•  5min Argument:Bricolage5min,postmodernvideo.Bricolageastheoppositeoffundamentalism.Usewhatworks.•  Agile,Waterfall,UCD,TheManifestos
  89. 89. Leanvalidation.Process: Implementation
  90. 90. DesignspikesProcess: Implementation

×