Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
• **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
In product development, avoiding these pitfalls requires not only defining the right metrics but also maintaining a willingness to revisit and refine them. Metrics should not be static; they must evolve as the context and the goals change. Moreover, leaders must remain vigilant to ensure that the pursuit of those metrics does not lead to a loss of purpose or values. Sometimes it means slowing down, adding friction, or choosing a less profitable path because it’s the right one.
Unintended Consequences - by Mike Fisher
Unintended Consequences
Mike Fisher
For the most part, metrics are reviewed daily by their owners and weekly in the WBR, so that expected fluctuations become familiar and exceptions stand out.
Working Backwards
Colin Bryar and Bill Carr
...catch up on these, and many more highlights
Readwise