Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
However, if it's the first time they have worked on this problem, then they will likely need some time to learn the space, start collecting some data to establish a baseline, and get a sense of what the possibilities are. In this case, encourage the team to jump in and not get stuck in paralysis by analysis, and acknowledge with them that they will learn much more as they progress, and that the confidence level will, of course, be low in this first quarter because they are still learning what they don't know.
Empowered
Marty Cagan and Chris Jones
Other teams, however, put off doing the unglamorous work of removing their dependencies and instrumenting their systems. Instead, they focused too soon on the flashier work of developing new features, which enabled them to make some satisfying early progress. Their dependencies remained, however, and the continuing drag soon became apparent as the teams lost momentum.
Working Backwards
Colin Bryar and Bill Carr
Let’s be honest. Scaling work isn't the shiniest, sexiest, or most visible thing internally and externally. In most orgs, when you do scaling work you don't get recognized for it in the same way as launching a new feature. This leads individual PMs and PM orgs to a mentality that scaling work isn't real product work. ***The reality is: you don't get recognized for doing scaling work, but when you don't do it, you will get recognized in a very negative way.***
> "*One small way Facebook rewards scaling work is by featuring a ‘Fix of the Week.’ Every week, Mark invites someone to discuss an important fix at the all-hands meeting which gives the company an opportunity to celebrate the critical, necessary work that often goes under-appreciated."* ***-* Ravi Mehta**, **former CPO at Tinder, Product at Facebook, Tripadvisor**
Product Work Beyond Product-Market Fit
Fareed Mosavat & Casey Winters
...catch up on these, and many more highlights
Readwise