Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
If the ultimate business goal is revenue, the product team's main metrics can’t be about revenue. This is because the primary function of OKRs is not to qualify for a bigger bonus, a promotion or personal validation. They should be used as a tool unjudgementally to *indicate* whether the team’s work is generating the right outcome for users. It gives clues to whether progress made is resonating with customers.
The focus on customer centric metrics eliminates the distraction and worry for the product team. It means they can be laser focussed on building the sharpist product to solve the specific user problems that have been identified by the team to be the most important to solve.
We're Zipping Up Into a New Operational Onesie.
Product Breaks
A project begins with a vision that is, at best, a vague image of the glorious thing the project will become. Planning is pushing the vision to the point where it is sufficiently researched, analyzed, tested, and detailed that we can be confident we have a reliable road map of the way forward. Most planning is done with computers, paper, and physical models, meaning that planning is relatively cheap and safe. Barring other time pressures, it’s fine for planning to be slow. Delivery is another matter. Delivery is when serious money is spent and the project becomes vulnerable as a consequence.
How Big Things Get Done
Bent Flyvbjerg and Dan Gardner
The concept of product discovery emerged because smart companies saw the waste in working this way. They wanted to ensure that they had sufficient evidence to believe that the solution they asked their engineers to build would successfully solve the customer or business problem it was intended to solve.
...catch up on these, and many more highlights
Readwise