I call it debugging design, that's like the title of the bucket I'm writing at the minute. And if I can teach them how to get something up and look at a website and actually debug it in terms of what is wrong on this page? Something's not right. How can they identify what's wrong and fix it? Similar to how they work in code, you know, they, they, something, or something else. It really is just a case of identifying the issues and fixing them.
Laura Elizabeth believes developers can learn design. She articulates the importance of reflecting on our users’ needs more than our personal tastes. She touches on how making a product makes us better designers. She also inspires us to always be genuine in our dealings with our customers if we want to build (and keep) trust.
- Secret Identity (4:05)
- Origin Story (9:55)
- Biggest Superhero (13:32)
- Biggest Failure (16:23)
- Design Superpower (20:54)
- Transition from Freelance to Product (23:04)
- Design Kryptonite (26:13)
- Design Superhero Name (29:34)
- Should Developers Design? (34:10)
- Habit Of Success (42:59)
- Invincible Resource (48:55)
- Book Recommendation (52:09)
- Listener Question (54:58)
- Best Advice (59:39)
- Connect & Keep Up (64:08)
Check out the detailed show notes and Eli Jorgensen’s astonishing superhero artwork at userdefenders.com/040
This episode is brought to you by Adobe, makers of XD. Try it free at userdefenders.com/xd
Get your FREE audiobook from Audible at userdefenders.com/freebook. No commitment. Cancel in 30 days, and you won't be charged. The book is still yours to keep.