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
Don’t Jump Straight to Your Conclusions When preparing for a meeting with stakeholders, we tend to focus on our conclusions—our roadmap, our release plan, our prioritized backlog. More often than not, this is exactly what our stakeholders are asking us to share. Even in companies that espouse a focus on outcomes, we still tend to spend most of our time talking about outputs. The challenge with this approach is that our stakeholders often have their own conclusions. It’s easy to have an opinion about outputs. We all have our own preferences about how a product or service should work. When we anchor the conversation in the solution space, we encourage our stakeholders to share their own preferences. However, these preferences aren’t always grounded in good discovery. After all, it’s our job to do discovery, not our stakeholders’.
Continuous Discovery Habits
Teresa Torres
Regardless of the timeframe you’re working to, then a solid product strategy has 7 major sections:
1. **Objective** - what is the challenge we are responding to?
2. **Users** - what does our audience need?
3. **Superpowers** - where can we create unique value?
4. **Vision** - what is the future we are building?
5. **Pillars** - what are the main themes of work to get there?
6. **Impact** - does our planned work meet our objective?
7. **Roadmap** - what are we doing next, and how do we share progress?
How to Write a Product Strategy in 1 Day / 1 Week / 1 Month
Aakash Gupta
...catch up on these, and many more highlights
Readwise