Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
The philosopher and educator John Dewey went a step further: “We do not learn from experience … we learn from reflecting on experience.”
Here are some reflections for closing out an OKR cycle:
• Did I accomplish all of my objectives? If so, what contributed to my success?
• If not, what obstacles did I encounter?
• If I were to rewrite a goal achieved in full, what would I change?
• What have I learned that might alter my approach to the next cycle’s OKRs?
Measure What Matters
John Doerr
If you’re only responsible for a part of the user experience, and not the whole thing, then you should think through the core benefits you can offer users (i.e. the value proposition from JTBD), and how you can reinforce these benefits in ways that competitors will find difficult to replicate.
This can take the format:
*[Imagined feature] might offer [core customer benefit], whilst being difficult to copy because [hard-to-copy superpower].*
**Example**
**Smart locks** on home dramatically improve guest experience (never lose key) and host safety (change code for every stay). This is difficult for competitors to copy because integrating hardware and software at scale and cross-platform is a huge task.
How to Write a Product Strategy in 1 Day / 1 Week / 1 Month
Aakash Gupta
Using OKRs helps you move the team from output thinking to outcome thinking. It may take a few tries, but you will be more successful once you focus on outcomes.
Radical Focus SECOND EDITION
Christina Wodtke
...catch up on these, and many more highlights
Readwise