39:45
product vision
A product vision is a distinct artifact from mission and strategy — it is the specific, leadership-authored answer to "what will we do over the next few years to advance our mission," built from validated customer problems, corporate strategy, and a revenue path — and John Moore (SVPG) argues the real-world failure mode is not a bad vision leading a company astray but roughly 80% of companies having no real vision at all, leaving a gap between mission and yearly targets that gets filled ad hoc by projects.
Mission = why (enduring, decades-long, unchanging), Vision = what a company will do over a defined horizon to bring the mission to life, Strategy = how the vision gets executed, Roadmap = near-term execution detail.
A mission alone (e.g. Google's "organize the world's information") makes a poor vision because it doesn't constrain choices — a vision needs "muscle on the bones" to align teams instead of scattering them.
Three common misconceptions: having no vision at all; conflating vision with mission; conflating a product vision with a culture/PR-oriented "company vision."
A vision must inspire (people want to feel they're "leaving a dent on the universe") and provide focus/alignment (a "north star"); without one, companies default to incremental, revenue-only thinking.
A vision "can never be a collective enterprise" — it must be authored/filtered by the most senior product leader (CPO/CTO/VP Product), with input from CTO/CFO, while the CEO is the #1 stakeholder and, ideally, the vision's heaviest user.
Scope rule: most companies need exactly one integrated, holistic product vision; only very large multi-business-unit companies (e.g. Amazon, with AWS, retail, Alexa) warrant separate visions per unit.
Three core, non-negotiable vision ingredients: validated business and customer problems, alignment with corporate/executive strategy, and at least a glimpse of the revenue/monetization path — supplemented by a customer/business "wow" narrative and industry-trend/competitive-leapfrog framing (e.g. Gen AI today).
A vision must be audacious but calibrated to company culture — Microsoft's internally-mocked "flying car" vision video failed because it was disconnected from readiness, whereas SpaceX succeeds with an extremely long-horizon, seemingly unbelievable vision (Mars).
Vision time horizons are contested: legacy norm was 3–5 years, some companies now push for 10-year visions, but John argues faster tech change (especially Gen AI) makes shorter horizons (~18 months) more realistic, with reviews now happening roughly annually.
Real companies have already rewritten visions quickly under AI pressure: Superhuman shifted from speed/automation to "AI-powered communication quality"; Adobe rapidly integrated AI (e.g. Firefly) across its product line.
Building a vision requires prior "homework": deep qualitative research validated broadly with quantitative data (the Trainline approach), and clarity on corporate strategy — a short "vision sprint" only works if these ingredients are already gathered.
A "vision sprint" should not be attempted if corporate strategy decisions are still pending (e.g., due in ~3 months) — the sequencing matters.
Three-question test for whether a real vision exists: can you say what problems you're solving and for whom; can you say how you'll make customers' lives better; can you see corporate strategy and company identity reflected in it.
Advice for a PM whose company lacks a vision: don't panic, form a personal point of view, lean on research teams, read "Inspired" and "Empowered," start introducing ideas to your manager, and begin educating the company informally.
A vision is only real if it's known: "it's not a vision if nobody knows about it" — like an invisible north star, an unknown vision fails its purpose.
Vision communication can take many forms (video, PR FAQ, deck, storyboards), but SVPG favors video for its emotional storytelling power; whatever the medium, it must contain the real ingredients, not just a tagline and slick visuals.
All-hands presentations of a vision mainly demonstrate alignment, not comprehension; the most effective way to actually communicate a vision is one-on-one, cascaded down through the org and spot-checked (e.g., asking a random engineer to explain what the vision statement really means).
The observed bigger problem in industry is the total absence of vision (~80% estimate) rather than a bad vision — companies typically have a mission and yearly targets with nothing substantive connecting them, so that gap gets filled directly by projects.
A compelling vision is more valuable to customers than a roadmap in a fast-changing world, because customers would rather commit to a company's 3–5 year future than to short-term deliverables; it also reduces reactive-culture pressure and repeated team restructuring driven by chasing each new threat/opportunity.
The real litmus test of a strong vision is not enthusiasm from product/engineering (who "grok" it naturally) but excitement from non-product functions like CFO, corporate affairs, finance, marketing, and sales.
Case studies: Kaiser Permanente's mission ("quality affordable healthcare") drove a telehealth-focused product vision, "Get Care Now," that launched just before the pandemic; John Deere's "farm of the future" vision exemplifies the recurring "smart X of the future" pattern across industries.
First-time vision leaders should: (1) gather core customer-problem ingredients (test: can you name the 10 most egregious org-wide problems), (2) confirm understanding of corporate strategy, and (3) seek coaching to assemble the vision itself.
Mission–Vision–Strategy–Roadmap hierarchy — A layered model where mission is the enduring "why," vision is the 3–5 year (or shorter) "what," strategy is the "how," and roadmap is near-term execution. Apply: Check any strategic artifact against this hierarchy — if your "vision" doesn't constrain choices or your "mission" changes yearly, you've mislabeled the artifact.
Three core vision ingredients — The non-negotiable inputs a real vision must contain: validated business and customer problems, alignment with corporate/executive strategy, and a glimpse of the revenue/monetization path. Apply: Before drafting a vision, confirm you can point to validated (not assumed) customer problems, know the exec-level strategic bets, and can sketch how the vision makes money.
Supplementary vision ingredients — Additional elements that give a vision "zing": a customer/business "wow" outcome narrative, awareness of industry trends, and a competitive leapfrogging angle (e.g., Gen AI). Apply: Layer a compelling future-state narrative and a named industry trend/competitive angle on top of the three core ingredients to make the vision inspiring, not just structurally correct.
Single-integrated-vision scope rule (with multi-BU exception) — A heuristic that most companies should have exactly one holistic product vision, with the only exception being very large companies with independent business units (e.g., Amazon's AWS, retail, and Alexa). Apply: Resist letting every team or business unit create its own vision; consolidate into one company-wide vision unless your business units genuinely operate as separate companies.
Vision ownership/RACI model — A responsibility model where the most senior product leader (CPO/CTO/VP Product) owns and authors the vision, the CEO is the #1 stakeholder and ideally its heaviest user, and CTO/VP Engineering and CFO provide key input. Apply: Assign one senior product leader to draft the vision, actively involve the CEO as sponsor/user, and pull in engineering and finance leadership for input rather than crowdsourcing the vision broadly.
Vision sprint — A condensed team exercise (e.g., about a week) to work through and articulate a product vision. Apply: Only run a vision sprint after the underlying ingredients (validated problems, corporate strategy clarity) are already gathered — otherwise the sprint alone can't produce a grounded vision.
Trainline research method (deep-then-broad validation) — A research approach used at Trainline: go deep with a smaller set of customers across key geographies to surface unstudied problems, then validate those conclusions broadly with quantitative data. Apply: Use targeted qualitative research to identify candidate core customer problems, then run a broader quantitative study to confirm they're representative before building a vision around them.
Three-question vision test — A diagnostic of whether a real vision exists: can you state what problems you're solving and for whom, can you state how you'll make customers' lives better, and can you see corporate strategy/company identity reflected in it. Apply: Run any existing "vision" statement through these three questions; if any answer is missing, treat the vision as not yet real.
Duplex-vs-skyscraper investment analogy — An analogy where building a two-story duplex without knowing a skyscraper will later be needed forces a costly re-platform, illustrating what happens when technology investment decisions are made without a vision. Apply: Use this analogy to explain to stakeholders why architecture/infrastructure decisions should be made with the intended future scale (the vision) in mind from day one, even if initial scope is small.
Vision communication medium checklist — The principle that a vision can be conveyed via video, PR FAQ, deck, or storyboards, but whichever medium is chosen must actually contain the core ingredients (validated problems, strategy fit) rather than just a tagline and visuals. Apply: Before finalizing a vision's presentation format, verify the chosen medium communicates the substantive ingredients, not just an inspirational surface narrative.
All-hands-vs-one-on-one communication distinction — A distinction where presenting a vision at an all-hands mainly demonstrates organizational alignment, while genuine comprehension is achieved and verified through one-on-one conversations. Apply: Follow a big all-hands vision reveal with individual follow-up conversations asking what problems are being solved, for which customers, and how each person personally contributes.
Cascading comprehension test — A coaching technique where a leader relays vision-comprehension questions to direct reports and expects them to relay the same questions further down, spot-checked by asking a random employee (e.g., an engineer) what the vision statement really means. Apply: Periodically ask a random employee outside leadership to explain the company vision in their own words to verify the vision has actually propagated through the org.
"Tasting the food" vision-substance metaphor — A metaphor for judging whether a vision has real substance — like being able to identify specific ingredients (e.g., cinnamon, paprika) in a dish rather than just confirming a meal exists. Apply: When reviewing a vision, check that you can identify its specific components (named problems, strategy links, revenue logic) rather than accepting a generic statement as sufficient.
Cross-functional excitement test for a strong vision — A litmus test claiming the true measure of a strong vision is that it excites functions beyond product/engineering — CFO, corporate affairs, finance, marketing, and sales — since product and tech people tend to "grok" a vision by default. Apply: Gauge vision strength by presenting it to non-product functions (finance, sales, marketing) and observing whether they respond with genuine excitement, not just polite acknowledgment.
First-time vision-leader starter method — A three-step approach for a product leader building their first vision: gather core customer-problem ingredients (test: name the 10 most egregious org-wide problems), confirm understanding of corporate strategy, and seek coaching to assemble the vision. Apply: Before attempting to write a vision for the first time, list the organization's 10 most egregious customer/business problems, verify your grasp of current corporate strategy, and bring in outside coaching to help construct the final artifact.
Gen AI is framed as causing the first vision-horizon disruption "since the birth of the internet," which inverts the prevailing industry trend toward longer (10-year) visions into an argument for shorter (~18-month) ones.
The acceptable degree of audacity in a vision is not absolute but culturally relative — the same stretch that collapses into a laughed-at "flying car" video at one company (Microsoft) works as a serious, sustained vision at another (SpaceX).
Vision-building is explicitly sequence-gated on corporate strategy: attempting a "vision sprint" before executive-level strategic decisions land (e.g., due in ~3 months) is called out as premature, implying most PMs underestimate this dependency.
The stated bigger risk isn't a misleading vision but its total absence — roughly 80% of companies reportedly have a mission and yearly targets with nothing substantive connecting them, so unarticulated vision silently gets replaced by ad hoc projects.
All-hands vision reveals are reframed as theater that signals alignment rather than the mechanism that actually transmits understanding — real comprehension is tested and built one-on-one, cascaded hierarchically, and spot-checked by interrogating random employees.
The genuine test of vision strength is cross-functional excitement outside product/engineering (finance, corporate affairs, sales) rather than enthusiasm from product and tech people, who are said to "grok" a vision by default regardless of its quality.
Kaiser's telehealth vision ("Get Care Now") is presented as having been built before the pandemic and merely validated by it — an implicit "never let a crisis go to waste" framing where prior positioning, not the crisis itself, produced the payoff.
Without a shared vision, infrastructure investment becomes retroactive guesswork (the duplex-vs-skyscraper analogy) and team topology gets rebuilt reactively roughly every five months as new threats or opportunities emerge.
«We are in business to save our planet.»
— 01:50
«That is a great mission. It's a crappy vision.»
— 03:46
«The vision is the thing that takes us from the incremental to the audacious.»
— 04:23
«We want to feel like we're leaving our dent on the universe.»
— 05:58
«A vision, it just can never be a collective enterprise.»
— 08:51
«The number one stakeholder in my opinion for a vision is the CEO.»
— 09:34
«Do not make the mistake of everyone having their own product vision.»
— 11:49
«How can you think 10 years out. I mean, it's impossible.»
— 19:48
«For the first time in my career, you know, maybe since the birth of the internet, you know, Gen AI and AI in general is shifting things so much more quickly.»
— 20:24
«If I cannot answer the question, what problems are you going to solve and who are you solving those problems for? You don't have a vision.»
— 24:38
«It's not a vision if nobody knows about it.»
— 28:26
«What I have seen a lot of is no vision, right? That is by far the bigger issue.»
— 32:04
«Someone only hears you once you've said something a hundred times.»
— 33:52
«Never let a crisis go to waste.»
— 36:51
«What are our 10 most egregious problems across the organization?»
— 38:14
«A quick disclaimer. While this podcast is named product therapy, it is not hosted by licensed therapists or mental health professionals, and it is in no way a substitute for professional mental health services.»
— 39:21
Reception
No comments are available to gauge audience reception.
A coherent, practitioner-grounded framework for separating mission, vision, and strategy and for diagnosing why most companies lack a real vision, though it draws mainly on the speaker's own consulting anecdotes (Microsoft, Trainline, Kaiser) rather than external validation or data beyond the cited ~80% estimate.
39:45