Agile UX for Developers (or, Why Fluff is Stuff Too)
summary
Claim: UX decisions can’t wait until coding — making the UI early changes measurable and testable improves outcomes. Workshop uses 5-minute timebox role plays, cards from client meetings, a design studio (passive ideation + rapid sketching) and a fishbowl review to produce paper prototypes and simple donation flows. Teams sketch donate buttons on every page, project-specific giving, third-party credibility pages and visual impact maps; sketches converge quickly and reveal viability before any code is written.
AI-written summary · about
chapters (8)
- 0:00Agile UX intro
- 10:12Restaurant metaphor
- 21:36Workshop setup
- 31:53User interviews & cards
- 40:34Design Studio ideation
- 46:01Fishbowl feedback
- 57:32Agile UX reflections
- 1:00:25Closing summary
related talks
54mAgile UX - How to Combine Agility with Usability
36m"UX for Developers, Seriously!"
49mUX and an Agile Development Process
49mCo-creating with UX and Software
41mIntegrating User Experience and Agile
24mOvercoming Resistance: UX Practices in Agile Teams
36mMixing Lean UX & Agile Development
47mExperience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt
