Chasing Quality
summary
Argues that quality is the overlap of form, function and feeling and that real quality shows when you can share a screenshot of what shipped rather than a mockup. Recommends concrete tactics: learn enough to collaborate with engineers, use quick prototypes to bring people on the journey, set shared principles to push back on bad ideas. Cites a Twitter poll with 55% rarely or never satisfied and describes building a camera effects platform and an effects gallery that just launched to prove the approach works.
AI-written summary · about
chapters (25)
- 0:00CHASING QUALITY George Kedenburg III, Framer Loupe 2019
- 1:17CREATION TEAM
- 4:08quality is elusive
- 4:21okay really tho, what is quality?
- 5:14what are we missing?
- 7:02everyone is on the same team
- 7:21assume good intent
- 7:52designers should code!
- 9:24think logically
- 9:46collaborate better
- 10:16we did it!
- 10:37this is what we're missing.
- 12:09let people in
- 12:38relationships make quality possible
- 13:19what do these have in common?
- 15:11have principles
- 15:36bad ideas
- 16:22great ideas need clear communication
- 17:05a crash course in design communication
- 17:16what is the problem?
- 17:38how is it framed?
- 18:02scope your feedback
- 18:23tell AND show
- 18:53bring everyone on the journey
- 19:15your work # you
related talks
28mQuality as an attitude – From Testing to Quality Engineering to…what?
20mCrafting quality that endures
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)
49mIs your Quality on the Road to Nowhere?
21mTaste Driven Development
19mConditions for quality at scale
14mThinking of Quality as developer productivity tool
35mWhy Software Engineers Should Make Quality a Priority