Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
How do you organize this way? First you begin with the customer or user—whomever is consuming your product at the end of the day. What is the value that you are providing them? Then work backward. What are the touchpoints they have with your company on the way to receiving that value? Having identified these, how do you organize to optimize and streamline that journey for them? How do you optimize to provide more value, faster?
Escaping the Build Trap
Melissa Perri
So making a thing, creating an output of some sort, is not our goal. Instead, success is the extent to which we achieve an outcome and help our customers achieve an outcome they seek.
Sense and Respond
Jeff Gothelf, Josh Seiden
All those lovely ideas you have for projects get moved into your pipeline. Pipelines are more suited to OKRs than Roadmaps. ... I’ll define Roadmaps as a plan for our desired future and Pipelines as a collection of ideas of projects that might get us to our desired future. Roadmaps have dates. Pipelines use impact/effort/confidence to prioritize the best ideas. By saying Pipelines are preferable to Roadmaps, I simply mean that Pipelines give you flexibility as you try to reach your Objective. If you call it a Roadmap but treat it like a Pipeline, that’s fine. The critical idea is that you have a long list of potential solutions to try out. ... If you have a Roadmap, you’ll want to dismantle it and put it in a Pipeline format.
Radical Focus SECOND EDITION
Christina Wodtke
...catch up on these, and many more highlights
Readwise