Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
For this reason we built the Tabbed Inbox through a series of build-measure-learn loops, which are called Steps in GIST. There were usability tests, longitudinal studies, fishfood and dogfood, labs, and partial launches. Each step generated a more complete version of the product, but also gave us new evidence, which helped build our confidence in the idea and get more funding. We used what we learned in each step to course-correct and improve the idea. The feature we eventually launched was profoundly better than the one we started with.
Evidence-Guided
Itamar Gilad
Product strategy is selecting the right problems to solve and breaking them down into actionable opportunities with measurable objectives.
Let’s unpack that...
• **'Right problems**' because we must prioritise, we can't solve everything at once
• '**Problems**' not solutions, so teams have the freedom to discover solutions themselves
• '**Actionable opportunities'** so teams know what to do next
• **'Measurable objectives**' so teams focus on outcomes and can learn from results
Strategy is focus. Product strategy purposefully narrows attention to prevent distraction. By aligning limited resources toward a single focal point, we dramatically increase the odds of meaningful breakthroughs.
The purpose of Product strategy is to create clarity at the team level. It shifts conversations from "what do stakeholders want us to build?" to "how do we solve the problem we all agreed was most important?". Framing expectations as expected outcomes helps to empower teams**.**
Product Strategy as a Living Conversation
Product Breaks
When it came to goal setting, Andy Grove felt strongly that less is more: The one thing an [OKR] system should provide par excellence is focus. This can only happen if we keep the number of objectives small ….
Measure What Matters
John Doerr
...catch up on these, and many more highlights
Readwise