# Value Stream Mapping: editable working templates
Make a copy for each engagement. Use Unknown rather than filling gaps with guesses.
These are service-workflow adaptations of value stream mapping, not a certification standard.
Start with templates 1 and 3. Use the others when the team chooses a stream.

## Review cover
Organization:
Facilitator:
People doing the work:
Date:
Decision this review should help:
Stage: offers overview / selected-stream review / pilot review
Privacy and sharing boundary:
Validation: pending / reviewed by [roles] on [date]

## 1. Offers and audiences
| Offer | Beneficiary and needed result | Purchaser or funding source | Delivery roles | Current / proposed | Evidence and unknowns |
| --- | --- | --- | --- | --- | --- |
| [Offer] | [Who benefits, and how?] | [Who pays or funds access?] | [Roles, not assumed owners] | [State] | [Source, date, questions] |

Connections between offers:
What must stay true (access, quality, human support, capacity):
Distinct streams to consider:
Team's selected stream, reason and date: not chosen
If not chosen, stop at high-level outlines and ask the team to choose.

## 2. Current-state workflow
Customer outcome:
Start event:
End event:
Unit of work:
Example or sample and date:
Status: provisional until reviewed by the team

| Step | Role | Input and source | Work and output | Recipient / handoff | Active time | Waiting before step / queue | System | Exception or rework | Evidence label / source |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| [Step] | [Role] | [Information needed] | [What happens] | [Who or what receives it] | Unknown | Unknown | [Tool or paper] | Unknown | Reported: [source/date] |

Plain-text map:
[Start] → [Step: role + input/output] → [Wait: unknown] → [Next step] → [Customer result]
Add a return arrow for rework and describe the information that triggers each step.

Elapsed lead time and calendar:
Volume / demand period:
Work waiting, observed on:
Quality measure and denominator:
Who checked this map, corrections and date:
Evidence still needed:

## 3. Evidence and unknowns
| Question or claim | Label | Source / date | What it establishes | What it does not establish | How to check | Responsible role / due date |
| --- | --- | --- | --- | --- | --- | --- |
| [Claim] | Observed / Reported / Assumption to check / Proposed change / Unknown | [Reference] | [Supported conclusion] | [Limit] | [Observation or question] | Unassigned |

## 4. Current, next pilot and longer-term ideal
Selected stream:
Customer result:
Protected constraints:

| Aspect | Current state and evidence | Next pilot (proposed) | Longer-term ideal | Dependencies / open decisions |
| --- | --- | --- | --- | --- |
| Customer experience | Unknown | Not selected | To discuss | [What needs deciding?] |
| Work and information flow | Unknown | Not selected | To discuss | |
| Human decisions and support | Unknown | Not selected | To discuss | |
| Capacity and funding | Unknown | Not selected | To discuss | |
| Outcome, quality and effort | Unknown | Not selected | To discuss | |

Alternatives considered (including simpler tools or no change):
Team's choice and trade-off:
Who reviewed this and when:

## 5. Improvement experiment and next review
Problem and supporting evidence:
Hypothesis: If we [change], we expect [result], because [reason to test].
Change to test:
What stays unchanged:
Owner: unassigned until confirmed
Participants:
Available time / budget:
Baseline, period, sample and source:
Primary outcome measure:
Quality / access / workload guardrails:
Proposed target and who agrees it:
Start and review date: unconfirmed
Stop or adapt if:
Other changes that might affect results:
Observation plan if baseline is missing:

At review:
What was done:
What happened:
What remains uncertain:
Decision: keep / adjust / stop / gather more evidence
Who decides:
What changes in the routine or SOP:
Next owner and review date: