Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
To do this, members continued to run the service manually until they had clear evidence that automation was needed, and then they built only the smallest amount of software that would address the need.
Sense and Respond
Jeff Gothelf, Josh Seiden
Product stickiness (daily/weekly/monthly active users [DAU/WAU/MAU]) Frequency (e.g. number of logins for a given customer) Feature adoption rates Feature retention rates Product usage data - Depth (feature usage by time, funnel, and more) - Breadth (could be the number of active users)
Product Operations
Melissa Perri and Denise Tilles
• **Feature Work -** Creating and capturing value by extending a product's functionality and market into incremental and adjacent areas.
• **Growth Work -** Creating and capturing value by accelerating adoption and usage by the existing market.
• **Scaling Work -** Focusing on bottlenecks to ensure the team can continue to move forward and take on new levels of feature, growth, and product-market fit expansion work.
• **Product-Market Fit Expansion -** Increasing the ceiling on product-market fit in a non-incremental way by expanding into an adjacent market, adjacent product, or both.
> *"One of the most common conflicts I've seen is when product leaders try to apply a single development process, measure of success, and strategy to all product work. For instance, while some of the steps can be similar, growth and feature work are fundamentally different and a lot of energy is wasted trying to make them all fit into the same process, success metric, and approach."* **-** **Fareed Mosavat**, **former Director of Product at Slack**
Product Work Beyond Product-Market Fit
Fareed Mosavat & Casey Winters
...catch up on these, and many more highlights
Readwise