Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
*Take small steps.* Rather than trying to predict outcomes, aim to test, explore, and improvise. Consider each step or action you take to be a small, brief experiment. Try something, then step back and observe what happens. Then, try again. Remember that many small steps can add up to a great big change given a little time and persistence.
Make Life Possible
Mandy Brown
Indeed, this is what has happened at AutoTrader UK, where teams are no longer funded annually to build a set of features. Instead, the organization now checks in with each team on a quarterly basis to see how it’s tracking against initiative goals. Initiative goals are quantitative and based on changing customer behavior in some way that benefits the business. Teams get funded to change these behaviors, one quarter at a time. As the quarter nears its end the company assesses, with the team, whether it’s worthwhile to continue working toward those outcomes. If so, the team gets another quarter’s worth of runway. If not, it moves on to a new initiative.
Sense and Respond
Jeff Gothelf, Josh Seiden
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