Last reading on 4th Jan 2022

My notes:

This title drew my attention after a conversation with my line manager (a business-oriented director of products, so not a designer, not a developer). I was trying to explain to him my approach to the design work and he looked at me a little worried saying that everyone has their own way to approach this work... meaning it's not easy to handle this situation. This is similar to the author's initial question in this book while having a conversation with one of his clients: “Our tech teams are learning Agile. Our product teams are learning Lean, and our design teams are learning Design Thinking. Which one is right?".

Jeff Gothelf's recommendations:1. Work in short cycles2. Hold regular retrospectives3. Put the customer at the center of everything4. Go and see5. Balance product discovery with delivery work by only testing high-risk hypotesys6. Do less research, more often7. Work (and train) as one balanced team8. Radical transparency9. Review your incentive structure (and performance management criteria)10. Make product discovery work a first-class citizen of your backlog

Cross-functional teams should master bits of all the methodology and focus on satisfying customer needs, collaborating to create compelling experiences, and continuously improving them.