A batch of the best highlights from what Felicity's read, .
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
I emphasize to product people all the time that there is no single product discovery process just as there is no single product development/delivery process. There are many different discovery processes, all for different situations. For example, a [discovery sprint](https://svpg.com/discovery-sprints/) looks very different from customer discovery, but you should be skilled at both.
Moreover, it’s important to realize that it’s not about process. It’s much more about putting in place the necessary culture, and training your team on the critical techniques.
Process vs. Model
Marty Cagan
Many companies like to describe themselves as winning through operational effectiveness or customer intimacy. These sound like good ideas, but if they don’t translate into a genuinely lower cost structure or higher prices from customers, they aren’t really strategies worth having.
Playing to Win
A. G. Lafley, Roger Martin, A.G. Lafley, Roger L. Martin