Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
In my experience there are a few parts to the change. First we need to shift the definition of team success from pushing code to production (output) to achieving the team goals (outcomes). The constant drum beat of launching steps, and seeking user/business evidence helps drive the point home. Second, we want team members to have plenty of context: users and their needs, business rationale, competitive situation, and more. The context helps team members understand what makes sense and what doesn’t, and eliminates the need to spoon-feed them with bite-sized, detailed requirements.
Evidence-Guided
Itamar Gilad
A product strategy is your plan for creating the most value possible for your users and your company. And you do this by focusing your time on a small set of really high impact work, rather than diluting your efforts across all the different things you could potentially do.
Product Growth Newsletter
Akashi Gupta
Every item on the roadmap should also be tied back to the rationale of why we are doing it and how it will further the business.
Product Operations
Melissa Perri and Denise Tilles
...catch up on these, and many more highlights
Readwise