How They Work Better Together: Lean UX, Agile Development and User-Centered Design
summary
Claims that design, dev and product iterate together using sketches, quick prototypes and live fixes rather than waterfall deliverables; tools actually used include Ruby Motion iPad app, Bluetooth LE sensors (off‑the‑shelf node variable tech) and Silverback for 20–30 minute usability sessions. Teams extract reusable UI like a timeline and ship a living styleguide (Wilde/Kevlar as Ruby gem or Bower package), fix small production pain points immediately, and measure clicks and abandonment to prove changes work.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:20Experience Matters
- 4:06Building Codes
- 4:56Waterfall
- 8:05Lean UX
- 8:56Agile
- 10:24Lean Startup
- 14:13Working in Parallel
- 15:58Mental Models
- 19:55Just in Time
- 22:11Interaction Paradigm
- 23:23The Mad Dash
- 25:27Design Drift
- 27:26Project Management Office
- 28:25UserCentered Design
- 30:28User Testing
- 31:01Leading Questions
- 31:44What Should We Do
- 32:06Stop Using Agile
- 32:34Google Analytics
- 32:59Love your users
- 33:24No more silos
- 34:06Pull request workflow
- 34:30Read some books
- 35:15The Getaway Car
related talks
54mAgile UX - How to Combine Agility with Usability
33mIs Lean UX Agile’s Brain? How Lean UX Fixes Common Agile
28mCreating Better Products Together. UX and Engineering Working in Harmony
49mUX and an Agile Development Process
59mLean UX Development: Approach and Toolkit
34mThinking more product: Moving from Scrum to dual-track Agile
02mUXDX
05mIntervista