Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
In my experience there are a few parts to the change. First we need to shift the definition of team success from pushing code to production (output) to achieving the team goals (outcomes). The constant drum beat of launching steps, and seeking user/business evidence helps drive the point home. Second, we want team members to have plenty of context: users and their needs, business rationale, competitive situation, and more. The context helps team members understand what makes sense and what doesn’t, and eliminates the need to spoon-feed them with bite-sized, detailed requirements.
Evidence-Guided
Itamar Gilad
Key Results: While the objective is the problem to solve, the key results tell us how we define success. And it's essential that we define success by business results (aka outcome) and not simply activity or output.
Empowered
Marty Cagan and Chris Jones
The kernel of a strategy contains three elements: 1. A diagnosis that defines or explains the nature of the challenge. A good diagnosis simplifies the often overwhelming complexity of reality by identifying certain aspects of the situation as critical. 2. A guiding policy for dealing with the challenge. This is an overall approach chosen to cope with or overcome the obstacles identified in the diagnosis. 3. A set of coherent actions that are designed to carry out the guiding policy. These are steps that are coordinated with one another to work together in accomplishing the guiding policy.
Good Strategy/Bad Strategy
Richard Rumelt
...catch up on these, and many more highlights
Readwise