Should Designers?
summary
Claim: limited code skills change workflow — designers learn font sizes and colors then use the web inspector and JSON configuration files to drive UI and tokens. Teams break work into components with element collages and short cross‑disciplinary hackathons, shipping standalone verticals (Verywell, The Balance, The Spruce) at about three months per vertical. Tools used: Sketch → JSON, design tokens, React Sketch, Bodymovin. Outcome: designers edit configs and code, infinite‑scroll tests increase time on site, collaboration speeds delivery.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:57Gantt Charts
- 5:49How Teams Should Work Together
- 8:35Nike Better World Site
- 9:58Designers Are Notorious for Designing Too Big and at the Wrong Time
- 12:20Heavily Requested Features
- 18:55Have Fun
- 24:49Font Sizes
- 27:21Learn Json
- 28:09Design Tokens
- 35:078 Point Grid
- 42:30Agile Manifesto
- 47:01What Elements of Design Could Developers Learn in Order To Collaborate Better
- 50:07The Difference between Being Responsible and Being Accountable
- 59:21Pricing Design
related talks
14mRethinking Designer-Developer Collaboration
33mA Modern Designer's Workflow
15mModern Approach to Designer ❤️ Developer Collaboration
20mDesign Systems for the Rest of Us
29mDesigning with Code in Mind
40mHow to optimise the workflow between designers and developers using design..
18mDesign Systems in Practice
23mDevelopers, start designing!