Overcoming Resistance: UX Practices in Agile Teams
summary
Motorola Solutions teams describe embedding UX into Agile by working one sprint ahead and running dual-track agile so design and development iterate in parallel; early user testing and stakeholder syncs cut feature iterations and reduce user errors. They report concrete gains: internal use of Figma for shared designs, developers leaving comments, and a cited industry example of 26% fewer support tickets after a help‑center redesign; claim that $1 of UX can save $100 in rework motivates prioritizing UX tasks and regular pairing sessions.
AI-written summary · about
chapters (13)
- 0:00UX in Agile teams
- 1:33UX resistance hurts Agile
- 3:22Reasons for UX pushback
- 5:28Proving UX value
- 7:16Cost savings from UX
- 8:22Breaking silos designers devs
- 9:47Dual-track Agile UX dev
- 10:53Balancing speed and UX research
- 12:21Collaborative design sessions
- 13:25Designers embracing imperfection
- 14:55UX must-have not nice-to-have
- 15:39Agile and UX learning to share
- 16:22Q&A team structures
related talks
41mIntegrating User Experience and Agile
54mAgile UX - How to Combine Agility with Usability
49mUX and an Agile Development Process
49mCo-creating with UX and Software
53mThe UX of UX: Building a Culture of UX
01h 01mAgile UX for Developers (or, Why Fluff is Stuff Too)
18mAgile leadership and technical mastery, a harmonious alliance
36mMixing Lean UX & Agile Development