How to make UX & Devs build killer products
summary
Compares two concrete allocation patterns — the UX agency model vs embedding a designer — and reports that CB Labs uses a hybrid with a spoke designer per team across seven development teams; UX starts just before development to break the ice, prototypes in InVision and Framer to validate quickly, and keeps a visible UX column on the board. Defines tactics that reduce rework: designers attend standups and retros, include UX in Definition of Done, and route blockers through the scrum master.
AI-written summary · about
chapters (10)
- 0:00Introduction and talk overview
- 1:50Imagining a house-building analogy
- 5:50Introducing the speaker and background
- 9:25Allocating UX resources in teams
- 16:52Choosing the right UX allocation model
- 21:55Aligning UX and development work
- 27:14Overcoming collaboration challenges
- 32:15Encouraging designer participation
- 34:03Results and closing remarks
- 34:50Q&A session
related talks
49mCo-creating with UX and Software
51mUX + Engineering: A Tale of Two Cities
32mPairing with designers to create a seamless user experience
45mGreat UX, Despite Agile: How to Get the Best Out of Your Design Team in Agile Projects
36mUX designers /developers collaboration anti patterns
24mPanel Talk: Integrating UX for Improved Product Development
41mDesignOps - How I Built UX Teams from Scratch in a Company
30mBuilding Better Products Faster
