Designers vs Developers: Who is in control here?
summary
Framework maps who drives at each phase and who navigates, with concrete rules: one active driver at a time, multiple navigators to offload decisions. Cites real work—an app built with Adobe PhoneGap, a site still depending on Knockout.js, demos using Lottie—and company practice of 50% pro-bono work. Recommends documenting hard requirements (image presence, specific responsive breakpoints), prefer native controls like input type=date/select, use short Slack huddles instead of long message threads, and forbid the pocket veto of unimplemented designs.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:18Web dev in the bad old days
- 8:13Responsive design challenges
- 13:56Honest communication
- 19:16Driver and navigator concept
- 26:16UX vs UI roles
- 36:51Respecting craft
- 41:00Tools vs collaboration
- 43:12Handling difficult members
- 48:09Client-facing unity
- 50:37Recap and closing
related talks
18mWhy Designers Are so Hard to Work With
37mCoder Meets Designer: Reconciling Design (...)
23mDevelopers, start designing!
25mDesigners + Developers = Best Friends Forever?
41mThe Designers Are Coming
20mBridging the Gap between Designers and Developers
36mUX designers /developers collaboration anti patterns
38mEnough Design