Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
start thinking in outcomes rather than outputs. That means rather than defining your success by the code that you ship (your output), you define success as the value that code creates for your customers and for your business (the outcomes). Rather than measuring value in features and bells and whistles, we measure success in impact—the impact we have had on our customers’ lives and the impact we have had on the sustainability and growth of our business.
Continuous Discovery Habits
Teresa Torres
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
Map out the steps each actor has to take for anyone to get value from the solution. Be specific. What does each actor need to do in order for someone to get value from the solution?
Continuous Discovery Habits
Teresa Torres
...catch up on these, and many more highlights
Readwise