Geoffrey Moore's fill-in-the-blank sentence that forces a team to agree, in one line, on who the product is for, what it does, and why it's different.
▸ Try the interactive toolGeoffrey Moore's Product Vision Template is a structured, fill-in-the-blank sentence that forces a team to articulate — in one coherent statement — who the product is for, what problem it solves, what category it belongs to, and how it is meaningfully different from the alternatives.
Introduced in Crossing the Chasm (1991), it remains the most widely used vision-articulation tool in product management because it is three things at once: a positioning statement, a strategic compass, and a team-alignment device. It is short enough to memorise and specific enough to make real decisions against.
FOR [target customer] WHO [statement of need or opportunity], THE [product name] IS A [product category] THAT [key benefit — the reason to buy]. UNLIKE [primary competitive alternative], OUR PRODUCT [primary differentiation].
A vision statement is cheap to write and expensive to skip. Each blank in the template closes off a specific, recurring failure.
| The risk | What goes wrong without it | What the template prevents |
|---|---|---|
| Scope creep | The team builds for everyone because "FOR" was never defined. Effort spreads across incompatible user needs. | Forces specificity on the target — one segment, not a market. |
| Misaligned roadmaps | Engineering, design, and sales each carry a different mental model of what the product is. Decisions quietly conflict. | Creates one written reference every team member can quote. |
| Weak positioning | Marketing describes the product differently than sales. Prospects get confused and conversion suffers. | The "UNLIKE" and differentiator clauses force competitive clarity. |
| Strategy drift | The team chases features based on whoever spoke to a customer last. There's no filter for what fits. | The statement becomes a filter: "Does this serve [FOR] and deliver [KEY BENEFIT]?" |
| Exec & investor confusion | Leadership can't explain the product in 30 seconds. Fundraising and buy-in are slower. | Gives everyone a memorable, repeatable 30-second articulation. |
Work through the clauses in order. Each one is a decision, not a description — resist the urge to make any blank vague enough to be safe.
Name the person who opens the product and uses it, not the person who pays for it. If the "FOR" describes a buyer ("teams who need to cut costs"), you've written a sales pitch. Pick one segment and the specific need or opportunity that defines them.
The category sets the customer's expectations and mental shelf. Choose the one that makes your benefit obvious. A category that's too broad ("a platform") tells the reader nothing; one that's too clever invents a market that doesn't exist yet.
State the single most important reason to buy — the outcome, not the feature. "That sends reminders" is a feature; "that makes sure nothing falls through the cracks" is a benefit. One benefit, the strongest one.
Name the thing people actually do today instead of using you — which is often "nothing structured," a spreadsheet, or a manual process, not a famous rival. Naming a competitor you don't really compete with makes the whole differentiation meaningless.
Describe a transformation, not a feature list. Features get copied; a meaningful before/after state is much harder to replicate. Ask: what is the durable thing we do that the alternative structurally cannot?
A short illustration of how the finished sentence earns its keep.
A team kept arguing about what to build next, because each function pictured a different product. They wrote one vision sentence together: "FOR early-career employees WHO feel they're falling behind in a new role, the product IS A peer-learning space THAT makes their growth visible and supported. UNLIKE generic course libraries, OUR PRODUCT pairs people with a real person who knows them."
The sentence immediately did work. A proposed analytics dashboard aimed at buyers failed the "FOR" test — it served the purchaser, not the daily user — so it moved off the core roadmap. A reminder-notifications feature failed the differentiator test: it was a feature any course library could copy, not the "real person who knows you" transformation.
The deliverable is a single sentence — but each clause should trace to a defensible decision.
| Clause | What it captures | The test it must pass |
|---|---|---|
| FOR / WHO | The single user segment and their defining need | Could you point to one real person who fits? If it fits "40% of software users," it's too broad. |
| IS A | The category the product lives in | Does it set the right expectation and make the benefit obvious? |
| THAT | The single strongest reason to buy | Is it an outcome, not a feature? Strip any word that names a mechanism. |
| UNLIKE | The real alternative people use today | Is it what they'd actually fall back on — even if that's "nothing structured"? |
| OUR PRODUCT | The durable differentiator | Is it a transformation a competitor can't easily copy, not a feature they could ship next quarter? |
A vision statement you can't make decisions against is just decoration. The value isn't the wording — it's that every clause forces a choice the team would otherwise keep avoiding.
Once written and agreed, the statement does positioning (for marketing and sales), alignment (for engineering and design), and prioritisation (as a filter for the backlog) — all from one line everyone can recite. That's why it's the first tool: nearly everything downstream assumes it exists.
"FOR teams who need to reduce costs" is a sales pitch. Engineers then build dashboards for the purchaser instead of an experience for the daily user. Ask: who opens this every day?
"Our product has AI matching and weekly reminders." Features get copied. State the transformation — the before/after — that's hard to replicate.
"UNLIKE Google" or "UNLIKE Microsoft." Buyers know you're not replacing them, so the differentiation reads as empty. Name what people actually do instead of using you.
"FOR people who want to grow, THE product IS A platform THAT helps them improve." This describes nearly all software. If you could paste a competitor's name in and it still reads true, it isn't specific enough.
The vision is the second rung of the Mission/Vision/Strategy/Roadmap ladder. This sentence is what "Vision" looks like when made concrete; the ladder shows what sits above and below it.
JTBD gives you the precise "WHO" and the real "UNLIKE" — the job the user is hiring you for, and the surprising thing they fired to do it.
The VPC checks whether the "key benefit" you claimed actually maps to the customer's pains and gains, rather than just sounding good.
A clear vision is the strategic-fit lens that scoring frameworks assume. "Does this serve our FOR and deliver our benefit?" is the first cut before any score.
AI is a fast drafting and pressure-testing partner for a vision — but the vision itself is a judgment only you can own.
The judgment that stays yours: A vision is a strategic bet about the change you want to make — that conviction has to be yours. Use AI to articulate and challenge it, never to decide it for you.
Pick a product you use or work on. Fill in all five blanks — FOR, WHO, IS A, THAT, UNLIKE, OUR PRODUCT — in one sentence, out loud, without softening any clause.
Then stress-test it: could a competitor paste their own name into "OUR PRODUCT" and have it still read true? Is the "UNLIKE" the thing people actually do instead, or a famous name you don't really fight?
If the sentence could describe three other products, it isn't a vision yet — it's a category description. Keep cutting until only your product fits.