Experience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt
summary
Argues that embedding lightweight research and an experience map into quarterly agile cadence turns UX debt into actionable backlog items; uses a one‑month recruitment window, weekly readouts, mid‑sprint presentations and video clips of users to convince devs. Runs an exploratory user study with 20 participants and two researchers, uses sticky‑note workshops and a business model canvas to map top five features, surfaces real bugs (missing HTTPS, broken flows) and assigns ownership so fixes happen before release rather than piling up as support tickets.
AI-written summary · about
chapters (8)
- 0:00Introduction to experience maps
- 3:59Understanding agile and UX debt
- 15:52Fragmenting research in agile
- 23:47Business model canvas for UX
- 29:26Building experience maps
- 35:10Applying experience maps in projects
- 38:44Key takeaways and conclusion
- 39:46Q&A session
related talks
40mUser Experience for Product Managers
41mMapping Experiences: From Insight To Action
49mCo-creating with UX and Software
49mUX and an Agile Development Process
01h 01mAgile UX for Developers (or, Why Fluff is Stuff Too)
41mIntegrating User Experience and Agile
40mAdjusting UX Research for an Agile world
24mOvercoming Resistance: UX Practices in Agile Teams