How To Win Designers And Influence Developers
summary
Claims three concrete team practices that change outcomes: stop criticizing after an intern uploads print‑resolution images instead of web ones for thousands of assets the team renames files fixes badly named scripts and writes step‑by‑step export instructions to prevent repeats. It also uses give credit via pull request comments, and ask questions early to avoid impossible designs. Missing deadlines get solved by explicitly requesting more hands. These tactics reduce bugs, rebuild trust, and speed delivery.
AI-written summary · about
chapters (9)
- 0:00Managing creative teams
- 2:15Happier teams better products
- 4:43Lessons from Carnegie
- 7:55Power of praise
- 10:42Focus on what you control
- 14:13Questions as a weapon
- 17:49Summary and the importance of not being a jerk
- 19:14Live demo: bad design ideas
- 21:54Homework and closing
