Development and design: all together like Fuenteovejuna
summary
The talk addresses the persistent gap between design and front-end development, naming the problem that developers often receive a finished, client-approved design that constrains implementation and budgets. It advocates for involving developers early during conception, research and design, describes benefits of collaborative workflows for digital-product development, and offers practical tips to improve communication and daily handoff processes between designers and developers.
AI-written summary · about
chapters (32)
- 0:00Welcome
- 3:13Introduction
- 4:37Old workflow
- 8:50Static design pain
- 10:14Sketch revolution
- 12:40Figma bridge
- 15:48Figma collaboration
- 17:09Penpot open source
- 18:32Design order best practices
- 20:37Design components and states
- 21:42Production copy issues
- 23:04Current workflow
- 25:30Design-dev gaps
- 28:16Early dev involvement
- 29:18Process simplification
- 30:44Shared collaboration spaces
- 31:48Pair designing
- 33:11Motivation and docs
- 33:53Tech research with design
- 35:38Design decision priorities
- 36:43Team alignment and vision
- 37:47User value delivery
- 38:28Common language and communication
- 39:555-day design method
- 41:20Early collaboration benefits
- 43:05UX engineer role
- 45:30Process changes for results
- 46:13Closing
- 46:34Q&A: initial controversy
- 47:37Q&A: client changes
- 48:41Q&A: tools and learning
- 50:27Q&A: business involvement
related talks
45mDESIGN 🤝 DEVELOPMENT: ALL TO ONE Fuenteovejuna
31mDesign Through a Developer's Eyes
35mDesign vs Development: The Miracle of the Match Between Two Opposite Poles
40mDiseño y desarrollo y viceversa
45mHow designers trick you every day
36mThe Developers, the Daily War
25mDesigners + Developers = Best Friends Forever?
22mDesigners vs Developers: What Product unites let nothing divide