Lean UX Agile and lean design process Sibylle Peter, Dozentin SGI
Learning objectives Basic knowledge of Lean UX Integration of Lean UX in agile software development Challenges & Experiences in the real world (guest lecture)
Lean UX – what does it mean?
Summary Remove Waste: from documents hand off to minimal viable conversations Collaborative design: from design silo to cross-functional collaboration with marketing, product managers, QA, engineering etc. Designer: from hero to design facilitation driven by experiments and measurements
Hypothesis Software development and use brought new professions (interaction designers, information architect etc.) but the process of designing has been the same as before: Design in advance cost of being wrong remains high! Today: continuous processes needed
Foundations Lean Startup minimal viable conversations Design Thinking looking at systems, broadens the scope Agile fast iterative delivery of value
Challenge for Designers Be brave to show the work in an unfinished state Accepting the iterative nature of design: you as a team are NOT going to get it right the first time.
Principles Team culture Team organization Design process
Team Culture Moving from doubt to certainty Outcomes not output Removing waste Shared understanding No rock stars, gurus or ninjas Permission to fail (be wrong)
Team collaboration Small cross-functional teams Small (<=10), dedicated, collocated Self-sufficient & empowered Problem-focused teams
Design Process Work in small batches to mitigate risk Continuous discovery GOOB: the new user centricity Externalizing your work Making over analysis Getting out of the deliverable business
Lean UX Process
Collaborative Design Conversations around a shared vision Design Studio (collaborative design techniques) Design Systems which allow to share the work Team working agreement
What is an MVP anyway? What is the most important thing to learn first/next about this hypothesis? What is the least amount of work needed to learn that?