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
*Staff Engineer* introduces an approach I call [Take five, then synthesize](https://lethain.us20.list-manage.com/track/click?u=f7003ed301623a88fab7cf783&id=1e5e9d0544&e=a102c6f471), which does strategy by:
1. Documenting how five current and historical related decisions have been made in your organization. This is an extended exploration phase
2. Synthesizing those five documents into a diagnosis and policy. You are naming the implicit strategy, so it’s impossible for someone to reasonably argue you’re not empowered to do strategy: you’re just describing what’s already happening
Who Gets to Do Strategy? @ Irrational Exuberance
Will Larson
I often look at the Objective and see if there are words that could be quantified. In the example above, “love” becomes NPS4 and “sales” becomes referrals. Both are measurable outcomes.
Radical Focus SECOND EDITION
Christina Wodtke
...catch up on these, and many more highlights
Readwise