---
id: req.product-vision
title: Product vision
kind: practice
domain: requirements
description: Write a one-page product vision — positioning statement, audiences, observable outcomes and non-goals — and agree it before the requirements specification is written.
version: 1.0.0
status: approved
authority: recommended
applies_to: [core]
sources:
  - title: IREB CPRE Glossary — "Vision (for a system or product)"
    url: https://cpre.ireb.org/en/downloads-and-resources/glossary
    license: LicenseRef-All-Rights-Reserved
    accessed: 2026-11-20
  - title: Karl Wiegers and Joy Beatty, "Software Requirements", 3rd edition (Microsoft Press, 2013) — the vision and scope document
    url: https://www.microsoftpressstore.com/store/software-requirements-9780735679665
    license: LicenseRef-All-Rights-Reserved
    accessed: 2026-11-20
  - title: Roman Pichler, "The Product Vision Board"
    url: https://www.romanpichler.com/blog/the-product-vision-board/
    license: LicenseRef-All-Rights-Reserved
    accessed: 2026-11-20
  - title: SWEBOK Guide v4.0 — Software Requirements knowledge area
    url: https://www.computer.org/education/bodies-of-knowledge/software-engineering
    license: LicenseRef-All-Rights-Reserved
    accessed: 2026-11-20
standards: [ISO/IEC/IEEE 29148:2018]
related: [req.requirements-specification, req.scope-and-mvp, mgmt.project-foundation]
templates: [templates/vision.md]
last_reviewed: 2026-11-22
review_every: 12
---

## Summary

A product vision is a short, written picture of the product once it exists: who it is for, which need it meets,
what is different about it, and what will be true if it succeeds. It is the first requirements artefact. The
specification, the blueprint and every later decision are checked against it, so it has to be specific enough
to say no. A good vision fits on one page, names who it is for, lists outcomes that someone other than the
author can check, and states what the product will not do.

## Rules

- **R1.** A product MUST have one written vision, stored in the project repository, and the requirements
  specification MUST NOT be written before the vision has been confirmed by the person who owns the product.
- **R2.** The vision MUST contain a positioning statement that names the target users, the need or problem,
  the product category, the key benefit and the main alternatives the product differs from.
- **R3.** The vision MUST name its audiences as real groups of people, not "everyone", and say what each
  group gets from the product.
- **R4.** The vision MUST list three to five outcomes. Each outcome MUST have a time horizon and MUST be
  observable by someone other than its author.
- **R5.** The vision MUST list non-goals: what the product deliberately will not be or do.
- **R6.** The vision MUST NOT name technologies, vendors or architecture choices, and MUST NOT list features;
  those belong to the blueprint and the requirements specification.
- **R7.** Every outcome MUST be served by at least one scenario or requirement of the requirements
  specification before the specification is approved; a requirement that serves no outcome SHOULD be removed
  or an outcome added.
- **R8.** A change to the positioning statement, an outcome or a non-goal MUST be approved by the person who
  owns the product, MUST be recorded with its date in the vision itself, and MUST trigger a check of the
  specification and the blueprint.
- **R9.** The vision SHOULD fit on one page and SHOULD be reviewed at least once a year, and whenever
  evidence contradicts an outcome.

## Guidance

- **Positioning form.** A classic way to write the statement is: *For* (target users) *who* (need or problem),
  (product) *is a* (category) *that* (key benefit). *Unlike* (alternatives), it (main difference). Wiegers and
  Beatty recommend this form for the vision statement, crediting Geoffrey Moore's positioning statement;
  Pichler's vision board asks the same questions as boxes: target group, needs, product, value. Use whichever
  your team will fill in honestly. The Hub template is `templates/vision.md`; copy it to `project/VISION.md`.
- **Outcomes, not features.** "Within 12 months, a new contributor opens a first pull request in under one
  day" is an outcome. "Add a getting-started page" is a feature. If an outcome cannot be measured or
  observed, rewrite it until it can.
- **Non-goals are decisions.** A non-goal is not a wish to be modest; it is a recorded decision that stops
  scope from creeping in later. Good non-goals are things somebody might reasonably expect.
- **Vision, scope and roadmap.** The vision says why and for whom. The scope (see `req.scope-and-mvp`) says
  what this release does and does not include. The roadmap says in which order. Keep them separate files so
  each can change at its own speed.
- **Who confirms.** In a team where an AI agent drafts the document, the agent writes the vision as `review`,
  asks the owner to confirm the statement and the non-goals in the tracker, and does not mark it approved.
- **Small products.** A one-person tool still benefits from five lines: who, what need, what outcome, what
  not. Do the full page when other people or agents will build against it.
- **When not to apply.** A throw-away experiment or a bug fix does not need a vision; the product it belongs
  to has one.

## Explanation

The IREB glossary defines a vision as a conceptual picture of a future system or product, describing its key
characteristics and how it will create value for its users. Requirements work starts from this picture:
without it, requirements are collected from whoever asks loudest, and a long list of reasonable features
produces a product with no centre.

Wiegers and Beatty put the vision into a *vision and scope* document that comes before detailed requirements:
business opportunity, objectives and success measures, a vision statement, and the scope and limitations of
each release. ISO/IEC/IEEE 29148 likewise places stakeholder and business needs ahead of the system and software
requirements they lead to, and SWEBOK v4 describes requirements work as starting from the needs of the people
the product serves. The rules above keep that order: vision first, then specification, with a trace between
them (R7) so that nothing is built that serves no outcome.

For agents the vision has one more job: it is the short text that stops a plausible but wrong direction. An
agent that reads "non-goal: no user accounts" will not propose a login system in its first draft.

## Examples

Good — specific, with outcomes and non-goals (a fictional product):

```markdown
## Statement
For field engineers who lose paper notes on site visits, Fieldnote is a mobile notebook that works offline
and syncs when a signal returns. Unlike generic note apps, it ties every note to a site, an asset and a date.

## Outcomes
1. Within 3 months of launch, 20 engineers use it for every visit.
2. Within 6 months, no visit report is rebuilt from memory (checked by the weekly report review).

## Non-goals
- No shared editing of one note by several people at once.
- No invoicing.
```

Bad — everyone, no outcomes, technology in the vision:

```markdown
Fieldnote is a modern, scalable platform for everyone, built with React and GraphQL, that
empowers users to be more productive.
```

## Sources

- [IREB CPRE Glossary](https://cpre.ireb.org/en/downloads-and-resources/glossary) — © IREB, all rights reserved; the definition of vision is paraphrased. Accessed 2026-11-20.
- [Karl Wiegers and Joy Beatty, *Software Requirements*, 3rd edition](https://www.microsoftpressstore.com/store/software-requirements-9780735679665) — Microsoft Press, all rights reserved; the vision and scope document and the positioning form of the vision statement are summarised, not copied. Accessed 2026-11-20.
- [Roman Pichler, "The Product Vision Board"](https://www.romanpichler.com/blog/the-product-vision-board/) — all rights reserved; target group, needs, product and value as the parts of a vision. Accessed 2026-11-20.
- [SWEBOK Guide v4.0](https://www.computer.org/education/bodies-of-knowledge/software-engineering) — IEEE Computer Society, all rights reserved; Software Requirements knowledge area, summarised. Accessed 2026-11-20.
- ISO/IEC/IEEE 29148:2018, *Systems and software engineering — Life cycle processes — Requirements engineering* — referenced by name only.
