Adventures in Agile Research
summary
Only two researchers support five product teams, causing weeks-long lead times so product teams run too many surveys and mostly inconclusive A/B tests. The change is to run research days every three to four weeks, require a note‑taker and observer from the product team, do collaborative write-ups and a wash‑up the next day, and publish findings on a Trello research library. Recruitment starts by emailing existing learners (very high response); plan is to build an opt‑in panel and formalize ResearchOps.
AI-written summary · about
related talks
40mAdjusting UX Research for an Agile world
44mProduct Research as a Risk Mitigation Strategy for Product Development
46mStarting Up Research
28mThe Secrets and Synthesis of Successful UX Research
19mTerms of Engagement: Research as a Team Sport.
24mPanel Talk: Integrating UX for Improved Product Development
01h 04mDiscount Usability Testing for Agile Teams
27mUser Research for everyone