Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
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
To understand how to set our strategic intents, we had to first understand what business value really means. Joshua Arnold, a business and product consultant and expert on cost of delay, uses a great model for thinking about business value,1 as shown in Figure 13-1. Figure 13-1. Framework for thinking about value, by Joshua Arnold (reprinted by permission of Joshua Arnold, © 2002)
Escaping the Build Trap
Melissa Perri
I am describing a strategy as a design rather than as a plan or as a choice because I want to emphasize the issue of mutual adjustment. In design problems, where various elements must be arranged, adjusted, and coordinated, there can be sharply peaked gains to getting combinations right and sharp costs to getting them wrong. A good strategy coordinates policies across activities to focus the competitive punch.
Good Strategy/Bad Strategy
Richard Rumelt
...catch up on these, and many more highlights
Readwise