Adjusting UX Research for an Agile world
summary
Argues that research must be embedded and scheduled — aim for a recurring slot (example: every other Thursday) and put UX work in the same backlog as engineering; recommends one researcher serving multiple teams but ideally embedded UX people per cross-functional team, and using tools like Powwow for self-scheduling and a shared notes spreadsheet (Homer Sharron style). Suggests lean hypotheses (e.g. 8 of 10 participants find X), small rounds (5 participants, reuse studies), share facilitation across the team, and act on findings (autosave story changed roadmap).
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:52Challenges of UX in Agile
- 5:05Team structure for UX research
- 9:42Convincing stakeholders about UX
- 10:48Scheduling research in sprints
- 15:46Recruiting participants efficiently
- 16:29Planning quick research studies
- 20:46Involving the whole team in research
- 23:18Analyzing and integrating findings
- 31:09Documentation and backlog integration
- 33:59Final thoughts and Q&A
related talks
07mAdventures in Agile Research
41mIntegrating User Experience and Agile
47mExperience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt
24mPanel Talk: Integrating UX for Improved Product Development
28mThe Secrets and Synthesis of Successful UX Research
46mStarting Up Research
33mA Scrappy UXer's Tale of Effective Low-Tech, Low-Prep, Quick Turnaround UX Research
49mCo-creating with UX and Software