Four distinct layers, often conflated: Mission is why the company exists (enduring, decades-long, unchanging). **Product Vision** is what the company will do over a defined horizon to bring the mission to life. **Product Strategy** is how the vision gets executed. **Roadmap (Feature/Project List)** is near-term execution detail.
A mission alone makes a poor vision because it doesn't constrain choices. Example: "We are in business to save our planet" is a great mission but a crappy vision — it inspires but puts no "muscle on the bones" to align teams around specific choices. Google's "organize the world's information" has the same problem: a vision needs enough specificity to align teams instead of scattering them across everything the mission could justify.
Kaiser Permanente's mission, "quality affordable healthcare," drove its product vision "Get Care Now," a telehealth-focused vision that shipped just before the COVID-19 pandemic — an example of a vision that's a specific derivation of the mission rather than a restatement of it. John Deere's "farm of the future" vision is an instance of a recurring naming pattern across industries — "smart [domain] of the future" — that shows up whenever an established company builds a technology-forward vision on top of an old-economy mission.
Janakiraman frames the mission→vision→strategy→roadmap hierarchy in terms of resource allocation: mission and vision express purpose (why the company/team exists and where it's going), while strategy is the layer that forces an explicit choice about where to deploy scarce resources (people, time, attention) for maximum impact, before the roadmap turns that choice into an ordered execution list. He illustrates the stakes of getting the strategy layer right with the Resonance Analogy for Strategy (Frequency Amplification): effort aimed at the wrong frequency dissipates regardless of how hard the team works, while effort aimed at the resonant frequency compounds.