UX Lessons from the USSR: The Trouble with Manifestos with Erik von Stackelberg
•
1 j'aime•849 vues
This document discusses combining different processes for developing digital products, known as "process bricolage." It advocates embracing diverse methods from processes like Agile, waterfall, and user-centered design. The document summarizes key aspects of different processes and roles, and proposes a sample bricolaged process incorporating elements like lean research, user stories, design studios, models, experience criteria, and lean validation in implementation. It acknowledges arguments against bricolage but asserts that creating digital products requires an interdisciplinary approach and that the development process should also combine methods where sensible.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à UX Lessons from the USSR: The Trouble with Manifestos with Erik von Stackelberg
Similaire à UX Lessons from the USSR: The Trouble with Manifestos with Erik von Stackelberg (20)
Plus de FITC
Plus de FITC (20)
Dernier
Dernier (20)
UX Lessons from the USSR: The Trouble with Manifestos with Erik von Stackelberg
- 2. UX Lessons from the USSR: The Trouble with Manifestos
- 6. Erik von who? Erik von Stackelberg, Creative Director @stackelberg
- 7. The Argument
- 8. Creating digital products is an interdisciplinary undertaking. Equally, the process we use should also embrace diverse methods where they make sense.
- 9. Goals, in order of usefulness… • Discussion for process wonks. • Survey of techniques. • A sample process for building digital products (no patents pending!)
- 10. Disclaimer • This isn’t sexy. • This is anecdotal. • I’m not from Russia. • I speak really quickly.
- 11. On Manifestos
- 13. Wikipedia says: “A manifesto usually accepts a previously published opinion or public consensus and/or promotes a new idea with prescriptive notions for carrying out changes the author believes should be made.”
- 19. The Agile Manifesto (Abbreviated) • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan
- 20. A Really Reductive Explanation of Agile
- 22. A Really Reductive Explanation of Waterfall
- 29. Proposed Spectrum of Interpretation • Fundamentalist • Dogmatist • Moderate
- 33. On Bricolage
- 35. Wikipedia says: “…bricolage is the construction or creation of a work from a diverse range of things that happen to be available, or a work created by such a process.”
- 36. A spectrum of interpretation. • Fundamentalist • Dogmatist • Moderate • Bricoleur
- 41. Key Roles & Team Structure
- 43. Team Structure There’s no “I” in team. On mixing the traditional creative process with some Agile flavouring.
- 48. Key Roles Balancing expertise and empathy. On modifying traditional Agile roles to share responsibility but maintain diversity.
- 49. Key Roles
- 53. Process
- 55. Process
- 56. Process: Discovery On adding an early dash of UCD research and Lean validation into the Agile framework.
- 59. Process: Product Definition On mashing some user- centered design planning into the Agile framework.
- 64. Storymaps arehella useful. Jeff Patton Process: Product Definition
- 68. Process: UX Definition On adding models into the mix to net waterfall- like client comfort and design vision (and Lean early validation).
- 78. Defy the mishmash GUI. Process: UX Definition
- 82. There’smoreto life than being ridiculously good-looking. Process: UX Definition
- 85. Process: UX Definition On MacGyvering experience criteria into the backlog.
- 89. Process: Implementation On integrating UCD practices into Agile sprints.
- 92. Creating digital products is an interdisciplinary undertaking. Equally, the process we use should also embrace diverse methods where they make sense.
- 93. Sans Bricolage
- 94. Sans Bricolage There are arguments against process bricolage. Here are some.
- 100. Wrapping Up
- 101. Creating digital products is an interdisciplinary undertaking. Equally, the process we use should also embrace diverse methods where they make sense.
- 102. 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
- 103. Resources I wish we had 4 years ago.
- 104. Erik von Stackelberg @stackelberg Thank you! Myplanet Digital myplanetdigital.com @myplanetdigital
- 105. UX Lessons from the USSR: The Trouble with Manifestos
- 106. Dwight D. Eisenhower says: “In preparing for battle I have always found that plans are useless, but planning is indispensable.”
- 107. Sun Tzu says: “Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat.”
- 109. Items • MAKEITUSEFULFORTHEAUDIENCE. • MAKETITENTERTAINING. • Moreanecdotes? • Todo:mineresponsivedesignforquips./ • Intro,Framing • 5min MPD/ErikIntro • 5min Argument:Manifestos,valuesystemsareproductsofmetanarratives. Peoplecommitsoheavilytoaparticularideologyorliteralapproach (fundamentalism)thattheycansometimesforgettheintention(USSR/marxism historyhere.)Bricolageinhibitsfundamentalismbecauseitexposesustoother approachesconstantly.Troublewithmanifestosisactuallytroublewith fundamentalism.Fundamentalism(Stalin)—>Moderates(selectivechurchgoers —don’tdoeverything)—>Bricoleurs(usingthepiecesthatmakesensebut actuallyaddingtheirowntoo)(Canadians).Giveartexample?Realists, Modernists,Postmodernists? • 5min Argument:Bricolage5min,postmodernvideo.Bricolageasthe oppositeoffundamentalism.Usewhatworks. • Agile,Waterfall,UCD,TheManifestos