Engineering Better Design Relations
summary
Claim: better designer–developer relations produce higher-quality, less wasteful apps. Evidence: one company abandons Basecamp, adopts slack and figma, and creates a git-backed creative repo for assets so commits replace lost Dropbox threads. Concrete practices: agree on common language, define what pixel-perfect means per role, run surveys to find pain points, and give technical reasoning during critique. The change reduces lost assets and speeds handoffs, so the fix demonstrably works.
AI-written summary · about
chapters (6)
- 0:00Start
- 4:02Respect Understand Learn
- 10:57Find the Pain Points
- 11:25How do others feel?
- 18:57Critique is part of the design process
- 19:59Give technical reasoning.
related talks
23mHow To Win Designers And Influence Developers
18mCollaboration in product design
29mEffective design and engineering collaboration
25mWhy Designers & Developers Need a Common Language
30mBuilding Better Products Faster
23mDevelopers, start designing!
22mShould devs design?
26mImportance of supporting designer & developer creativity