Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
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
This is the most important thing to remember about using statistics effectively. Statistics are rarely meaningful in and of themselves. Statistics will, and should, almost always be used to illustrate a relationship. It’s more important for people to remember the relationship than the number.
Made to Stick
Chip Heath and Dan Heath
Next, agree upon metrics of success. Eric Ries is great at this, so read his books The Lean Startup and The Startup Way to learn his in-depth methods for what he calls “Innovation Accounting.” But in short, the small team needs a set of metrics to define what a successful experimental outcome looks like. Note, these aren’t long-term business metrics; these are short-term experimental outcomes. Eric calls it validating your blind-faith assumptions.
Ask Your Developer
Jeff Lawson
...catch up on these, and many more highlights
Readwise