Product Vision at Company Scale: The CPO's Narrative Job

A product vision at company scale is the story an organization repeats about the future when its CPO isn't in the room. It names the customer, the broken status quo it replaces, the future state it makes possible, and early proof that future is arriving — built compact enough that a new hire can retell it, not just recite it.

Vision is the durable future state; strategy is the path there; the roadmap is near-term proof of progress. Test yours by asking someone two layers removed from you to retell it, unaided, in under a minute — if they can't, you have a slogan, not a narrative.

Vision, Strategy, and Roadmap Answer Three Different Questions

Vision, strategy, and roadmap get used interchangeably in most companies, but they answer different questions on different timescales. Vision describes an enduring future state (five-plus years); strategy is the set of bets that move toward it (twelve to twenty-four months); the roadmap is the near-term, constantly-revised proof that those bets are working (this quarter, next quarter). Treating them as one document is the single most common cause of vision confusion at scale.

Marty Cagan's writing at the Silicon Valley Product Group draws this line sharply: a product vision should describe a compelling future three-to-ten years out that the current roadmap should never fully satisfy — if your roadmap "completes" your vision, the vision was too small.

Jim Collins and Jerry Porras made a parallel argument in Built to Last: an enduring company separates a core ideology (purpose and values, which should almost never change) from specific goals and practices (which should change constantly as the market does). Vision lives in the first bucket; roadmaps live in the second. Confusing the two is why so many "visions" get quietly rewritten every planning cycle — they were roadmaps wearing a bigger word.

This distinction matters most for CPOs newly arriving at scale, where a predecessor's vision, strategy, and roadmap have often calcified into one indistinguishable slide. Sorting them out is one of the first structural moves worth making — the CPO's first 90 days is the wrong time to write a new vision from scratch, but it's exactly the right time to diagnose which of the three layers is actually missing.

Vision authorship is only one chapter of the broader job, though — it sits alongside portfolio calls, org design, and stakeholder management as one of the core disciplines covered in a complete CPO playbook. Treat this piece as the deep dive on the narrative half of that job, not the whole role.

The CPO's Real Job Is Narrative Transmission, Not Documentation

At company scale, the CPO's core job isn't writing a vision statement — it's engineering a story that survives being repeated by people who've never met you, three or four layers down, without your original phrasing attached. That's narrative transmission: designing language compact and vivid enough to travel intact through a hierarchy, rather than dissolving into generic corporate-speak by the third retelling.

This is a harder problem than most CPOs budget time for, because a vision that only lives in the CPO's own head, or in one polished all-hands deck, has already failed the job — it never reaches the engineer explaining to a new hire why the team exists. John Kotter's classic formulation from Leading Change is the elevator test: if you can't describe the vision to someone in five minutes or less and get a reaction that signals both understanding and interest, it isn't ready to lead a change effort.

Patrick Lencioni makes a related point in The Advantage — most executives stop repeating a message right around when it's finally starting to sink in for everyone else, because they're bored of their own words long before the org has internalized them. The lesson for a CPO: your own boredom with the story is not a signal to stop telling it.

Narrative transmission is a design problem, not a willpower problem. A few mechanisms actually move a story down through layers instead of just up through a slide deck:

• Verbatim repetition of the same phrases across every strategy doc, OKR kickoff, and roadmap review — not "in other words," but the identical sentence, every time.
• Onboarding as a transmission checkpoint, not an HR formality — new hires hear the vision narrative before they hear the org chart.
• Manager-led cascades, where each layer retells the story in their own words to their own team within a set window after an all-hands, rather than leaving it to a recording.
• The "enemy" language recurring in artifacts — specs, retros, and roadmap reviews reference the same status quo the vision names as broken, so the story stays load-bearing rather than ornamental.
• Removing the CPO as a single point of failure — if the story only works when you personally tell it, it isn't a narrative yet, it's a performance.

The Vision-Narrative Template: For Whom, the Enemy, the Future, the Proof

A repeatable vision narrative has four parts: for whom it's written, the enemy or status quo it replaces, the future it makes possible, and the proof that future is already arriving. Skip any one of the four and the story either becomes generic (no "for whom"), toothless (no enemy), abstract (no future scene), or unbelievable (no proof) — and unbelievable or generic stories are the ones that die at the first retelling.

Each element does a specific job:

1. For whom — name a specific role or persona, not "our customers" or "the market." Specificity here is what makes the enemy and the future concrete instead of abstract two steps later.
2. The enemy / status quo — the broken default your future replaces. This is rarely a competitor; it's usually a workaround, a spreadsheet, an outdated assumption, or an entrenched process the persona has learned to tolerate. Naming it precisely is what the Jobs to Be Done framework calls surfacing the friction in the current "hire" — the vision's enemy and the JTBD struggling moment are usually the same thing described from different altitudes.
3. The future — a concrete, sensory scene of the world after the enemy is gone, not a string of adjectives like "faster" or "more efficient." If you can't picture a person actually living inside it, it's still an aspiration, not a vision.
4. The proof — a recent, specific signal that the future is real and arriving, tied to strategy and roadmap without becoming the whole pitch. Proof anchors the vision to present-tense credibility.

Consider a hypothetical illustration, not a real company: a B2B expense-management product built around this four-part shape.

For whom: finance leads at fast-growing companies who approve spend by gut feel because their tools can't tell them what's normal. The enemy: the monthly spreadsheet reconciliation that turns every approval into a guess made under time pressure. The future: a finance lead opens a request and instantly sees whether it's typical for that team, that vendor, that month — approval becomes a five-second judgment call, not a research project. The proof: the anomaly-flagging beta already cut manual review time for the first cohort of pilot teams.

Notice the future half of that story reads almost like a redesigned customer journey — the emotional arc from dread to confidence at the approval moment. That's not a coincidence: a company-scale vision is, in miniature, a promise about how the defining moments in a customer's journey will feel different once it's real.

Test Whether Your Org Can Actually Repeat the Vision

The only real test of a company-scale vision is whether someone who didn't write it can retell it, cold, without notes, in under ninety seconds. Ask a person two or three organizational layers removed from you — not your direct reports, who've heard you say it a hundred times — and listen for whether they reproduce the four-part shape or reach for a feature list instead.

Run it as a deliberate exercise, not a hallway ambush:

1. Pick someone two-to-three layers removed from the CPO — an IC or a first-line manager, not a VP who sat in the strategy offsite.
2. Ask cold, with no warning and no prep time: "Why does this product exist, and where is it headed?"
3. Time it. A strong answer lands in sixty to ninety seconds. A response that runs long and vague, or stalls after one sentence, is a signal either way.
4. Score against the four-part template, not against how closely it matches your exact words — the goal is faithful reconstruction, not memorization.
5. Note where they punt — to a feature name, a competitor's name, or "ask my manager" — because that's exactly where the narrative broke down in transmission.

Gallup's long-running workplace research is a sobering data point on how rarely this test passes at scale: across its employee-engagement studies, well under half of employees strongly agree they actually know what their company stands for and what makes it different from competitors. That gap is exactly the transmission failure this test is designed to catch before it hardens into culture.

Where Vision Frays as the Company Scales

Vision typically fractures along three fault lines as a company scales: business units that quietly rewrite it to fit their own roadmap, portfolio bets that contradict the enemy the vision names, and an org structure that splits the narrative-bearing team before the story is fully transmitted. None of these are communication failures in the moment — they're structural failures that surface as communication failures.

• Business-unit drift. Each unit's leader retells "a version" of the vision optimized for their own team's roadmap, and within a year the four core elements have quietly diverged unit to unit.
• Portfolio contradiction. When capital-allocation decisions consistently fund initiatives that serve the enemy's logic rather than replace it — the safest bets, not the vision's bets — the story stops being credible no matter how well it's worded.
• Org-design fragmentation. If the teams meant to carry the narrative sit under different reporting lines with different incentives, the transmission chain breaks structurally before it ever reaches a retelling test. Product org design at scale is, in part, the discipline of keeping that chain intact.

The fix in each case is the same discipline applied upstream: treat vision integrity as a design constraint on portfolio and org decisions, not an afterthought communicated once those decisions are already made.

Keep the Vision Honest as Assumptions Change

A company-scale vision only stays credible if the assumptions it rests on get revisited on purpose, not just recited word-for-word every quarter regardless of what's changed underneath them. Treating vision as a plaque rather than a living set of testable bets is how CPOs end up defending a future that quietly stopped being true two strategy cycles ago.

Prodinja's Leadership Suite frames vision-setting as exactly that: a repeatable leadership act you return to and re-run, not a one-time authoring exercise you frame and forget.

Alongside it, the Decision Journal is designed to capture the strategic assumptions a vision and its supporting bets actually rest on — so that when a market shift or a failed bet calls one of them into question, there's a specific, named assumption to revisit instead of a vague sense that "the vision feels stale." It's a prototype experience built around that discipline, not a claim that any tool writes the vision for you — that job stays the CPO's.

Key Takeaways

• Vision, strategy, and roadmap answer different questions on different timescales — vision describes an enduring future, strategy is the bets that move toward it, and the roadmap is near-term proof; conflating them is the most common source of "vision" confusion at scale.
• The CPO's real job is narrative transmission, not documentation — a vision that only works when the CPO personally tells it hasn't actually reached the organization yet.
• A repeatable narrative has four parts: for whom, the enemy or status quo, the future, and the proof — missing any one makes the story generic, toothless, abstract, or unbelievable.
• The only real test is retelling, not recitation — ask someone two or three layers removed to retell the vision cold, and score their answer against the four-part shape, not your exact wording.
• Vision fractures structurally, not just rhetorically — business-unit drift, portfolio bets that contradict the enemy, and split org design all break transmission before communication even gets a chance to fail.
• Revisit the assumptions the vision rests on, on a real cadence, so the story stays a living bet rather than a plaque nobody's allowed to question.