UX designers /developers collaboration anti patterns
summary
Covers three concrete anti‑patterns and concrete fixes: the assembly line where external UX hands off docs and development wastes weeks when requirements change; the groundhog day incremental trap solved by investing in a shared design system and interface inventory (screenshot every page, extract components, merge duplicates); and lost in translation prototypes that mix investor demos with engineering specs. Recommends including developers in research, naming prototype fidelity and purpose, building a component library (modular Lego set) and using explicit design principles so delivered UIs match what was estimated.
AI-written summary · about
chapters (15)
- 0:00UX designer-dev collaboration
- 1:29Why collaboration matters
- 4:45Anti-patterns defined
- 5:51Assembly line anti-pattern
- 8:11Failed collaboration case
- 9:58Avoiding anti-patterns
- 11:56Shifting to exploratory mindset
- 13:01Devs in UX research
- 16:54Groundhog day anti-pattern
- 19:49Design systems complexity
- 20:34Improving design system processes
- 25:41Lost in translation with prototypes
- 29:17Prototype fidelity
- 32:52Recommended books
- 35:18Closing remarks & Q&A
related talks
49mCo-creating with UX and Software
40mHow to make UX & Devs build killer products
30mBuilding Better Products Faster
51mUX + Engineering: A Tale of Two Cities
15mHoly War between Designers & Developers
32mPairing with designers to create a seamless user experience
36m"UX for Developers, Seriously!"
37mLearning UX Design & Visual Design Basics To Improve Web Developer and Designer Collaboration