<!--
  Value Stream worksheet, from Blueprint Catalog (https://catalog.mikereams.com/library?s=templates).
  CC BY 4.0, Mike Reams. For a business-architecture Value Stream: a stakeholder's journey to a result they value,
  drawn in stages that each name the capabilities they rely on. Not a process map: no swimlanes, no systems, no teams.
-->

# Value Stream: <Trigger-to-Result name, e.g. Order to Cash>

| Field | Value |
|---|---|
| Stakeholder | <who receives the value> |
| Trigger | <the event that starts it> |
| Value item / outcome | <what the stakeholder has at the end, in their terms> |
| Scope note | <where it starts and stops; what neighboring streams own> |
| Catalog reference | <VS-… if you started from a catalog value stream> |

## Stages

Keep to five to nine stages. Each stage ends with something decided or produced; name it so a stakeholder would
recognize it. Capabilities are L2 by preference (ids from the catalog, or your own).

| # | Stage | Entry condition | Exit condition (value added) | Capabilities used | Pain points | Measure |
|---|---|---|---|---|---|---|
| 1 | <Stage name> | <what must be true to start> | <what is decided or produced> | BC-…, BC-… | <what goes wrong here> | <one measure, e.g. time in stage> |
| 2 | | | | | | |
| 3 | | | | | | |
| 4 | | | | | | |
| 5 | | | | | | |

## Read across

- Capabilities that appear in three or more stages: <list> — candidates for investment or a single owner.
- Stages with the most pain points: <list> — where to look first.
- Capabilities used here with no realizing application, or more than one: <list>.
