Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
**Interesting connection to AI Training / Research:** The overall approach / objectives of the WBR seem very similar to how Ilya Sutskever described how they approach AI training / research. The focus is less on “new ideas,” and more on understanding the behavior of the system. Here’s the quote:
> “Coming up with new ideas is actually just a modest part of the work. Even more important is to understand the results…to understand what’s going on…figuring out the next experiment to run. A lot of the time is spent on that. Understanding what could be wrong, what could have caused the system (neural net) to produce a result which was not expected.”
The real driver of progress / execution / performance/ superior results comes *less* from the generation of the new ideas, *more* on the ability to understand WHY the outcomes are happening. To put it another way: the better you understand the system, the better your innovation and performance will be.
The Amazon Weekly Business Review - Commoncog
The Commonplace Community
I recommend teams use three different artifacts to keep track of what they are learning from their customer interviews:
1. The interview snapshot: This artifact summarizes what you learned from a single customer interview. Teams should create an interview snapshot for each interview that they conduct.
2. A comprehensive experience map: This map represents the experience of multiple customers. It’s an amalgamation of all the individual experience maps that appear on your interview snapshots.
3. An [opportunity solution tree](https://www.producttalk.org/opportunity-solution-tree/): This artifact captures any opportunities from across your interview snapshots that are relevant to your current [product outcome](https://www.producttalk.org/2020/05/product-outcomes/).
The Interview Snapshot: How to Synthesize and Share What You Learned From a Single Customer Interview
Teresa Torres
I emphasize to product people all the time that there is no single product discovery process just as there is no single product development/delivery process. There are many different discovery processes, all for different situations. For example, a [discovery sprint](https://svpg.com/discovery-sprints/) looks very different from customer discovery, but you should be skilled at both.
Moreover, it’s important to realize that it’s not about process. It’s much more about putting in place the necessary culture, and training your team on the critical techniques.
Process vs. Model
Marty Cagan
...catch up on these, and many more highlights
Readwise